# Docs

> Routes ccusage documentation impact work. Use when code or behavior changes affect README files, docs guides, VitePress navigation, screenshots, schema docs, or user-facing commands/options, and when auditing whether a change needs docs at all.

- Skill: `ccusage/docs` (Agent Skill)
- Install (CLI): `npx skillmds@latest add ccusage/docs`
- Raw SKILL.md: https://api.skillmd.com/api/skills/ccusage/docs/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Docs & Writing
- Author: ccusage (https://skillmd.com/u/ccusage)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/ccusage/docs

---


# ccusage Docs

Documentation impact is decided by what a user can observe, not by which
directory changed. Internal refactors, test-only changes, and skill maintenance
need nothing; anything that changes what a user can run, see, or configure needs
a pass over every surface, not only the guide page you started from:

- root `README.md`
- `apps/ccusage/README.md`
- the relevant `docs/guide/` pages and their cross-links
- VitePress navigation in `docs/.vitepress/`

Then read the local conventions before writing:

- `docs/README.md` - site structure, schema-copy behavior, `just docs::*` recipes.
- `docs/AGENTS.md` - screenshot placement and alt text, cross-linking, lint escapes.
- `apps/ccusage/AGENTS.md` - before touching README content that ships to npm.