← ClaudeAtlas

write-prompt-guidelisted

Produce a pack-specific PROMPT_GUIDE.md that teaches end users what to type to get a good run out of one Agent Skill pack, from that pack's own SKILL.md, README, and open issues. Use when a skill pack has agent-facing docs but nothing telling a human how to invoke it well.
wakqasahmed/ai-engineering-workflow-skills · ★ 2 · AI & Automation · score 68
Install: claude install-skill wakqasahmed/ai-engineering-workflow-skills
# Write a Prompt Guide A skill pack's `SKILL.md` tells an **agent** what to do. Its `README.md` tells a reader what the pack **is**. Neither tells a **user** what to type, what context to hand over before the run starts, or which of the pack's known limitations they have to compensate for by hand. That gap is what this skill fills, for one named target pack at a time. This is not a prompt-engineering tutorial. A generic "be specific, give examples" page helps nobody who already installed the pack. The deliverable is specific to one pack: its real inputs, its real invocation triggers, its real output shape, and its real open bugs. ## Evidence basis The structure below is not invented. It is the intersection of the official prompting documentation of four model/agent providers — Anthropic, OpenAI, Google, and BytePlus — recorded with URLs and per-claim attribution in this repo's [`SOURCES.md`](../../../SOURCES.md) (`ANTHROPIC-PROMPTING-01`, `OPENAI-PROMPTING-01`, `GOOGLE-PROMPTING-01`, `BYTEPLUS-PROMPTING-01`). Two techniques appear in all four independently and a third in two of them independently, which is why these three are the non-negotiable spine of every guide this skill produces: 1. **Structural separation of instructions, context, examples, and input** — Anthropic via XML tags (`<instructions>`, `<context>`, `<input>`), OpenAI and BytePlus via the same four Markdown sections (`# Identity`, `# Instructions`, `# Examples`, `# Context`), Google via "XML tags or Mark