aiw-prompt-smithlisted

Author or repair prompting artifacts, including system prompts, CLAUDE.md, AGENTS.md/AGENT.md files, other skills, agent prompt files, and any file an agent loads at session start or opens at a step to learn what to do, whatever it is named, such as a README a mode file includes, a method page, or a reference an operator agent reads for a field. Use when writing any of these from scratch, when moving instructions from one file to another, and especially when one has produced a noticed failure and needs fixing at the cause rather than a narrow patch. Trigger whenever the user is drafting, reviewing, tightening, or debugging a system prompt, a project-instructions file, an agent-instructions file, or a skill, even if they don't say the word "prompt", e.g. "my CLAUDE.md keeps making it do X", "this skill over-triggers", "help me write instructions for the agent", "why does my agent ignore this rule". Prefer this skill over ad-hoc editing whenever the likely fix would otherwise be to just append another rule.
philippe-ths/ai-coding-workflow · ★ 0 · AI & Automation · score 66

Install: claude install-skill philippe-ths/ai-coding-workflow

# Prompt Smith Two jobs, one spine. Use this when **writing** a prompting artifact (system prompt, CLAUDE.md, AGENTS.md/AGENT.md, another skill, an agent prompt file, or any file an agent loads to learn what to do, whatever it is named) or **repairing** one after it produced a failure you noticed. Moving instructions from one file to another is repair: something about where they lived has failed. The governing idea is **altitude**. Every instruction sits at some level of generality, and most prompt problems are altitude errors. Too low and you write a brittle rule for the one case in front of you, and this is what breeds bloat. Too high and you write something so vague it steers nothing. Aim for the altitude where a competent role or a named concept does the work. This skill is deliberately small. If your edit makes an artifact longer without making it clearer, you are probably patching the instance, not fixing the class. ## Start here (both modes) Before writing or editing anything, get four answers. If you are repairing, get a fifth. 1. **Behaviour**: what should the artifact make the model do? 2. **Failure it prevents**: what goes wrong without this? If nothing, you do not need the instruction. 3. **One example**: a concrete good-vs-bad pair, ideally an awkward case rather than an easy one. 4. **Layer**: who reads this line, in which file, with what else in their context at the time? Altitude is about the line; layer is about where it lives, and it is a decision, not