content-documentationlisted

# content-documentation — Technical documentation skeleton Goal: give the reader a **reproducible** path from their starting state to the goal. Not theory, not an essay — a step-by-step set of instructions where every step is verifiable. Before starting, read: - `~/.claude/rules/content-voice.md` - `~/.claude/rules/content-formatting.md` — the tutorials section ## Step 1. Define the scope Ask: - **the tutorial's goal**: "after reading this, the reader will be able to _<verb + result>_" - examples: "deploy a Postgres cluster with replication across 3 nodes," "set up OAuth login via Google in an Express app," "measure heap allocations in a Go service" - **the reader's starting state**: what they have, what's assumed - **the final state**: what should be working at the end - **the platform / stack**: versions, OS, cloud If the goal is vague ("a tutorial on k8s") — **stop and help narrow it down to specifics**. A tutorial "on k8s" is impossible — "deploy minikube + deploy a stateless API + expose via Ingress" is possible. ## Step 2. Build the skeleton ```markdown # <Title: verb + result> > **Goal:** after completing this tutorial you'll be able to _<specifically>_. > **Time:** ~X minutes. > **Level:** beginner / intermediate / advanced. ## What you'll need - <tooling: version> - <tooling: version> - <access: where to get it> - <cloud/environment, if applicable> ## Step 1. <Verb + what> <1-2 lines of context: what we're doing and why.> ```<lang> <command> ``` **Che