convex-create-component

Create Convex components with isolated tables and app-facing APIs.

Updated Apr 24, 2026
One-click install
npx skills add https://github.com/featurectrl/website --skill convex-create-component-featurectrl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: convex-create-component
Source: https://github.com/featurectrl/website/tree/main/.claude/skills/convex-create-component
Command: npx skills add https://github.com/featurectrl/website --skill convex-create-component-featurectrl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Convex projects often struggle to design and implement reusable components with isolated data boundaries. This skill provides a structured approach for creating components that own their own tables, expose a clear app-facing API, and can be reused across apps or different modules.

Core Features & Use Cases

  • Isolated tables and clear boundaries for each component
  • Packaging Convex functionality for reuse across apps
  • App-facing wrappers and integration via app.use and ComponentApi

Quick Start

Plan the component's data model, public API, and app wiring; implement under convex/components/<name>/, generate server code, and wire it into the app, then run npx convex dev to iterate.

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 isolated data boundaries?

Reusable Convex components are built using defineComponent to establish isolated tables and clear boundaries, then exposed via an app-facing API to ensure modular backend logic remains separate across different apps.

What is the best way to package Convex functionality for reuse across apps?

Packaging Convex functionality for reuse involves designing components with app-facing wrappers and clear boundaries, then integrating them across apps using app.use and ComponentApi for proper boundary data transfer.

How does app.use and ComponentApi work for integrating Convex components?

Integrating Convex components uses app.use and ComponentApi to wire app-facing wrappers, ensuring proper boundary data transfer from the app to the component while maintaining public function exposure and isolated tables.

When should I extract backend logic into a Convex component?

Extract backend logic into a Convex component when packaging modularized functionality for reuse across apps, ensuring isolated tables and clear boundaries define the component's data model and app-facing API.

Can I use defineComponent to isolate tables and enforce boundaries in Convex?

defineComponent isolates tables and enforces boundaries in Convex by structuring owned tables and public functions, ensuring the component maintains clear data boundaries and an app-facing API for integration.

Does integrating Convex components across apps require app wrappers?

Integrating Convex components across apps requires app wrappers to expose the app-facing API and ensure proper boundary data transfer from the app to the component, maintaining the integrity of isolated tables.