← ClaudeAtlas

doc-style-builderlisted

Write and build documentation for any work product (an API, a deploy or update, a system, a feature, a release, a test round) in one consistent house style, and output a matching PDF + DOCX from a single Markdown source. Use whenever the user wants to document, write up, report on, or hand over something: "write an API spec", "เขียนเอกสาร", "ทำรายงานอัปเดต", "document this endpoint", "make a user guide", "write the README", "changelog for this release", "system overview for onboarding", "report for the client", "export as PDF and Word", or asks to make an existing document match the house style. Covers seven document types (report/change record, API reference, user guide/quickstart, FAQ, architecture/onboarding, README, changelog) with fixed skeletons, and a theme of TH Sarabun fonts, a plain black/grey palette, and green/yellow/red change highlighting. Thai-first headings; English works the same way.
th3r-dev/th3-skills · ★ 2 · Data & Documents · score 66
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,