convex-create-component

Design and implement reusable Convex components with isolated tables and app-facing APIs.

Updated Apr 4, 2026

Search Tags:#typescript #components #backend #monorepo #auth #convex

Ready to run

npx skills add https://github.com/flvvius/cue --skill convex-create-component-flvvius

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: convex-create-component
Source: https://github.com/flvvius/cue/tree/main/packages/backend/.agents/skills/convex-create-component
Command: npx skills add https://github.com/flvvius/cue --skill convex-create-component-flvvius

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you design and implement Convex components when backend logic needs clear boundaries, isolated tables, and a small app-facing API instead of staying as scattered app code.

Core Features & Use Cases

Component Design: Chooses whether a local, packaged, or hybrid component is the right fit for the requested feature.
Boundary-Aware Implementation: Structures tables, functions, auth handling, environment access, and wrappers so component code stays isolated and safe.
Convex Integration: Guides how to install the component with app wiring, generate code, and call component functions through the app.
Use Case: A team wants to extract notifications, integrations, or reusable backend workflows into a Convex module that can be maintained independently and reused cleanly.

Quick Start

Ask for help designing a Convex component for your feature, and I will first confirm the right component shape before planning the tables, API surface, and app wrappers.

Frequently Asked Questions about convex-create-component

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

FAQPage Schema

How do I structure reusable Convex components with isolated tables and clear API boundaries?▼

You should design the Convex component by first determining if a local, packaged, or hybrid shape fits your feature, then planning isolated tables, the API surface, and app wrappers to maintain clear backend boundaries.

When do I need to extract backend logic into a packaged Convex component?▼

You need to extract backend logic into a packaged Convex component when features like notifications or third-party integrations require isolated tables, independent maintenance, and clean reuse across different app environments.

How do I handle auth and environment variables across Convex component boundaries?▼

Handle auth and environment variables across Convex component boundaries by using explicit validators and app-side environment handling, ensuring component code remains isolated and safe from direct external access.

Does this approach support codegen for component function calls in a TypeScript monorepo?▼

Yes, this approach supports codegen-aware implementation across component boundaries. It guides you through installing the component with app wiring, generating code, and calling component functions safely within your TypeScript monorepo.

What is the difference between local, packaged, and hybrid Convex components?▼

Local components live within your app for immediate use, packaged components are extracted for independent maintenance and reuse, and hybrid setups combine both for reusable workflows and shared backend logic across teams.