What problem does it solve?
Technical docs often read as vague, jargon-heavy, or marketing-flavored prose that buries the useful information. This Skill enforces a concrete style guide derived from Modal's documentation voice so drafts and revisions come out direct, confident, and example-first.
Core Features & Use Cases
- Style-guided drafting: Write new docs, guides, and tutorials following rules for voice, structure, terminology, punctuation, code examples, and formatting.
- Prose revision: Rewrite existing documentation toward second-person address, minimal jargon, no em-dashes, and backticked code identifiers.
- Full rule reference: Consult
references/style-guide.md for the complete rule set with real examples as evidence.
- Use Case: You draft a getting-started guide for your SDK and want it to read like Modal's docs: open with the concept, show a runnable example early, address the reader as "you", and cut vague intensifiers like "seamlessly".
Quick Start
Ask the assistant to draft or rewrite a documentation page using the good-docs-writing style guide, for example: "Rewrite this tutorial intro in the Modal docs voice."
