Market developer tools with technical content & community

Provides a structured method for writing technical tutorials, quickstarts, and code walkthroughs that actually work end-to-end. It defines four tutorial types by length and purpose - a 5-10 minute Quickstart for first success ASAP, a 20-45 minute Tutorial for learning a concept deeply, a 1-3 hour Workshop for a comprehensive project, and a Code Walkthrough for explaining existing code - and a fixed seven-part anatomy: title and meta with a time estimate, an overview previewing the final result, an explicit prerequisites check with verification commands, progressive build steps punctuated by "it works!" checkpoints, a "what you built" recap with complete code, a troubleshooting section, and next steps. Its layer-cake progressive-complexity model builds from a minimal running skeleton through a core feature, real data, error handling, and polish - showing progress rather than a 200-line complete file up front - and every code block must pass a five-point copy-paste checklist: runs standalone, includes all imports, references no undefined variables from unshown steps, is environment-agnostic across Mac, Linux, and Windows, and comments explain why rather than restating what the code does.

curl http://localhost:3000/api/users

Use it whenever the user wants a step-by-step tutorial, quickstart, getting-started guide, or walkthrough - not for pure reference documentation or API listings, which fall outside its scope. Before writing, it loads developer-audience context (skill level, tech-stack familiarity, environment, and why they're learning) from .agents/developer-audience-context.md, running the developer-audience-context skill first if that file doesn't exist. A checkpoint-every-3-5-steps rule creates motivation via visible confirmation of success (terminal output, a browser result, formatted JSON, or logs), and the troubleshooting section should proactively warn about known cross-platform pitfalls, such as Windows needing set/$env: instead of export for environment variables, rather than only reacting to reported errors.

Input is the target audience context and the working code or commands the tutorial teaches; output follows one of two full templates depending on tutorial type - a Quickstart template (Prerequisites, Install, Configure, Write Code, Run It, a "You Did It!" close with next-step links) or a Full Tutorial template (a metadata table for time, level, and prerequisites, a "What You'll Build" preview, numbered feature steps each ending in a checkpoint, complete final code, a troubleshooting section, and a "What You Learned" recap). A three-part quality checklist gates publication: code quality (every block runs unmodified, imports included, expected output shown, the .env pattern used for secrets), structure quality (explicit prerequisites, an accurate time estimate that's actually been tested, checkpoints every 3-5 steps, complete final code, troubleshooting covering likely errors), and accessibility (works on Mac, Linux, and Windows, commands valid in bash/zsh/PowerShell, correct file-path separators, no assumptions about pre-installed tools).

Names specific supporting tools by function: Octolens for mining Stack Overflow and GitHub issues to find the common questions and errors that should drive troubleshooting content, Replit/CodeSandbox for embedding runnable examples, Carbon/Ray.so for code screenshots, Excalidraw for architecture diagrams, and Terminalizer/Loom for recorded terminal sessions or video supplements. It hands off to four sibling skills: developer-audience-context for skill-level and environment detection, devrel-content for general technical-writing principles, developer-onboarding for optimizing time-to-first-success, and developer-seo for making tutorials discoverable via search.

Developer relations, technical writing, and DevEx teams producing tutorials, quickstarts, or code walkthroughs who want a tested structure - progressive complexity, verified checkpoints, cross-platform copy-paste-ready code, and proactive troubleshooting - rather than a wall of unverified prose and code snippets.