pdd-prompting

Installation
SKILL.md

PDD prompting

Each module's .prompt.md is the source; code implements it.

Core rules

  • Read RUNBOOK.md first, guide.md in full, and story-guide.md; skip runbook/*.md chapters unless a workflow step or lint error points to one.
  • Finish Prompt Space (pdd lint --local -> passing pdd test) before code; change no code and start no interactive pdd simulate unless asked.
  • One prompt per module: purpose, ## Domain decisions and 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 link kind: native-only adapters under ## Dependencies (RUNBOOK §21).
  • Linked .ui.svg is the layout spec: parts, words, order, ids and states. Check with pdd 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 $step or world only for persistence, with 1 observable 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 lint before pdd test; test includes lint. Report only real output.

Files

Installs
69
GitHub Stars
937
First Seen
Oct 27, 2026