new-guidelisted

# Skill: new-guide Create a new user-facing guide under `docs/guides/<quadrant>/<slug>.md`, following the [Diátaxis framework](https://diataxis.fr/). The framework itself is documented in this repo at `docs/guides/README.md` and the per-quadrant README in each subdirectory — read those for the *what*; this skill is the *procedure* for landing a new piece on the right side of the line. The load-bearing rule is **link out, don't blend**. When mid-draft you find yourself wanting to add theory inside a tutorial, or steps inside an explanation, that's the cue to write the adjacent piece separately and link. Mixing quadrants is the most common reason user docs frustrate everyone. ## When to invoke Before invoking, confirm: 1. The topic is *user-facing* — the reader is someone using the product, not a contributor reading the code. Contributor-facing material lives in `docs/architecture/` (current state) or `docs/adr/` (decisions). If it's spec-shaped, use `new-spec`. 2. The behavior being documented *already ships* — guides are living docs that must match current product behavior. If you're proposing a change, you want an RFC or a spec, not a guide. 3. You can name a real reader. "Someone might want to know X" isn't a reader; "an adopter who has installed the credential-brokers pack and needs to rotate their token" is. If any check fails, push back rather than proceeding. ## Procedure 1. **Settle the audience contract — gated checkpoint.** With nothing