aboutsummaryrefslogtreecommitdiff
path: root/.claude/commands/prompt-engineering.md
diff options
context:
space:
mode:
authorCraig Jennings <c@cjennings.net>2026-05-06 06:38:24 -0500
committerCraig Jennings <c@cjennings.net>2026-05-06 06:38:24 -0500
commitd4ff742e42832e889a4a3b10f6e8820f0a738010 (patch)
tree42b4be08aaf479df7a29cf7e94db374356af56c3 /.claude/commands/prompt-engineering.md
parentaa6924591127970d3241ab6b1a50f4bab457da27 (diff)
downloadrulesets-d4ff742e42832e889a4a3b10f6e8820f0a738010.tar.gz
rulesets-d4ff742e42832e889a4a3b10f6e8820f0a738010.zip
fix(commands): drop leftover name: frontmatter from converted commands
The conversion commit ran sed -i to strip the name: line, but the staged version from git mv was captured before the sed ran. Result: the commit shipped the original frontmatter, and the sed cleanup was sitting in the working tree. This commit lands the cleanup that should have been in aa69245.
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).
---