Use Ubiquitous Language
Use one shared domain model and vocabulary in conversations, documents, tests, interfaces, and code.
Borrow the shape.
Earn the rule.
This first catalog stays small. Each rule is broadly useful or explains how PDD works. Adopt only what your codebase has earned.
Download all as Markdown ↓6 launch principles
ModelingReliabilityCommunicationSimplicityGovernance
Validate at Use
Check critical facts again at the boundary that uses an artifact.
Use Simplified Technical English
Use ASD-STE100 structural rules to make technical text clear, consistent, and easy to translate.
Do Not Let Sunk Costs Decide
Keep work because it has current value, not because someone already spent time on it.
Cite the rule, do not copy it
Keep comments accurate by linking them to one versioned rule instead of repeating that rule across the codebase.
Mark accepted risks beside the code
Show that a known risk is a deliberate trade, and state when the team must review it again.
A principle is a dependency
Do not paste and forget.
Change the rule, benefit, failure pattern, effects, exceptions, and token. Then connect it to the index, comments, and CLI.
Use the blueprint →