docs-decisions

Create a lowercase, descriptively named Markdown file in docs/decisions/ using the decision template: state the decision first, then context, consequences, and verification steps. Register every new record in docs/decisions/README.md.

Run bun run build, types:check, lint, lint:links, and test from the docs/ directory. Branch docs work from next and target PRs at next, and use lint:links whenever content links changed.

Update an existing record when a docs change alters an accepted decision. Read the current record, patch the decision or add a dated note, update the decisions index, and verify links with bun run lint:links.

No. This skill is scoped to documentation work where docs are the main deliverable, including docs content, Fumadocs configuration, changelogs, and automation prompts. SDK runtime changes fall outside its scope.

Use relative site links instead of absolute URLs, prefer cURL for API examples, and change generated OpenAPI, toolkit, and meta-tool data only through their scripts. TypeScript code blocks are type-checked by the docs build via Twoslash.