ClaudeSuperPower
SubmitLog in

suggest

Skill

Proactively suggest the right Convex component when you notice the user hand-rolling something that already exists: setInterval polling (→ @convex-dev/crons), shared counter increments (→ @convex-dev/sharded-counter), .collect().length scans (→ @convex-dev/aggregate), email (→ resend component), rat

0Automation

Install

git clone https://github.com/get-convex/convex-backend-skill.git ~/.claude/skills/suggest

What is suggest?

Proactively suggest the right Convex component when you notice the user hand-rolling something that already exists: setInterval polling (→ @convex-dev/crons), shared counter increments (→ @convex-dev/sharded-counter), .collect().length scans (→ @convex-dev/aggregate), email (→ resend component), rate limiting via DB counter (→ @convex-dev/rate-limiter), fs.write uploads (→ Convex Storage), Elasticsearch (→ built-in search), online presence (→ @convex-dev/presence), long-running multi-step actions (→ @convex-dev/workflow), Pinecone/vector DB (→ @convex-dev/rag), or collaborative editing (→ @convex-dev/prosemirror-sync). TRIGGER when you notice this pattern in code or intent — AFTER completing the user's request, not interrupting it. DO NOT trigger for generic non-Convex questions.

What this can do

Capabilities declared in this component's own frontmatter — not inferred.

Inherit all session tools

Declares no tool restrictions — inherits every session tool

~198 tokens of context used while enabled, before you invoke anything

Documentation

README · ~1 min read

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.

Steps

  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.

Reviews

Log in to leave a review.

No reviews yet — be the first.

Explore related

Other things in this space — across every part of the ecosystem, not just skills.

Subagents

All subagents →

code-architect

Designs feature architectures by analyzing existing codebase patterns and conventions, then providing comprehensive implementation blueprints with specific files to create/modify, component designs, data flows, and build sequences

32.8K stars

plugin-validator

Use this agent when the user asks to "validate my plugin", "check plugin structure", "verify plugin is correct", "validate plugin.json", "check plugin files", or mentions plugin validation. Also trigger proactively after user creates or modifies plugin components. Examples: <example> Context: User f

32.8K stars

scan-inventory

Restricted read-only repository cartographer dispatched by the Claude Security scan workflow to partition the tree into components and account for every top-level directory; not for direct invocation or vulnerability research.

32.8K stars