Declare the Tools You Need
Name the tool or MCP server by name, and say what to do if it isn't reachable.
Where you'll practice this
3 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.
Declare the Tools You Need
A support ticket says a handful of orders ended up stuck in a `failed` status last night. You want the assistant to query the production Postgres database (read-only) and show you the 10 most recent failed orders so you can triage. Your team has a Postgres MCP server already…
Tools the Skill Needs
You're authoring a `triage` skill that helps maintainers organize the issue tracker on a GitHub repo. The skill needs to: list open issues with no labels, read the bodies of stale issues, apply a small vocabulary of labels (`bug`, `feature`, `question`, `needs-repro`,…
When MCP Goes Dark
You're running a production incident: a customer reported a payment failure, and you want the agent to (a) pull the failing charge from the Stripe MCP and (b) post a status comment to the linked Linear issue. Both MCP servers are flaky in this environment — the Stripe MCP has…
Other principles in Context
Describe Before You Prescribe
Describe the Data Shape
Claude can't clean data it can't picture.
Explain the Integration Point
Keep Memory Reusable
Save patterns and preferences that survive across sessions; never save snapshots of finished work.
Map to Real Components
Use Code Connect so it reuses your components, not new markup.
Name the Framework