dddlisted

## What This Skill Changes ddd changes how you respond when code structure, layering, API contracts, or behavior visibility questions surface. By default, you might give one-line advice, refactor inline, or skip the analysis. ddd forces structured diagnosis before any code changes. | Concern | Default behavior | ddd behavior | |---------|-----------------|--------------| | Architecture | Suggest a refactor; hope for the best | Map structure with `tp-explorer`, emit a Failure Signal, dispatch to `implement` | | API design | Sketch endpoints from intuition | Spawn `tp-endpoint-auditor`, produce a contract failure signal, dispatch to `refine` | | Transparency | Note CQS violations in passing | Audit Command/Query boundaries explicitly; classify as pure/impure | | Quality | Catch obvious smells | Apply library-first threshold (30 lines), error-as-vocabulary, naming idioms | **Downstream action:** this skill never edits code. After diagnosis, dispatch the Failure Signal JSON to `core-principled:implement` (for restructuring) or `core-principled:refine` (for contract polish and quality cleanup). ## Routing Guidance - ARCHITECTURE: 'where does business logic go', 'too much nesting', 'too many parameters', 'function does too much', 'business logic in controllers' - QUALITY: 'what should I name this', 'should I use a library', 'silent failure' - TRANSPARENCY: 'hidden side effect', 'does this return or mutate', 'is this a side effect', 'mutation disguised as query' - API: 'design