V3 Core Implementation

Implement a DDD-based core TypeScript module with isolated domain logic and SQLite-backed persistence.

Updated Feb 10, 2026
One-click install
npx skills add https://github.com/monktui/git-review --skill v3-core-implementation-monktui
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: V3 Core Implementation
Source: https://github.com/monktui/git-review/tree/main/.claude/skills/v3-core-implementation
Command: npx skills add https://github.com/monktui/git-review --skill v3-core-implementation-monktui

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of creating a maintainable, well-structured core backend in TypeScript, where domain logic stays isolated from infrastructure while supporting clean dependency injection and reliable behavior through comprehensive tests.

Core Features & Use Cases

  • DDD domain modeling: Implements bounded contexts (task, session, health, lifecycle, and event coordination) using Entities, Value Objects, Aggregates, and Domain Events.
  • Clean architecture & DI: Provides a shared kernel plus application-layer use cases wired via an Inversify dependency container for repositories, services, logging, and event buses.
  • Repository implementations: Defines repository interfaces and includes a SQLite-backed repository for persistence of task state.
  • Test coverage for core logic: Includes domain unit tests and integration tests to validate entities, event emission, and repository behavior.

Quick Start

Implement the core foundation by creating the DDD domain structure and base classes, then implement the task, session, and health bounded contexts by wiring their entities, services, repositories, and corresponding tests.

Frequently Asked Questions about V3 Core Implementation

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

FAQPage Schema
How do I implement a DDD TypeScript core with clean architecture boundaries?

You can model bounded contexts using strict TypeScript configurations, defining isolated domain logic alongside application use cases. This separates core business rules from infrastructure components like SQLite-backed repositories.

How do I set up dependency injection for domain events in a TypeScript backend?

Yes, you can validate domain events and entity behavior by running included unit tests and integration tests. These tests ensure your repository implementations and event emission logic function reliably.

What's the best way to model bounded contexts for task state with SQLite persistence?

Modeling bounded contexts for task state involves defining repository interfaces and connecting them to a SQLite-backed repository for persistence. This approach keeps your domain aggregates cleanly separated from database operations.

Do I need an Inversify dependency container to wire clean architecture use cases?

Yes, an Inversify dependency container is required to wire application-layer use cases. It manages injections for repositories, services, and logging, ensuring your clean architecture boundaries remain strictly enforced.

When should I not use domain events for coordinating bounded contexts?

You should avoid domain events for coordinating bounded contexts when your application use cases require synchronous, transactional consistency across aggregates, as event publishing inherently decouples communication and eventual consistency.