Back to tags
Tag

Agent Skills with tag: documentation

127 skills match this tag. Use tags to discover related Agent Skills and explore similar workflows.

AI Documentation Standards

Write AI-readable documentation following concise-over-comprehensive principle, hierarchical CLAUDE.md/AGENTS.md inheritance (100-200 line rule), structured formats (tables over prose), parallel validation, and session knowledge capture. Use when writing documentation, updating docs, or optimizing existing docs.

documentationstructured-formattingconcisenessvalidation
randalmurphal
randalmurphal
0

markdown

Always use this skill when writing or editing markdown files!

markdownmarkup-languagedocumentationcontent-formatting
cardoso-neto
cardoso-neto
0

creating-skills

Create high-quality Claude Code skills with proper structure, effective descriptions, and best practices. Use when creating a new skill, writing SKILL.md files, setting up skill directories, or asking how to make skills.

claude-codeskill-developmentbest-practicesdocumentation
Optima-Financial
Optima-Financial
0

mermaid

Create text-based diagrams using Mermaid syntax. Perfect for version-controlled diagrams that render in GitHub, documentation sites, and markdown files.

mermaid-syntaxdiagramsmarkdowndocumentation
flight505
flight505
0

create-skill

Guide for authoring agent skills. Use when creating new skills, writing SKILL.md files, or improving existing skills.

developer-guidancedocumentationskill-authoringexample
lbussell
lbussell
0

pre-work-research

Use before starting implementation - research repository documentation, codebase patterns, and external resources to inform the approach

codebase-analysisdocumentationimplementation-preparationapproach-evaluation
troykelly
troykelly
1

deferred-finding

Use when a review finding cannot be fixed in current PR - creates properly documented tracking issue with full context, linked to parent, following full issue-driven-development process

issue-trackingprocess-managementdocumentationparent-issue-linking
troykelly
troykelly
1

research-after-failure

Use after 2 consecutive failed attempts at solving a problem - STOP guessing and research documentation, codebase, and online resources before resuming

debuggingdeveloper-guidanceproblem-solvingdocumentation
troykelly
troykelly
1

issue-decomposition

Use when an issue is too large for a single task - breaks into linked sub-issues with full documentation, ensuring manageable work units

task-decompositionissue-trackingproblem-framingdocumentation
troykelly
troykelly
1

doc-coauthoring

Guide 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.

coauthoringcollaborationworkflowdocumentation
zhuxining
zhuxining
0

nim-pr-guide

>

nimprogramming-languageguidedocumentation
axiomantic
axiomantic
0

Documentation review

Reviews documentation for factual accuracy

documentationfactual-accuracyquality-assurancecontent-validation
ovachiever
ovachiever
81

notion-knowledge-capture

Transforms conversations and discussions into structured documentation pages in Notion. Captures insights, decisions, and knowledge from chat context, formats appropriately, and saves to wikis or databases with proper organization and linking for easy discovery.

notiondocumentationworkflow-automationknowledge-management
ovachiever
ovachiever
81

notion-research-documentation

Searches across your Notion workspace, synthesizes findings from multiple pages, and creates comprehensive research documentation saved as new Notion pages. Turns scattered information into structured reports with proper citations and actionable insights.

notiondocumentationinformation-synthesiscitation
ovachiever
ovachiever
81

readme-updater

Keep README files current with project changes. Use when project structure changes, features added, or setup instructions modified. Suggests README updates based on code changes. Triggers on significant project changes, new features, dependency changes.

readmedocumentationproject-structuredependency-management
ovachiever
ovachiever
81

doc-coauthoring

Guide 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.

coauthoringworkflowtechnical-writingdocumentation
Wattysaid
Wattysaid
0

map-codebase

Analyze codebase with parallel Explore agents to produce .planning/codebase/ documents. Use for brownfield project onboarding, refreshing codebase understanding after significant changes, before major refactoring, or when onboarding to unfamiliar codebases. Creates structured documentation of stack, architecture, structure, conventions, testing, integrations, and concerns.

codebase-analysisarchitecture-documentsdeveloper-guidancedocumentation
philoserf
philoserf
0

repo-docs

Update and maintain core repository documentation files (README.md, CHANGELOG.md, LICENSE, CONTRIBUTING.md) before commits or releases. Use when users need to update documentation to reflect code changes, prepare for releases, or ensure documentation consistency.

documentationrepository-managementrelease-preparationcommit-process
alanben
alanben
0

Page 1 of 8 · 127 results