Skip to content

bestdeejay-design/agent-skills / skills/docs-system

docs-system

Unverified

Meta-guide + router for documentation: the two branches (docs-product for 'why/what', docs-project for 'how'), the phase order, completeness levels L1/L2/L3, and the completeness checklist. Load a branch directly when the task is clearly product or engineering; load this skill for the big picture, ordering and completeness gates. Triggers: 'документация', 'набор документации', 'каталог документов', 'документация структура', 'полная документация', 'docs catalog', 'documentation structure', 'какую документацию писать'.

Docs System — meta-guide & router

This skill is now the meta-guide. The two branches live in focused skills: load them directly. Use this skill for the big picture: which docs to write, in which order, and how complete the set must be.

Two branches of documentation

BranchAnswersSkill
Product docs — «why» and «what»VISION → PRD → ROADMAP → FEATURESdocs-product
Project docs — «how»README/ENTRY/ARCHITECTURE/ADR/contracts/tests + REFERENCE mapdocs-project

Rule: product docs answer «why» and «what»; engineering docs answer «how». If a doc has no reader and no question it answers — it does not belong.

When to use this skill (router)

  • The task is about the documentation SYSTEM as a whole: what to write, in what order, how complete.
  • The phases / levels / completeness gates need to be applied.
  • The task is clearly product OR engineering → load the branch directly instead.

Order and levels

  • Phase order (when to write each doc): references/order.md.
  • Levels L1/L2/L3 (how deep a doc set must be for the system size): references/levels.md.
  • Completeness checklist (what a complete doc set looks like): references/completeness.md.

Golden rules

  • Nothing is written "from the end": VISION → PRD → ROADMAP → FEATURES, then engineering docs.
  • Contracts (OpenAPI/AsyncAPI) are written BEFORE code.
  • The map (REFERENCE.md) is written last — it describes everything above it.
  • Example monorepo that follows all rules: examples/example-monorepo/.
  • Skill roadmap: ROADMAP.md.

Removal plan

Keep as the meta-guide (not deprecated — it still carries order/levels/ completeness). The two branches are the focused entry points.

Boundaries

  • Do not use to author one document branch directly; route to docs-product or docs-project.

Evidence and completion gate

Ground recommendations in the supplied repository or brief. State assumptions, missing inputs, and unresolved risks. Return a concrete artifact or checklist with an owner/action for each open item, then verify that the result answers the requested goal rather than merely repeating the framework.

rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization.Stars: 467kUpdated Claude CodeCodexVerifiedInstall
academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file).Stars: 196kUpdated Claude CodeCodexUnverifiedInstall
doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.Stars: 196kUpdated Claude CodeCodexVerifiedInstall