Writing clear technical documentation helps everyone on a team understand how things work. You can create documents for different audiences like developers, operators, and new team members. Technical documentation makes projects easier to use and maintain.
This skill helps you write a README for quick setup. It helps you create API documentation with endpoint examples and error codes. You can also write a runbook with step-by-step procedures and rollback steps. An architecture doc explains design choices and data flow. An onboarding guide helps new people get started fast.
The skill follows best practices like starting with the most useful information and showing examples instead of just telling. It also reminds you to keep documents up to date and link to other resources instead of repeating them.
Global
mkdir -p ~/.claude/skills/documentationProject
mkdir -p .claude/skills/documentationSource Repository
Grill With Docsmattpocock/skills
Stress-test your plan, refine your terms, and update docs instantly
Lark Doclarksuite/cli
Create read summarize edit translate and manage Lark cloud documents
To Prdmattpocock/skills
Generate a complete PRD from your conversation and codebase understanding
Github Actions Docsxixu-me/skills
Answers your GitHub Actions questions with exact official documentation links
Readme I18nxixu-me/skills
Localize your repo READMEs automatically with structure and selector intact
Domain Modelingmattpocock/skills
Define clear terms and record key decisions for a shared project language
Ubiquitous Languagemattpocock/skills
Build a shared glossary of terms from your conversations with clear definitions
Edit Articlemattpocock/skills
Polish your article drafts by improving clarity structure and flow