スキル一覧に戻る
dhruvbaldawa

engineering-prompts

by dhruvbaldawa

A place for my claude code configs

11🍴 1📅 2026年1月24日
GitHubで見るManusで実行

SKILL.md


name: engineering-prompts description: 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.

Engineering Prompts


LEVEL 1: QUICKSTART ⚡

Foundation First (Always Apply):

  1. Clarity: Explicit instructions + success criteria
  2. Context & Motivation: Explain WHY, not just WHAT
  3. Positive Framing: Say what TO do, not what NOT to do

Then Assess:

  1. Simple task? → Stop here. Foundation is enough.
  2. Complex task? → Add advanced techniques sparingly
  3. Test & Iterate: Measure effectiveness, refine based on results

Key insight: The best prompt achieves goals with minimum necessary structure.


LEVEL 2: DIAGNOSTICS 🔧

Output Problems → Solutions:

ProblemSolution
Too genericAdd specificity + examples
Off-topicAdd context explaining goals
Wrong formatExamples or prefilling
Unreliable on complex tasksPrompt chaining
Unnecessary preamblesPrefill or "start directly with..."
Hallucinations"If unsure, acknowledge uncertainty"
Shallow reasoningChain of thought

Process Problems → Fixes:

MistakeFix
Over-engineeringStart minimal, add only what helps
Negative framingSay what TO do instead
No motivationExplain the WHY
No iterationTest, measure, refine

LEVEL 3: THE 12 TECHNIQUES 🛠️

Foundation (Always Apply)

TechniqueWhat It DoesCost
1. ClarityExplicit instructions, success criteriaMinimal
2. Context & MotivationExplain WHY you want somethingMinimal
3. Positive FramingSay what TO do, not what NOT to doMinimal
4. XML StructureSeparate sections in complex prompts~50-100 tokens

Note: XML is less essential with Claude 4.x - use when genuinely needed.

Advanced (Apply When Needed)

TechniqueWhen to UseCost
5. Chain of ThoughtReasoning, analysis, math2-3x output
6. Prompt ChainingMulti-step, complex tasksMultiple calls
7. Multishot ExamplesPattern learning, format200-1K each
8. System RoleDomain expertise neededMinimal
9. PrefillingStrict format requirementsMinimal
10. Long Context20K+ token inputsBetter accuracy
11. Context BudgetRepeated use, conversations90% savings
12. Tool DocsFunction calling, agents100-500/tool

LEVEL 4: DESIGN CHECKLIST 📋

Before Writing:

  • Core task clear?
  • Output format defined?
  • Constraints known? (latency/cost/accuracy)
  • One-off or repeated use?

Complexity Assessment:

  • Simple (extraction, Q&A) → Foundation only
  • Medium (analysis, code gen) → + CoT, examples
  • Complex (research, novel problems) → + Chaining, role

Cost Optimization:

  • Cache system prompts + reference docs (90% savings)
  • Batch non-urgent work (50% savings)
  • Skip CoT for simple tasks (saves 2-3x)

Deliverable:

  • Prompt + techniques used + rationale + token estimate

LEVEL 5: ADVANCED TOPICS 🚀

Tool Integration

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

Context Management

Prompt Caching:

  • Cache: System prompts, reference docs, examples
  • Savings: 90% on cached content
  • Write: 25% of standard cost
  • Read: 10% of standard cost

Long Context Tips:

  • Place documents BEFORE queries
  • Use XML tags: <document>, <source>
  • Ground responses in quotes
  • 30% better performance with proper structure

Token Optimization

Reducing Token Usage:

  • Concise, clear instructions (no fluff)
  • Reuse examples across calls (cache them)
  • Structured output reduces back-and-forth
  • Tool use instead of long context when possible

Cost-Specific Anti-Patterns

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.


LEVEL 6: REFERENCES 📚

Deep Dive Documentation

Detailed Technique Catalog:

  • reference/technique-catalog.md - Each technique explained with examples, token costs, combination strategies

Real-World Examples:

  • reference/examples.md - Before/after pairs for coding, analysis, extraction, agent tasks

Research Papers:

  • reference/research.md - Latest Anthropic research, benchmarks, best practices evolution

スコア

総合スコア

50/100

リポジトリの品質指標に基づく評価

SKILL.md

SKILL.mdファイルが含まれている

+20
LICENSE

ライセンスが設定されている

0/10
説明文

100文字以上の説明がある

0/10
人気

GitHub Stars 100以上

0/15
最近の活動

3ヶ月以内に更新がある

0/10
フォーク

10回以上フォークされている

0/5
Issue管理

オープンIssueが50未満

+5
言語

プログラミング言語が設定されている

+5
タグ

1つ以上のタグが設定されている

0/5

レビュー

💬

レビュー機能は近日公開予定です