What problem does it solve?
This skill solves the inconsistency and technical debt associated with defining request and response shapes for MCP endpoints by providing a structured, domain-driven approach to DTO management.
Core Features & Use Cases
- Domain-Driven Organization: Groups DTOs by functional domain (explore, ingest, collection, document) to maintain a clean API surface.
- Standardized Interface Patterns: Enforces naming conventions and inheritance rules for request and response types.
- Use Case: When adding a new search feature to the MCP server, use this skill to define the required request and response interfaces in the appropriate domain file and ensure they are correctly exported through the barrel files.
Quick Start
Use the add-dto skill to create a new request and response type for the collection domain following the established interface patterns.