Total 43,459 skills, Documentation & Writing has 1289 skills
Showing 12 of 1289 skills
Creates comprehensive developer onboarding documentation and materials including step-by-step setup guides, first-task assignments, expected time per step, common troubleshooting, team introductions, and code walkthrough tours. Use when preparing "new developer onboarding", "first day setup", "junior dev training", or "team member onboarding".
Dev.to API via curl. Use this skill to publish and manage articles on Dev.to.
A resource set to help write various internal communications using the format preferred by the company. Claude should use this skill whenever asked to write any type of internal communication (status reports, leadership updates, 3P updates, company briefings, FAQs, incident reports, project updates, etc.).
Structured literature search and synthesis with citation extraction and gap identification
Explicitly update DESIGN.md with decisions from the current conversation. Use when you want to force a design document update.
Professional documentation writing skills. Used for creating technical documents, READMEs, API documents, user manuals, etc. This skill is applied when users need to write or improve documents.
Provides Chinese technical documentation writing guidelines. Use when creating new technical guides, editing existing docs to follow standards, or reviewing document format and structure.
Updates the "Prowler at a Glance" table in README.md with accurate provider statistics. Trigger: When updating README.md provider stats, checks count, services count, compliance frameworks, or categories.
Voice development and style coaching for creative writing. Analyzes the user's natural writing patterns, builds a voice profile, coaches on register transitions, and flags unintentional voice shifts. The voice is the user's — this skill helps them find and refine it.
Creative writing project architecture — concept mapping, thematic structure, outlining, and strand interweaving. Helps the user see the shape of their project. Use when structuring a new project, reorganizing an existing one, or mapping how narrative, art-as-code, and theory interweave.
Comprehensive checklist and process for reviewing documentation quality including voice, tone, structure, completeness, and technical accuracy.
Write and review API documentation comments using TSDoc and JSDoc best practices. Use when the user asks for docs, doc comments, TSDoc, JSDoc, @param/@returns help, or documentation quality improvements in JavaScript or TypeScript code.