design-system

To write a module CDD, this skill synthesizes repository context, module indexes, and dependency docs, then incrementally drafts each design section with approval checkpoints. It ensures your module design aligns with existing architecture decisions without missing prior constraints.

You can safely retrofit an existing CDD by filling only missing sections. The skill performs retrofit updates that preserve completed content, scanning the document to identify gaps and appending required design sections without overwriting your previous work.

The best way to draft design documents section by section is using incremental file writing with review checkpoints. This skill walks through Overview, Design, Formulas, Edge Cases, Dependencies, Tuning, and Acceptance Criteria, requiring approval after each draft before persisting.

Context gathering for module design reads relevant concept docs, module indexes, dependency documents, and prior failure patterns. This skill applies repository-aware context synthesis to extract constraints, ensuring the generated CDD reflects actual project dependencies and historical design failures.

You need a module registry to perform registry conflict checking during CDD authoring. This skill verifies the new module's frontmatter discovery and naming against existing entries, preventing duplicate registrations and ensuring proper specialist-agent consultation.

Automated module design documentation relies strictly on available repository context and dependency docs. If prior failure patterns or architecture concepts are missing from the repository, the generated CDD sections may lack necessary constraints, requiring manual specialist-agent consultation to fill gaps.