About w-docs
w-docs is a repository skill for updating documentation alongside code changes. It helps agents place explanations in the right existing documentation layer and avoid duplicating project information.
Key features
- 01Selects the matching documentation section
- 02Updates canonical MDX topic pages
- 03Limits README edits to setup and run details
- 04Updates agent rules only when constraints change
- 05Avoids unrequested file moves and commits
Use cases
- 01Documenting changed behavior or architecture
- 02Updating setup instructions after script changes
- 03Organizing proposed documentation file moves
Install
Copy the command and run it in a terminal.
$
npx skills add https:/ / github.com/ blockmatic/ basilic-skills --skill w-docsAfter installing, type/w-docsin Claude Code to confirm it loaded.
Details
From the project READMEDocument the current code or feature. Follow the consuming repo's docs and README rules. Do not commit unless asked. Durable information architecture belongs in existing MDX; do not invent a second sitemap.
Write to the layer that owns the change:
| Layer | Role | Update when |
|---|---|---|
Technical docs (path in AGENTS.md) | Architecture, ADRs, how-to | Behavior, architecture, commands, conventions, or workflow changed |
| Agent rules | Short constraints | A convention the agent must not violate changed |
| Nearest README | How to run this app/package; links only | Scripts, setup, or package purpose changed |
Inline comments only when the code is otherwise misleading. Do not copy MDX into rules or READMEs. Do not @-attach MDX.
- Identify the matching docs section, then an existing topic page (create a page only if none fits).
- Write or patch MDX if the canonical explanation changed.
- Patch README only for run/setup/scripts; link the MDX.
- Patch the glob-matched rule only if a constraint changed.
- For mechanical file or doc moves: propose the smallest from/to list grouped by related files; drop folder-name prefixes inside groups. Save only if the user gave a path. Do not move files unless they also asked to implement.
Comments
Markdown supported