Pin Your CI Environment
Say which language version, lockfile, and secrets CI must use, so every run matches what you ship.
Where you'll practice this
One Promptles scenario teaches this principle directly.
Check Every Pull Request
Courtside has `npm run lint` and `npm test` scripts, but nothing runs them on pull requests, so contributors' changes reach Esther's review untested. You want GitHub Actions to check every pull request to `main`. Contributors often push three or four small fixes to one pull…
Other principles in Constraints
Define Component Boundaries
When splitting a component, give the decisions already made and say nothing on screen should change.
Define Inputs and Outputs
Say what goes in, what comes out, and what happens with bad input. Leave the inside to Claude.
Define the Business Logic
Turn business words into exact rules: the fields, the thresholds, and how they combine.
Deprecate Before Removing
Keep the old name working for a release, point to the replacement, and announce when it goes away.
Describe Edge Cases
Name the unusual cases you know about and what should happen in each.
Describe Type Contracts
Tell Claude the rules the code doesn't show, like allowed values and optional fields. It can work out the rest.