Module Design

Apply software design principles to whatever the user brings. Explore the project before asking; let the principles drive the analysis. Produce a spec for new designs or a violations report for existing ones.

Available scripts

• scripts/skillsrc.py — Reads and writes module-design config from .draekien/.skillsrc.

Session Start

Run once on first invocation in this order:

1. Load config — run uv run scripts/skillsrc.py --config .draekien/.skillsrc --skill module-design get specsDir --default docs/designs to read the spec output directory. If the script is unavailable, parse .draekien/.skillsrc as JSON directly and read module-design.specsDir; default to docs/designs if absent.
2. Open question — if the module or system in scope isn't already clear from the conversation, ask what to look at before proceeding.

Understanding the module

After the user answers the opening question from Session Start, explore the project, then ask further targeted questions. What matters is understanding scope, responsibility, callers, data contract, side effects, and boundaries — whether by reading existing code or by interviewing the user. If the module exists, the codebase already answers most of these.