Agent skill · writing content · vercel
write-guide
Generates technical guides that teach real-world use cases through progressive examples. **Auto-activation:** User asks to write, create, or draft a guide or tutorial. Also use when converting feature documentation, API references, or skill knowledge into step-by-step learning content. **Input sources:** Feature skills, API documentation, existing code examples, or user-provided specifications. **Output type:** A markdown guide with YAML frontmatter, introduction, 2-4 progressive steps, and next steps section.
Why this skill is useful
Provides a structured template and specific guidelines for creating technical guides that the AI wouldn't reliably generate on its own.
What it needs
About 3k tokens when loaded. Last updated 2026-08-07. 141,663 stars on the source repository.
What this skill does
Writing Guides Goal Produce a technical guide that teaches a real-world use case through progressive examples. Concepts are introduced only when the reader needs them. Each guide solves one specific problem. Not a category of problems. If the outline has 5+ steps or covers multiple approaches, split it. Structure Every guide follows this arc: introduction, example setup, 2-5 progressive steps, next steps. Each step follows this loop: working code → new requirement → friction → explanation → resolution → observable proof. Sections: introduction (no heading, 2 paragraphs max), ## Example (what we're building + source link), ### Step N (action-oriented titles, 2-4 steps), ## Next steps (summary + related links). Headings should tell a story on their own. If readers only saw the headings, they'd understand the guide's takeaway. Template tsx filename="path/to/file.tsx" // Minimal working code Workflow 1. Research: Check available skills for relevant features. Read existing docs for context and linking opportunities. 2. Plan: Outline sections. Verify scope (one problem, 2-4 steps). Each step needs a friction point and resolution. 3. Write: Follow the template above. Apply the rules below. 4. Review: Re-read the rules, verify, then present. Rules 1. Progressive disclosure. Start with the smallest working example. Introduce complexity only when the example breaks. Name concepts at the moment of resolution, after the reader has felt the problem. Full loop: working → new requirement → something breaks → explain why → name the fix → apply → verify with proof → move on. 2. Show problems visually. Console errors, terminal output, build warnings, slow-loading pages. "If we refresh the page, we can see the component blocks the response." 3. Verify resolutions with observable proof. Before/after comparisons, browser reloads, terminal output. "If we refresh the page again, we can see it loads instantly." 4. One friction point per step. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills vercel/write-guide