cli-forge-lldlisted

> **Optimization:** This skill uses on-demand loading. Heavy content lives in `references/` and is loaded only when needed. > **Language rule:** Skill instructions are written in English. When generating user-facing output, detect the project's primary language (from README, comments, docs, commit messages) and produce the document in that language. If the project is bilingual, ask the user which language to use before proceeding. # Forge LLD — Low-Level / Detailed Design Translate an HLD's "what" into the "how" — detailed enough that a developer can implement without ambiguity. *(Robert C. Martin, Clean Architecture)* ## Core Principles 1. **Mitosis** — the document grows only the sections the component actually needs. A stateless function doesn't need a state machine. A read-only service doesn't need a migration plan. Kill empty sections, don't fill them with boilerplate 2. **Implementable precision** — every included section must be specific enough to code from. No hand-waving 3. **Contract-first** — define API contracts and interfaces before internals 4. **SOLID by default** — design visible in class diagrams must respect SOLID; flag violations explicitly 5. **Patterns justified** — only document a pattern when its use is non-obvious from reading the code 6. **KISS** — one clear diagram beats two pages of prose. One code example beats three paragraphs of explanation. Readers are developers — they scan for interfaces, schemas, and contracts 7. **Gotchas** — read `../.