convex-create-component

Generate Convex component skeletons with isolated tables and bounded APIs.

2|Updated Jan 7, 2026

Search Tags:#components #schema #modularity #convex #boundary #app-wrappers

Ready to run

npx skills add https://github.com/Lostovayne/Complete-Cursor-Clone-Next16 --skill convex-create-component-lostovayne

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: convex-create-component
Source: https://github.com/Lostovayne/Complete-Cursor-Clone-Next16/tree/main/.agents/skills/convex-create-component
Command: npx skills add https://github.com/Lostovayne/Complete-Cursor-Clone-Next16 --skill convex-create-component-lostovayne

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Convex components help teams structure backend logic and data access behind a stable interface, enabling clean boundaries between app code and reusable modules.

Core Features & Use Cases

Isolated tables and bounded APIs for each component to maintain clear ownership.
App-facing wrappers and fine-grained boundaries to minimize cross-boundary coupling.
Reusable patterns for local vs packaged components to support growth across apps.

Quick Start

Define your component structure under convex/components/<name>/ with a convex.config.ts, schema.ts, and lib.ts, then wire it into your app via convex.config.ts and app.use(...).

Frequently Asked Questions about convex-create-component

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I create reusable Convex components with clear boundaries?▼

Define your component structure under convex/components/<name>/ with convex.config.ts, schema.ts, and lib.ts files, then wire it into your app via convex.config.ts and app.use(...). This enforces isolated tables and bounded APIs for each component.

Why do I need app-level wrappers for Convex components?▼

App-level wrappers are required for client access and proper auth/env handling. They minimize cross-boundary coupling by providing a fine-grained boundary between your reusable component logic and your application code.

What's the best way to structure Convex schema and APIs for multiple apps?▼

Use reusable patterns for local vs packaged components to support growth across apps. Define isolated tables and bounded APIs for each component, maintaining clear ownership boundaries between app code and reusable modules.

Can I use Convex components across different applications?▼

Yes, Convex components can be built as reusable modules within a single app or across multiple apps. The skeleton includes convex.config.ts, schema.ts, and lib.ts, enforcing component boundaries for clean data and logic separation.

What files are required to set up a new Convex component?▼

A new Convex component requires a convex.config.ts, schema.ts, and lib.ts file. These files form the component skeleton, defining isolated tables, bounded APIs, and clear ownership boundaries.

When should I not use packaged Convex components?▼

Avoid packaged Convex components if your feature module cannot be isolated into bounded APIs with clear ownership boundaries. Components require app-level wrappers for client access, so tightly coupled app logic may not benefit from this modular structure.