Loading...
Loading...
Found 3,153 Skills
Provides rules for handling multi-language documentation. Use this when configuring agent skill documents using starlight-skills on an i18n-enabled project. Do not use this for standard single-language sites or plugin configuration options.
Text formatting conventions for markdown and prose files. Use when writing or editing any .md, .txt, .adoc, or .rst file, including AGENTS.md, SKILL.md files, and documentation in docs/.
Generate database schema diagrams, ERDs, and documentation from database schemas.
Apply Swift API Design Guidelines to name, label, and document Swift APIs. Covers argument label rules (prepositional phrase rule, grammatical phrase rule, first-label omission), mutating/nonmutating pair naming (-ed/-ing participle pattern, form- prefix, sort/sorted, formUnion/union), side-effect naming (noun for pure, verb for mutating), documentation comment structure (summary by declaration kind, O(1) complexity rule), clarity at call site, role-based naming, protocol naming (-able/-ible/-ing), default arguments over method families, casing conventions, and terminology. Use when designing new Swift APIs, reviewing naming and argument labels, writing documentation comments, or refactoring for call site clarity.
Run the SPARC Refinement and Completion phases — review code, improve test coverage, validate against specification, and generate documentation
Expert product specification and documentation writer. Use when creating PRDs, user stories, acceptance criteria, technical specifications, API documentation, edge case analysis, design handoff docs, feature flag plans, or success metrics. Covers the full spectrum from high-level requirements to implementation-ready specifications.
Use when bootstrapping a new personal wiki for any knowledge domain — research, codebase documentation, reading notes, competitive analysis, or any long-term knowledge accumulation project.
Verify code quality including naming conventions, organization, documentation, and general best practices. Use when asked to "verify quality", "check code quality", or "review code organization".
Creates or audits a CLAUDE.md file — the ambient project-context document Claude Code loads at session start. Use when user says 'create a CLAUDE.md', 'audit our CLAUDE.md', 'is our CLAUDE.md any good', 'our CLAUDE.md is out of date', 'make CLAUDE.md load-bearing', or 'write scope-level CLAUDE.md'. Do NOT use for skills (use create-or-audit-skill), agents (use create-or-audit-agent), or user-facing documentation (use write-doc).
Create character design documentation and character design sheet images for video, storyboard, advertising, animation, or AI video-generation workflows. Use this skill whenever the user asks to design a character, extract a character from a reference image, make a character sheet, create a turnaround sheet, keep a person consistent across scenes, or generate character assets for a video project. This skill first writes a confirmable {character-name}.md design spec, waits for user approval or revision, and only then generates {character-name}.png.
Create runbooks, playbooks, and technical documentation for engineering teams. Use when the user wants to document a process, create a runbook, build operational docs, or formalize any repeatable technical procedure. Triggers on requests like "create a runbook for...", "document this process", "write a playbook", or any technical documentation request.
Write, rewrite, or edit user-facing text in the repo's preferred plain human style. Use for any prose task: docs, README sections, comments, release notes, PRDs, posts, emails, explanations, and requests to humanize or tighten text. Default to general prose rules; read references/documentation.md only for README, technical docs, usage guides, CLI/API docs, or documentation audits.