convex-create-component

Create isolated Convex components with config, schema, and lib files.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/awfixers-stuff/corp.awfixer.me --skill convex-create-component-awfixers-stuff
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: convex-create-component
Source: https://github.com/awfixers-stuff/corp.awfixer.me/tree/main/.agents/skills/convex-create-component
Command: npx skills add https://github.com/awfixers-stuff/corp.awfixer.me --skill convex-create-component-awfixers-stuff

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Guides teams to establish clear boundaries around Convex components, enabling isolated backend logic with dedicated tables and app-facing APIs, instead of coupling everything into the main app.

Core Features & Use Cases

  • Define a local component boundary with its own convex.config.ts, schema.ts, and lib.ts.
  • Provide a consistent pattern for app wiring via app.use(...) and wrapper functions in the app.
  • Use for extracting reusable backend logic, integrations, or component-boundary work across apps.

Quick Start

Create a new Convex component scaffold with convex.config.ts, schema.ts, and lib.ts, and wire it into the app with 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 isolate backend logic into a reusable Convex component?

To isolate backend logic in Convex, define a local component boundary with its own convex.config.ts, schema.ts, and lib.ts, then mount it into the app using app.use(...) and app-facing wrapper functions.

What are Convex component boundaries and when do I need them?

Convex component boundaries separate isolated backend logic and dedicated tables from the main app. You need them when extracting reusable backend logic, building integrations, or packaging functionality into boundary-driven modules across multiple apps.

How do I wire a Convex component into my main app?

Wire a Convex component into your app by calling app.use(...) to mount the component, then create app-side wrapper functions to expose the component's app-facing APIs and enforce explicit validators on public component functions.

Does this approach require explicit validators on public component functions?

Yes, establishing a clear component boundary requires explicit validators on public component functions to ensure the isolated backend logic and dedicated tables remain decoupled from the main app's internal implementation.

What's the best way to extract reusable backend logic in Convex without coupling everything into the main app?

The best way to extract reusable backend logic in Convex is to package it into a boundary-driven component with its own schema and config, providing a consistent pattern for app wiring via app.use(...) and wrapper functions.