Agent skill · software engineering · aiskillstore
convex-create-component
Designs and builds Convex components with isolated tables, clear boundaries, and app-facing wrappers. Use this skill when creating a new Convex component, extracting reusable backend logic into a component, building a third-party integration that owns its own tables, packaging Convex functionality for reuse, or when the user mentions defineComponent, app.use, ComponentApi, ctx.runQuery/runMutation across component boundaries, or wants to separate concerns into isolated Convex modules.
Why this skill is useful
Provides specific patterns and structures for creating reusable Convex components that the AI wouldn't reliably generate on its own.
What it needs
Requires convex installed locally. About 6k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Convex Create Component Create reusable Convex components with clear boundaries and a small app-facing API. When to Use Creating a new Convex component in an existing app Extracting reusable backend logic into a component Building a third-party integration that should own its own tables and workflows Packaging Convex functionality for reuse across multiple apps When Not to Use One-off business logic that belongs in the main app Thin utilities that do not need Convex tables or functions App-level orchestration that should stay in convex/ Cases where a normal TypeScript library is enough Workflow 1. Ask the user what they are building and what the end goal is. If the repo already makes the answer obvious, say so and confirm before proceeding. 2. Choose the shape using the decision tree below and read the matching reference file. 3. Decide whether a component is justified. Prefer normal app code or a regular library if the feature does not need isolated tables, backend functions, or reusable persistent state. 4. Make a short plan for: what tables the component owns what public functions it exposes what data must be passed in from the app (auth, env vars, parent IDs) what stays in the app as wrappers or HTTP mounts 5. Create the component structure with convex.config.ts, schema.ts, and function files. 6. Implement functions using the component's own ./generated/server imports, not the app's generated files. 7. Wire the component into the app with app.use(...). If the app does not already have convex/convex.config.ts, create it. 8. Call the component from the app through components.<name> using ctx.runQuery, ctx.runMutation, or ctx.runAction. 9. If React clients, HTTP callers, or public APIs need access, create wrapper functions in the app instead of exposing component functions directly. 10. Run npx convex dev and fix codegen, type, or boundary issues before finishing. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/convex-create-component