Engineers effective prompts using systematic methodology. Use when designing prompts for Claude, optimizing existing prompts, or balancing simplicity, cost, and effectiveness. Applies progressive disclosure and empirical validation to prompt development.
Engineers effective prompts using systematic methodology. Use when designing prompts for Claude, optimizing existing prompts, or balancing simplicity, cost, and effectiveness.
/plugin marketplace add dhruvbaldawa/ccconfigs/plugin install essentials@ccconfigsThis skill inherits all available tools. When active, it can use any tool Claude has access to.
reference/examples.mdreference/research.mdreference/technique-catalog.mdFoundation First (Always Apply):
Then Assess:
Key insight: The best prompt achieves goals with minimum necessary structure.
Output Problems → Solutions:
| Problem | Solution |
|---|---|
| Too generic | Add specificity + examples |
| Off-topic | Add context explaining goals |
| Wrong format | Examples or prefilling |
| Unreliable on complex tasks | Prompt chaining |
| Unnecessary preambles | Prefill or "start directly with..." |
| Hallucinations | "If unsure, acknowledge uncertainty" |
| Shallow reasoning | Chain of thought |
Process Problems → Fixes:
| Mistake | Fix |
|---|---|
| Over-engineering | Start minimal, add only what helps |
| Negative framing | Say what TO do instead |
| No motivation | Explain the WHY |
| No iteration | Test, measure, refine |
| Technique | What It Does | Cost |
|---|---|---|
| 1. Clarity | Explicit instructions, success criteria | Minimal |
| 2. Context & Motivation | Explain WHY you want something | Minimal |
| 3. Positive Framing | Say what TO do, not what NOT to do | Minimal |
| 4. XML Structure | Separate sections in complex prompts | ~50-100 tokens |
Note: XML is less essential with Claude 4.x - use when genuinely needed.
| Technique | When to Use | Cost |
|---|---|---|
| 5. Chain of Thought | Reasoning, analysis, math | 2-3x output |
| 6. Prompt Chaining | Multi-step, complex tasks | Multiple calls |
| 7. Multishot Examples | Pattern learning, format | 200-1K each |
| 8. System Role | Domain expertise needed | Minimal |
| 9. Prefilling | Strict format requirements | Minimal |
| 10. Long Context | 20K+ token inputs | Better accuracy |
| 11. Context Budget | Repeated use, conversations | 90% savings |
| 12. Tool Docs | Function calling, agents | 100-500/tool |
Before Writing:
Complexity Assessment:
Cost Optimization:
Deliverable:
When to use MCP tools during prompt engineering:
Need latest practices?
└─ mcp__plugin_essentials_perplexity
Complex analysis needed?
└─ mcp__plugin_essentials_sequential-thinking
Need library docs?
└─ mcp__plugin_essentials_context7
Prompt Caching:
Long Context Tips:
<document>, <source>Reducing Token Usage:
❌ Ignoring caching - Not leveraging repeated content (90% savings lost) ❌ Over-requesting CoT - Chain of thought for simple tasks (2-3x wasted) ❌ Redundant examples - 5 examples when 2 suffice ❌ No batching - Real-time calls for non-urgent work (50% savings lost)
See LEVEL 2: Diagnostics for general fixes.
Detailed Technique Catalog:
reference/technique-catalog.md - Each technique explained with examples, token costs, combination strategiesReal-World Examples:
reference/examples.md - Before/after pairs for coding, analysis, extraction, agent tasksResearch Papers:
reference/research.md - Latest Anthropic research, benchmarks, best practices evolution