typescript-write

Domain-driven design for TypeScript/React organizes code into four layers: Repository (data access), API Client (external services), Hooks (business logic), and Components (UI). This Skill automates applying that structure to Next.js features, enforcing explicit typing, consistent error handling, and test-driven workflows to keep concerns separated and code maintainable.

Yes. Test-driven development with TypeScript/React means writing failing tests first, then implementing components, hooks, and API logic to pass them. This Skill applies TDD to a 4-layer DDD structure, ensuring your React features are typed, tested, and aligned with Semicolon team standards before deployment.

Supabase integration follows the DDD Repository pattern: create a dedicated Repository layer for Supabase queries, expose typed API Clients for business logic, wire logic through Hooks, and consume data in Components. This Skill enforces that layering automatically, preventing Supabase calls from leaking into UI code.

Explicit, strict typing prevents runtime errors; consistent error-handling patterns ensure predictable failures. This Skill standardizes both across your codebase by applying lint and typecheck rules, Repository/API Client/Hook/Component patterns, and Semicolon team conventions to all TypeScript/React code.

No. The Skill adds DDD components incrementally: identify where your existing code needs a Repository, API Client, Hook, or Component, add it following the pattern, and write failing tests first. You integrate one feature at a time without a full rewrite.

The Skill enforces lint and typecheck rules as part of its workflow, catching style, typing, and error-handling violations before code review. Violations block merge until resolved, ensuring consistent quality across your Next.js project.