convex-component-authoring

Create self-contained Convex components with isolated schemas and type-safe exports.

Updated Feb 7, 2026
One-click install
npx skills add https://github.com/rieckt/create-loumi-app --skill convex-component-authoring-rieckt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: convex-component-authoring
Source: https://github.com/rieckt/create-loumi-app/tree/main/template/skills/convex/convex-component-authoring
Command: npx skills add https://github.com/rieckt/create-loumi-app --skill convex-component-authoring-rieckt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams create self-contained Convex components with isolated data and exports, enabling reuse across projects.

Core Features & Use Cases

  • Isolated component scope: per-component schema, tables, and functions.
  • Type-safe exports and optional frontend hooks.
  • Publish-ready packaging and versioning for reuse across apps.

Quick Start

Initialize a new component project structure, implement your component per the guide, and publish to your registry.

Frequently Asked Questions about convex-component-authoring

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

FAQPage Schema
How do I build reusable Convex components with isolated data?

To build reusable Convex components, you define a self-contained project structure with per-component schemas, isolated data tables, and type-safe function exports. This blueprint ensures your component logic operates independently for safe reuse across different deployments.

What is the best way to package and publish a TypeScript component for Convex?

The best way to publish a Convex component is to follow a modular packaging workflow that includes type-safe exports, clear versioning, and isolated function organization. This prepares your TypeScript package for registry publication and cross-app reuse.

How do I structure a Convex component schema for cross-project reuse?

You structure a Convex component schema by creating an isolated component scope with dedicated tables and functions. This modular organization separates component data from the main application, enabling clean type-safe exports and reliable cross-project deployment.

Do I need TypeScript to export frontend hooks from a Convex component?

TypeScript is used to ensure type-safe exports and optional frontend hooks when building a Convex component. Using TypeScript allows you to provide clear, modular interfaces for frontend integration while maintaining strict data isolation within the component.

When should I isolate Convex functions into a modular component?

You should isolate Convex functions into a modular component when you need to reuse specific backend logic and schemas across multiple projects or deployments. This approach prevents data coupling and simplifies packaging for broad application reuse.