Ship Team Defaults in Project Settings
Commit the marketplace and plugin to shared project settings, and note any one-time install step.
Where you'll practice this
One Promptles scenario teaches this principle directly.
Roll It Out to the Team
On Monday Priya committed the change below to `acme/web-app/.claude/settings.json` (the settings everyone who opens the repo shares) and posted in #eng that shipkit is now on for the whole repo. By Thursday about half the team still can't run `/shipkit:notes`, and nobody sees an…
Other principles in Context
Declare the Tools You Need
Name the connected source and what to do if it's unreachable. Access itself comes from the connection, not the prompt.
Describe Before You Prescribe
Say what happens now and what should happen instead, so Claude changes only the gap.
Describe Relationships
Say how your data connects and what happens on delete. Those are business decisions only you can make.
Explain the Integration Point
Describe the handoff: what starts it, what crosses, and what happens on a failure or a duplicate.
Follow an Existing Pattern
Point at something already done right and ask Claude to match it and reuse it.
Map to Real Components
Ask Claude to reuse the components you already ship, not build look-alike copies.