components-guide

To structure a Convex backend as independent components, you encapsulate features with isolated data schemas and APIs, wire them into convex.config.ts, and maintain a root SKILL.md with YAML frontmatter to define clear boundaries for modularity and reuse.

You should extract functionality from a monolithic Convex codebase into components when you need to improve maintainability, isolate features, enable the sibling components pattern, or reduce monolithic dependencies across multiple development teams.

The sibling components pattern in Convex backends is a modular architecture approach where self-contained components with isolated data schemas and APIs are composed together across projects to enforce clear boundaries and enable feature reuse.

Structuring Convex components requires no external dependencies, but it enforces a root SKILL.md with YAML frontmatter including name and description, while allowing optional scripts, references, and assets directories for supplemental resources.

The best way to reduce monolithic dependencies across teams using Convex is to encapsulate features as self-contained components with isolated data schemas and APIs, enabling the sibling components pattern for clear architectural boundaries and project reuse.