doc-style-builderlisted
Install: claude install-skill th3r-dev/th3-skills
# Doc Style Builder
One method, seven skeletons, one theme. The value is **consistency**: a reader who has seen one document
of a type can find what they need in the next one without reading it, and a revision shows exactly what
changed.
## Work like this: gather → ground → summarize → confirm → build
The usual failure is a document that looks right and describes the system wrongly. Avoid it in this order:
1. **Gather.** Collect what the user points at: code, an OpenAPI file, logs, screenshots, notes, an older version of the document.
2. **Ground.** Check each fact against the real thing before writing it: the controller and DTO for an API,
the server's own output for a deploy, the running screen for a guide. When the user's notes and the
system disagree, the system wins. Tell the user about the conflict.
3. **Pick the reader and the type.** Decide who reads it (end user, integrator, operator, developer,
approver outside the team), then pick the type from `references/doc-types.md`. The reader decides
what to leave out.
4. **Summarize.** List the sections, the tables, and what changed since the last version, as a short
scannable list.
5. **Confirm.** Show the summary and wait for a go-ahead, unless the user said to just build it.
6. **Build.** Write the Markdown to the skeleton, then run the builder (below).
## House rules
- **Short and finished.** A document says what was done, where, and what the result was. Leave out the
working: raw logs, dead ends,