Best practices for writing and maintaining documentation in this repository. Use this skill when writing or updating files in docs/, adding Mermaid diagrams, or creating README and onboarding documentation.
Use up-to-date library and framework docs via Context7 MCP instead of training data. Activates for setup questions, API references, code examples, or when the user names a framework (e.g. React, Next.js, Prisma).
Use up-to-date library and framework docs via Context7 MCP instead of training data. Activates for setup questions, API references, code examples, or when the user names a framework (e.g. React, Next.js, Prisma).
Use when a task concerns the project's documentation tree itself — creating it where none exists, updating or amending documents in it, or migrating/reorganising an existing docs layout — and you must pick which specialized documentation skill covers it. This gateway routes; read manifest.json to choose a member and open that member's SKILL.md. Not for writing prose inside a document that already has a home.
Write and maintain the /docs knowledge base. Apply when adding or changing a page under /docs, or when a code change makes existing documentation wrong.
Producing technical documentation for a named reader — README, API reference, runbook, architecture doc, or onboarding guide. Covers per-type skeletons, audience targeting, and keeping docs current instead of stale.
Enforce minimum documentation standard across uFawkes* repos. Use when auditing a repo before release, onboarding a new repo to the suite, or implementing roadmap item 0.6 (cross-repo README links). Directly supports DORA AI Capability 3 and the 2023 DORA finding that documentation quality amplifies all technical capabilities.
Expert technical documentation architect specializing in developer experience, API portals, interactive documentation, and documentation-as-code strategies.
Durable Documentation
**Status:** experimental.
Governs durable, edited repository knowledge. Unlike the append-only log, documentation is actively edited as plans and decisions evolve.
## Directory Structure
A project managed by Agent
Write and maintain the /docs knowledge base. Apply when adding or changing a page under /docs, or when a code change makes existing documentation wrong.
Documentation standards and required templates for this project. Use this skill whenever producing any project document — feature plans, handoffs, release notes, capability documentation, production release records, or incident reports. Also trigger it when a plan, release, deployment, or incident occurs without documentation, because in this project undocumented work is unfinished work.
Plain text files in a repository that tell a coding agent how the project works: commands to run, conventions to follow and things to avoid. CLAUDE.md, AGENTS.md, cursor rules and skills are the common kinds.
CLAUDE.md or AGENTS.md?
CLAUDE.md is read by Claude Code. AGENTS.md is an open format that Codex, Cursor and other agents read. Many projects keep one and point the other at it.
What is a skill?
A folder with a SKILL.md that describes one capability, such as filling PDFs or reviewing code. The agent loads it only when the task calls for it.
Can I search my own team's files too?
Your agents already can, over MCP, limited to the files you're allowed to read. Searching them from this page is coming.