convex-suggest

作者: get-convex

在使用者手動實作 Convex 已能解決的模式(crons、sharded-counter、rate-limiter、storage、search、presence、workflow、RAG、prosemirror-sync)時,建議相符的 Convex component。被動式——在工作完成後建議,絕不中斷。未經同意絕不安裝。

npx skills add https://github.com/get-convex/agent-skills --skill convex-suggest

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.).

來自 get-convex 的更多技能

convex-performance-audit
get-convex
審計Convex在讀取、訂閱、寫入競爭及函數限制方面的效能。適用於功能緩慢、洞察發現、OCC衝突或讀取放大等情況。
developmentdatabasedata-analysis
convex
get-convex
將一般 Convex 請求路由至正確的專案技能。當使用者詢問該使用哪個 Convex 技能,或給出未明確指定的 Convex 應用任務時使用。
developmentdatabase
convex-setup-auth
get-convex
設定 Convex 驗證、身份映射與存取控制。用於 Convex 應用中的登入、驗證提供者、使用者資料表、受保護函式或角色。
developmentdatabaseapi
convex-quickstart
get-convex
建立或將 Convex 加入應用程式。適用於新的 Convex 專案、npm create convex@latest、前端設定、環境變數,或首次執行 npx convex dev。
developmentdatabase
convex-migration-helper
get-convex
使用 widen-migrate-narrow 和 @convex-dev/migrations 規劃 Convex 架構與資料遷移。適用於破壞性架構變更、資料回填、資料表重塑或零停機部署。
developmentdatabase
convex-create-component
get-convex
構建可重複使用的 Convex 元件,包含獨立的資料表與面向應用程式的 API。適用於新元件、可重複使用的後端模組、整合或元件邊界工作。
developmentdatabase
convex-migrate
get-convex
使用 @convex-dev/migrations 在已部署的 Convex 應用程式上遷移 schema 並回填資料。
developmentdatabase
convex-optimize
get-convex
審計並優化現有的 Convex 應用程式:安全性、擴展性、升級與可觀測性。