Show an Example
Show one real input and the exact output you want. One example settles what a description leaves open.
Where you'll practice this
2 Promptles scenarios teach this principle directly. Each one drops you into a real engineering ticket and asks you to write the prompt you'd send to Claude Code.
Show the Receipt
Copper Kettle runs a café cart at the weekend farmers market, and its app prints receipts with `printReceipt(items)` in `receipt.js`. Today every item lands on one line, like `Coffee: 3.5, Bagel: 2.25`. Rosa, the owner, sketched the receipt she wants on a napkin: each item on…
Sort Replies with Claude
Brightdesk's outbound campaigns get a few hundred email replies a day, and Wen Zhao, the SDR (the rep who follows up on campaign replies), sorts them by hand into five piles: interested, not interested, out of office, unsubscribe, and wrong person. You want a script that sends…
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 Examples in the Skill Body
Put two or three real examples in the skill. Examples carry further than rules.
Specify Output Format
Say what form the result should take: how Claude answers you, and what the thing it builds should produce.