Find the best CLAUDE.md, AGENTS.md and Claude skills

nafeeurSkill

documentation

nafeeur/MaskShift/skills/documentation/SKILL.md

Write accurate user, operator, API, and architecture documentation grounded in the implemented product.

Often used withcreate-media-pack·response-style·project-preferences

ole-techwoodSkill

documentation

ole-techwood/Skills/skills/documentation/SKILL.md

Records decisions and documentation. Use when making architectural decisions, changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.

Often used withcreate-media-pack·response-style·project-preferences

paruffSkill

documentation

paruff/uFawkesAI/.agents/skills/documentation/SKILL.md

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.

Often used withcreate-media-pack·response-style·project-preferences

ronrefaelSkill

documentation

ronrefael/sonde/.claude/skills/documentation/SKILL.md

Documentation generation workflow covering API docs, architecture docs, README files, code comments, and technical writing.

Often used withcreate-media-pack·response-style·project-preferences

stijnvanhulleSkill

documentation

stijnvanhulle/agents/.agents/skills/documentation/SKILL.md

Writes or reviews developer documentation in the project style with SEO guidance. Use when adding, changing, or removing content in a docs page, a README, an option or API description, a guide, a FAQ, or a blog post, even when the request only says "document this".

Often used withcreate-media-pack·response-style·project-preferences

homarr-labsSkill

documentation-sync

homarr-labs/homarr/.agents/skills/documentation-sync/SKILL.md

Write Homarr docs only when users need information to set up, use, or troubleshoot the app. Skip routine, obvious, or self-explanatory changes.

alizafarbatiSkill

documentation

alizafarbati/opencode-agents-mcp/skills/documentation/SKILL.md

Expert technical documentation architect specializing in developer experience, API portals, interactive documentation, and documentation-as-code strategies.

Often used withcreate-media-pack·response-style·project-preferences

allanninalSkill

documentation

allanninal/claude-code-skills/skills/documentation/SKILL.md

Generate professional technical documentation with ASCII diagrams, flowcharts, architecture visualizations, and industry-standard templates

Often used withcreate-media-pack·response-style·project-preferences

AndreiCocanSkill

documentation

AndreiCocan/skills/skills/documentation/SKILL.md

Documents code the way the language's own toolchain expects: the native doc format per language, contract-first doc comments on every public symbol, module-level overviews, examples the test suite runs so they cannot drift, and inline comments that explain why rather than what. Use whenever code is written, added, refactored, or reviewed, whenever a public API changes, and whenever asked to write, fix, or review comments, docstrings, doc comments, or API reference documentation.

Often used withcreate-media-pack·response-style·project-preferences

aniklavidaSkill

documentation

aniklavida/agent-assemble/documentation/SKILL.md

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

Often used withcreate-media-pack·response-style·project-preferences

BasharAmsoSkill

Documentation

BasharAmso/Bashi/.claude/skills/documentation/SKILL.md

Write project documentation including READMEs, API docs, and guides. Use this skill when documentation is requested or after a feature has shipped.

Often used withcreate-media-pack·response-style·project-preferences

DepressionCenterSkill

documentation

DepressionCenter/EFDC-Repo-Template/skills/documentation/SKILL.md

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.

Often used withcreate-media-pack·response-style·project-preferences

futex-aiSkill

documentation

futex-ai/skills/skills/documentation/SKILL.md

Use before you write or edit a README.md, a crate README, anything under docs/, an architecture doc, a protocol doc, or a code comment, before you add a rule to AGENTS.md or CLAUDE.md, when a behaviour change could leave a doc stale, when the code and a protocol doc disagree, when you decide whether a sentence belongs in a protocol doc, a README, a plan, a test, or the code, and when a change or a review option conflicts with a protocol doc.

Often used withcreate-media-pack·response-style·project-preferences

gabrielmongefrancoSkill

documentation

gabrielmongefranco/peerfoil/skills/documentation/SKILL.md

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.

Often used withcreate-media-pack·response-style·project-preferences

gabrielmongefrancoSkill

documentation

gabrielmongefranco/repo-template/skills/documentation/SKILL.md

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.

Often used withcreate-media-pack·response-style·project-preferences

khoralabsSkill

documentation

khoralabs/skills/skills/agent-review/documentation/SKILL.md

Maintain project documentation: README (Standard README spec), Architecture Decision Records, Diátaxis technical docs, and Keep a Changelog CHANGELOG.md. Use when writing or auditing README, ADR, docs site content, or changelog entries, or when the user mentions documentation structure or doc maintenance.

Often used withcreate-media-pack·response-style·project-preferences

nisarthSkill

documentation

nisarth/claude-skills-store/skills/engineering/documentation/SKILL.md

Write and maintain technical documentation. Trigger with "write docs for", "document this", "create a README", "write a runbook", "onboarding guide", or when the user needs help with any form of technical writing — API docs, architecture docs, or operational runbooks.

Often used withcreate-media-pack·response-style·project-preferences

shiranjitSkill

documentation

shiranjit/agentic-primer/skills/documentation/SKILL.md

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.

Often used withcreate-media-pack·response-style·project-preferences

t128nSkill

documentation

t128n/skills/skills/documentation/SKILL.md

Write, maintain, refactor, or review engineering documentation. Use for README files, architecture and API documentation, operational documentation, documentation consistency, or checking documentation against implemented behavior. Respect project conventions and use planning for new specifications, RFCs, ADRs, and implementation plans.

Often used withcreate-media-pack·response-style·project-preferences

tiago-oliveira-caSkill

documentation

tiago-oliveira-ca/zenodotus-harness/skills/documentation/SKILL.md

Software delivery documentation dispatcher. Routes to the correct document standard for the artifact being written or reviewed, following the BRD -> PRD -> FRD/NFR -> TRD -> SAB -> SAD -> ADR lifecycle. Use whenever creating, reviewing, auditing, or improving any software project document. Trigger on: "write a BRD", "PRD", "product requirements", "functional spec", "FRD", "TRD", "NFR", "document review", "business requirements", "acceptance criteria", "developer handoff", "write an ADR", "architecture decision", "write a SAD", "solution architecture", "traceability", "epic", "user story", "feature list", "roadmap", "release plan", "prioritize features", "MoSCoW", "RICE", "runbook", "postmortem", "go-live checklist", or any request to produce or improve a software delivery document.

Often used withcreate-media-pack·response-style·project-preferences