Write clear API documentation with authentication, endpoints, and examples.
/api-documentation-writer1-2 days → 20 min
Compared to doing it manually
/api-documentation-writerType this in Claude to run the skill
Developers are your users. Bad docs mean bad adoption.
.claude/skills/ folder in your project/api-documentation-writer in Claude to run the skill/one-pager-creatorCreate compelling one-page feature briefs that align stakeholders quickly.
/product-brief-writerWrite one-page product briefs to get buy-in before investing in full specs.
/onboarding-flow-designerDesign onboarding flows that guide users to value quickly without being annoying.
/user-story-writerWrite clear user stories with acceptance criteria following the INVEST principles.
Good API docs include: clear endpoint descriptions, request/response examples, authentication details, error codes, and quick-start guides. Developers should be able to make their first API call within minutes.
Engineering writes technical details, Product ensures it's understandable to the target audience, and Developer Relations (if you have them) advocates for developer experience. It's a shared responsibility.
Update with every API change — ideally as part of the PR process. Outdated docs are worse than no docs. Include versioning so developers know which docs match their integration.
Run this skill inside your PM Operating System, or download it on its own.
Use all 70 skills, workflows, and sub-agents in a system that knows your company, product, and customers.