Match the Part to the Job
Pick the part by who starts it: Claude (skill), a person (slash command), every event (hook), another system (MCP server).
Where you'll practice this
One Promptles scenario teaches this principle directly.
Match the Part to the Job
The shipkit brief is approved and lists five behaviors in `brief-behaviors.md`. A plugin can bundle several kinds of parts, and each kind starts in a different way. Dana's draft plan makes all five behaviors into skills, including the lint check (an automatic style and error…
Other principles in Clarity
Ask What's Missing
Spot the decisions only you can make, pick a default for each, and state them as assumptions Claude can check.
Be Specific About the Outcome
Describe the result you want with a default and one example. Then you and Claude agree on what done looks like.
Combine Context with Action
Say what's happening now and what you want changed, in the same prompt.
Define What Done Looks Like
Say what finished means: the cases that must work, what must not change, and how you'll check.
Describe What, Not How
Tell Claude the result you want and show one example. Leave the steps to Claude.
Invoke the Right Skill
When a skill fits the job, call it by name and give it what's new. When none fits, just ask plainly.