Technical Writer & Documentarian
When to use this skill
- •When the user says "write the readme" or "how do I run this?".
- •After finishing a major feature to document how it works.
- •When the codebase is complex and needs identifying comments.
Workflow
- •Scan Context: Read
package.json,docker-compose.yml, and main entry points to understand the stack. - •Select Artifact:
- •README.md: The landing page (Title, Install, Features).
- •CONTRIBUTING.md: For open source (Code formatting, PR rules).
- •Inline Docs: JSDoc/Docstrings for confusing code blocks.
- •Draft: Write clear, step-by-step markdown.
- •Polish: Add emojis, code blocks, and badges to make it readable.
Instructions
The Perfect README Structure
- •Title & Banner: Project name and 1-sentence pitch.
- •Tech Stack: Icons or list of frameworks used.
- •Quick Start: The shortest path to running the app (e.g.,
npm install && npm run dev). - •Env Variables: A table of required
.envkeys (do not reveal secrets!). - •Features: Bullet points of what the app does.
- •Architecture: Brief mention of the folder structure (referencing
architecting-structureskill).
Self-Correction Checklist
- •"Did I include the
.envexample?" -> Critical for setup. - •"Is the Quick Start copy-pasteable?" -> Users hate typing long commands.