Summarize the Change for Review
Have Claude write the pull request for the reviewer: what changed, why, and how to test it.
Where you'll practice this
One Promptles scenario teaches this principle directly.
Open the Pull Request
The dark-mode toggle is done. `feature/dark-mode-toggle` is pushed with three commits that add the theme, put the switch on the settings page, and remember each person's choice between visits. Esther reviews it next. Clubs asked for dark mode because front-desk tablets glare…
Other principles in Output Format
Close the Design Loop
Send the built screen back into the design tool so designers review the real thing.
Describe the Destination
Describe where the data lands and the exact shape it needs there.
Make the Output Findable
Say where the result should live and how to title it so you and Claude can find it later.
Scope Your Commits
One logical change per commit, with a note saying what changed and why.
Show an Example
Show one real input and the exact output you want. One example settles what a description leaves open.
Show Examples in the Skill Body
Put two or three real examples in the skill. Examples carry further than rules.