api-documentation
fabioc-aloha/alex-cognitive-architecture/.github/skills/api-documentation/SKILL.md
Technical documentation, API references, user guides, and docs-as-code workflows.
One search for your own team's files and the public ecosystem. See how real projects write their agent instructions, and bring the good ideas home.
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
fabioc-aloha/alex-cognitive-architecture/.github/skills/api-documentation/SKILL.md
Technical documentation, API references, user guides, and docs-as-code workflows.
gologo13/agent-skills/skills/add-documentation/SKILL.md
Add comprehensive documentation for the current code/feature and format it according to the ...; keywords: api, architecture, error. Use only on explicit request; skip in routine implementation discussions.
leaf76/agent-skills/api-documentation/SKILL.md
Automatically generate and maintain API documentation from code. Supports OpenAPI, AsyncAPI specifications and interactive documentation. Use when adding new endpoints, updating API contracts, or ensuring documentation consistency.
PengEjeen/claude_skills/skills/documentation-gen/SKILL.md
기술 문서를 자동 생성하고 관리합니다. "문서화", "README 작성", "docs 생성", "JSDoc", "API 문서", "변경 로그", "CHANGELOG", "온보딩 가이드", "기술 문서 업데이트" 등의 요청 시 사용합니다. README, API 문서, ADR, CHANGELOG, 온보딩 가이드를 코드베이스 분석 기반으로 생성합니다. (개발 일지·ADR·문제 해결 기록은 dev-journal 스킬 참조)
SKY-lv/api-documentation/SKILL.md
API文档助手。生成API文档、编写Swagger/OpenAPI、示例代码。使用场景:(1) 文档生成,(2) Swagger配置,(3) 示例代码,(4) 版本管理。
techmefr/mentis/skills/documentation-adr/SKILL.md
Use when a significant architecture decision that is hard to walk back is taken: the ADR template, what belongs there rather than in inline docs, and the never-delete-always-supersede rule.
nilecui/SkillsBase/.cursor/skills/documentation-generation/SKILL.md
Create comprehensive technical documentation including API docs, component libraries, README files, architecture diagrams, and developer guides using tools like JSDoc, Storybook, or Docusaurus. Use when documenting APIs, creating component documentation, writing README files, generating API references, documenting architecture decisions, creating onboarding guides, maintaining changelogs, documenting configuration options, or building developer documentation sites.
gilsmt/skills/.agents/skills/code-documentation/SKILL.md
On writing code comments and documentation for functions and modules.
gspencergoog/skills/skills/code-documentation/SKILL.md
Writes and reviews code documentation: dartdoc, JSDoc, Python docstrings, and implementation comments, with per-language conventions for Dart, Python, and TypeScript. Use when writing new code or features, documenting public APIs, improving existing docstrings or comments, or checking a change for missing or unhelpful documentation. Don't use for prose documents such as READMEs, design docs, or PR descriptions (use write-prose).
illodev/taiga-mcp/.github/skills/wiki-documentation/SKILL.md
Manage Taiga wiki pages and documentation using MCP tools. Use when: creating wiki pages, updating documentation, managing wiki links and navigation, tracking wiki changes, organizing project documentation.
muhamedroshan/Odoo-Agent-Skills-Functional/skills/odoo-documentation/SKILL.md
Produce and maintain the complete Markdown documentation set for an Odoo implementation - requirements, questions and decisions, fit-gap matrix, technical limitations, demo DB configuration log, project phases, detailed workflow explanations (why and how), step-by-step review guide and customization specifications - in the client's confirmed language(s).
pepebot-space/skills/code-documentation/SKILL.md
Writing effective code documentation - API docs, README files, inline comments, and technical guides. Use for documenting codebases, APIs, or writing developer guides.
saemihemma/lead-producer-oss/.claude/skills/team-documentation/SKILL.md
Documentation team: guides, API docs, ADRs, and knowledge-base work with scope control and audience fit.
Suuunboy/code-documentation-skill/skills/code-documentation/SKILL.md
Write, review, and audit code documentation to the standard the language and the project actually use — Python docstrings (PEP 257, Google, NumPy, reST), C and C++ comment blocks (Doxygen, kernel-doc), plus READMEs and API reference docs. Use this skill whenever the user asks to document code, add or fix docstrings or comments, explain a module so other developers can use it, write or refresh a README or API reference, check documentation coverage, or judge whether existing docs are still accurate — including short requests like "document this", "add comments here", "describe this module for the team", or handing over a file and asking what its docs are missing.
yogsoth-ai/knowledge-structuring/skills/loop-documentation/SKILL.md
SOP for documenting a feedback loop — classify, describe dynamics, identify break points.
PrefectHQ/fastmcp-ts/.claude/skills/writing-documentation/SKILL.md
Use when writing, revising, reorganizing, or reviewing technical documentation — concept guides, feature docs, API references, developer-tool docs, tutorials, or docstrings that compile into user-facing docs. Covers both how to teach a single concept on one page and how to keep an entire documentation set coherent as it grows. Also covers short user-facing product text — UI copy, error messages, empty states, tooltips, and help text — which follows ASD-STE100 Simplified Technical English conventions (see "User-Facing Text"). Trigger whenever a task involves producing or improving end-user or developer-facing documentation, or when writing product strings a user will read. Not for README files (use crafting-effective-readmes), conversational walkthroughs of existing code or changes (use explain), or inline code comments.
shinpr/ai-coding-project-boilerplate/.claude/skills-en/documentation-criteria/SKILL.md
Determines which PRD, ADR, UI Spec, Design Doc, and Work Plan a change requires and where each is stored. Use when deciding documentation scope or creating or reviewing a technical document.
shinpr/ai-coding-project-boilerplate/.claude/skills-ja/documentation-criteria/SKILL.md
変更に必要なPRD、ADR、UI Spec、Design Doc、作業計画書と、それぞれの保存先を判定する。ドキュメントの範囲を決める時、または技術ドキュメントを作成・レビューする時に使用。
shinpr/ai-coding-project-boilerplate/.claude/skills-zh-CN/documentation-criteria/SKILL.md
判断某项变更需要哪些 PRD、ADR、UI 规范(UI Spec)、设计文档(Design Doc)和工作计划,以及每种文档的存放位置。用于决定文档范围,或创建/评审技术文档时使用。
jackmusick/bifrost/.claude/skills/bifrost-documentation/SKILL.md
Refresh Bifrost product documentation by re-capturing screenshots and (optionally) authoring missing pages. Trigger phrases - "refresh docs", "update screenshots", "/bifrost-documentation", "rebuild docs site". Has three modes - bootstrap (one-shot manifest generation, mandatory first run), diff (default - only refresh entries whose Bifrost source changed), full (re-capture and re-author everything).
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 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.
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.
Your agents already can, over MCP, limited to the files you're allowed to read. Searching them from this page is coming.