Total 50,320 skills, Documentation & Writing has 1450 skills
Showing 12 of 1450 skills
Prowler documentation style guide and writing standards. Trigger: When writing documentation for Prowler features, tutorials, or guides.
Put the answer first, then context and details follow. Use when writing documentation, tutorials, error messages, or any communication where readers need to decide quickly if something is relevant to them.
PRD 초안을 작성하고 형식을 검증한 뒤 GitHub PR 제출을 안내한다. "PRD 작성", "PRD 검증", "Day 6", "6일차", "PR 제출", "prd submit" 요청에 사용.
Write technical specifications that give agents enough context to implement features while leaving room for autonomous research and decision-making. Use when planning features, documenting architecture decisions, or creating implementation guides.
Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.
Use this skill when generating AI-agent-friendly documentation for a git repo or directory, answering questions about a codebase from existing docs, or incrementally updating documentation after code changes. Triggers on codedocs:generate, codedocs:ask, codedocs:update, "document this codebase", "generate docs for this repo", "what does this project do", "update the docs after my changes", or any task requiring structured codebase documentation that serves AI agents, developers, and new team members.
Generate feature specifications by analyzing existing source code.
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.
Write internal company communications — 3P updates (Progress/Plans/Problems), company-wide newsletters, FAQ roundups, incident reports, leadership updates, status reports, project updates, and general internal comms. Use this skill any time the user asks to draft, edit, or format something meant for internal audiences. Trigger on keywords like "3P", "weekly update", "newsletter", "FAQ", "internal comms", "status report", "company update", "team update", "incident report", or any request to summarize work for leadership, teammates, or the broader company. Even casual requests like "write my update" or "summarize what my team did this week" should trigger this skill.
Write user-facing documentation for a new or changed feature, in the project's docs site. Use when user says 'document this feature', 'write user docs', 'create feature page', 'add to the docs site', or 'write the end-user guide'. Do NOT use for internal architecture docs (use arc42 or write-doc), ADRs (use document-decision), or CLAUDE.md updates (use create-or-audit-claude-md).
Draft, restructure, or plan Nature-style manuscript sections from author-provided claims, results, figures, notes, or Chinese drafts. Use when the user wants to write or rebuild an abstract, introduction, results narrative, discussion, conclusion, title, or full manuscript argument rather than only polish finished prose.
Guides organizational and business storytelling—narrative structure (setup, tension, resolution), audience-tailored stories for executives, customers, boards, and teams, honest data and metrics framing, product and strategy narratives, incident and postmortem storytelling, and actuarial or insurance risk narratives for non-technical audiences. Covers story spine, key messages, and visual or slide narrative outlines. Use when the user says "tell the story", "storytelling", "narrative for executives", "data story", "board presentation narrative", "explain with a story", "story arc", "key message", "compelling narrative", "pitch story", or "incident story"—not cross-department reframing only (cross-department-translation), company-wide comms cadence and crisis wording packs (communication-lead), long-form creative fiction or screenwriting, brand copy without strategy context, or technical documentation and API reference (tech-writer-researcher).