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.

skills.sh installs: 288
last updated: Jun 3, 2026

View on GitHub

Install

$ npx -y skills add sebas5384/agentic-stuff --skill convex-ddd-architecture --agent claude-code

Installs into .claude/skills of the current project.

Files

Convex DDD Architecture

Reference skill for organizing Convex projects with DDD and Hexagonal architecture. It keeps domain logic isolated from database and external API concerns so changes remain local and safer to evolve.

When to Use

Use this skill when work includes one or more of these signals:

New Convex sub-domain design (schema, queries, mutations, domain, adapters)
Legacy Convex code migration toward DDD/Hexagonal boundaries
Business rules drifting into handlers instead of aggregates
Direct ctx.db access spreading outside repositories
External API calls requiring retries, orchestration, or translation layers
Team-level need for consistent file layout and naming in Convex projects
Choosing or refactoring identifiers (variables, functions): domain nouns on exports/models; shorter names inside modules/functions where scope already disambiguates (naming.md)