aboutsummaryrefslogtreecommitdiff
path: root/.claude/commands/prompt-engineering.md
diff options
context:
space:
mode:
Diffstat (limited to '.claude/commands/prompt-engineering.md')
-rw-r--r--.claude/commands/prompt-engineering.md1
1 files changed, 0 insertions, 1 deletions
diff --git a/.claude/commands/prompt-engineering.md b/.claude/commands/prompt-engineering.md
index d566286..f2c240a 100644
--- a/.claude/commands/prompt-engineering.md
+++ b/.claude/commands/prompt-engineering.md
@@ -1,5 +1,4 @@
---
-name: prompt-engineering
description: Craft prompts (commands, hooks, skill descriptions, sub-agent instructions, system prompts, one-shot requests to other LLMs) that do what they're meant to and resist common failure modes. Covers four moves that determine whether a prompt holds up: classify the prompt type (discipline-enforcing / guidance / collaborative / reference) to pick the right tone and techniques; apply the persuasion framework appropriate to that type (seven principles from Meincke et al. 2025, including which to avoid — notably Liking, which breeds sycophancy); match task fragility to degrees of freedom (high/medium/low); and spend the context window like a shared resource. Also contains a brief reference for classical techniques (few-shot, chain-of-thought, system prompts, templates). Use both in design mode (asking for help writing a new prompt from scratch) and critique mode (paste a draft, get it rewritten to resist common failure modes). Do NOT use for prose editing unrelated to LLM prompts (use a writing skill), for implementing application code that uses an LLM (different scope), or for content moderation / prompt-injection defense (adjacent but separate domain).
---