pdd-prompting
Installation
SKILL.md
PDD prompting
Each module's .prompt.md is the source; code implements it.
Core rules
- Read
RUNBOOK.mdfirst,guide.mdin full, andstory-guide.md; skiprunbook/*.mdchapters unless a workflow step or lint error points to one. - Finish Prompt Space (
pdd lint --local-> passingpdd test) before code; change no code and start no interactivepdd simulateunless asked. - One prompt per module: purpose,
## Domain decisionsand failure edges. Give each rule one owner prompt. Link shared rules. For a CLI, say if a rule belongs to the whole-CLI prompt or to one module's prompt. - Inject outside effects (DB, files, net, clock, RNG, IDs) via inputs or
<port>.<op>ports; never use prose counters or linkkind: native-onlyadapters under## Dependencies(RUNBOOK §21). - Linked
.ui.svgis the layout spec: parts, words, order, ids and states. Check withpdd lint --local; render PNGs only if asked (RUNBOOK §13). - Write Short JSON scenarios with self-contained step inputs (
seeds+$use/patch) for parallel steps; chain$steporworldonly for persistence, with1observable check per claim; never copy code output. - Show prompt, Story and cases first. Record actual chat approval with --said (RUNBOOK §2), never invent it.
- Do not run
pdd lintbeforepdd test; test includes lint. Report only real output.