Convex Ddd Architecture

If you're building a non-trivial Convex app and find business logic bleeding into your mutations or database calls scattered everywhere, this skill enforces DDD and hexagonal boundaries. It prescribes a folder structure that separates domain models, repository interfaces, and adapter implementations, plus patterns like composing schema from sub-domain tables and wrapping all functions through a custom boundary for trigger integration. The naming guidance is opinionated: domain vocabulary on exports, short locals inside functions, one file per query or mutation with default exports. Overkill for prototypes, but worth it when you need team consistency or plan to refactor a growing codebase without breaking everything.