Convex Suggest

by get-convex2cfe645c87f9No licenseListed Oct 8, 2026Updated Oct 8, 2026

Suggest the matching Convex component when the user hand-rolls a pattern it already solves (crons, sharded-counter, rate-limiter, storage, search, presence, workflow, RAG, prosemirror-sync). Passive — suggest after the task, never interrupt. Never install without consent.

Instructions onlySoftware Development
AI-generated overview

Suggests a matching Convex component when code duplicates an existing pattern, without interrupting the task.

What it does
This skill watches code and user requests for patterns that an existing Convex component already solves, such as cron jobs, sharded counters, rate limiting, storage, search, presence, workflows, RAG, or collaborative editing. After the current task is finished, it offers one suggestion naming the component, quoting the triggering code or phrase, and explaining why the component fits. It only proceeds with installation if the user explicitly agrees, and it drops the suggestion if the user declines or ignores it.
When to use it
Use it when working on Convex code or requests where the user appears to be hand-rolling functionality that a Convex component already provides. It is meant to run passively alongside a task and surface a single suggestion afterward, not to interrupt or block work.
Requirements
No scripts or special tooling are required; it is an instructions-only skill. It assumes a Convex project context and references an install command and detector rules, but needs no credentials or network access beyond the agent.
<!-- GENERATED from convex-agents content/capabilities/suggest.json — do not edit by hand. -->

Proactively suggest the right Convex component

When you see code or intent that duplicates what a Convex component already does, surface a targeted suggestion: ONE component, WHY (anchored in the user's own code or ask), and a concrete install hint. Never install without explicit consent. Never suggest more than one component at a time unless the user asks.

Workflow

  1. Observe the codeSnippets and userAsk passively — never block the current task to suggest.
  2. Match against the detector rules (see generators/suggest-detector.mjs): email/SMTP → resend; push notifications → expo-push; setInterval/cron → @convex-dev/crons; shared counter increments → @convex-dev/sharded-counter; .collect().length scans → @convex-dev/aggregate; multi-step/long-running actions → @convex-dev/workflow; bounded concurrency → @convex-dev/workpool; rate-limit counters in DB → @convex-dev/rate-limiter; fs.write/S3 uploads → Convex Storage; Elasticsearch/Algolia → built-in full-text search; presence/typing → @convex-dev/presence; Pinecone/external vector DB → @convex-dev/rag; collaborative editing → @convex-dev/prosemirror-sync.
  3. After finishing the current task, offer ONE suggestion: name the component, quote the specific code or phrase that triggered it, explain why the component fits better.
  4. If the user says yes: run /add <component> or follow the installHint from the detector.
  5. If the user says no or ignores it: drop it. Do not repeat the same suggestion.

Rules

  • Passive — never interrupt the current task; surface the suggestion AFTER completing what the user asked.
  • One at a time — pick the highest-priority match; do not dump a list of five components.
  • Cite WHY from the user's own code or ask — 'I noticed you wrote post.likes + 1 in a mutation that many users call concurrently; that causes OCC conflicts at scale.'
  • Never install without explicit consent — suggest, explain, wait for a yes.
  • Do not suggest a component the user has already installed.
  • Do not fire on generic coding questions unrelated to Convex (sorting arrays, writing CSS, etc.).

Source and attribution

Source:get-convex/agent-skillsinskills/convex-suggestat commit2cfe645

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal