Total 52,958 skills, Documentation & Writing has 1500 skills
Showing 12 of 1500 skills
Voice and tone rules for all written content. Use when writing prose that should sound human and be suitable for reading aloud.
Audit-style editing pass for `output/DRAFT.md`: remove template boilerplate, improve coherence, and enforce citation anchoring. **Trigger**: polish draft, de-template, coherence pass, remove boilerplate, 润色, 去套话, 去重复, 统一术语. **Use when**: a first-pass draft exists but reads like scaffolding (repetition/ellipsis/template phrases) or needs a coherence pass before global review/LaTeX. **Skip if**: the draft already reads human-grade and passes quality gates; or prose is not approved in `DECISIONS.md`. **Network**: none. **Guardrail**: do not add/remove/invent citation keys; do not move citations across subsections; do not change claims beyond what existing citations support.
Create and validate solution design documents (SDD). Use when designing architecture, defining interfaces, documenting technical decisions, analyzing system components, or working on solution-design.md files in docs/specs/. Includes validation checklist, consistency verification, and overlap detection.
Update the release notes file at `apps/docs/content/releases/next.mdx` based on PRs merged to main since the previous release, or archive `next.mdx` to a versioned file when a new version is published.
Use when writing or editing files in src/content/learn/. Provides Learn page structure and tone.
Guides writing Elixir documentation with @moduledoc, @doc, @typedoc, doctests, cross-references, and metadata. Use when adding or improving documentation in .ex files.
Regenerates documentation files (agents.md, agent-skills.md, plugins.md, usage.md) from marketplace data using Jinja templates. Use when plugins are added, updated, or removed to keep documentation in sync.
Use when complex systems need visual documentation, mapping component relationships and dependencies, creating hierarchies or taxonomies, documenting process flows or decision trees, understanding system architectures, visualizing data lineage or knowledge structures, planning information architecture, or when user mentions concept maps, system diagrams, dependency mapping, relationship visualization, or architecture blueprints.
This skill generates graphic novel narratives about physicists and scientists for intelligent textbooks. It creates compelling, historically-accurate stories with image prompts designed for high school students. Use this skill when the user wants to add a new scientist story to the Physics History Graphic Novels section of an MkDocs Material textbook, or when creating educational graphic novel content about historical scientists.
Update and maintain CLAUDE.md, README.md, agents, skills, and rules to match current project state. Use when docs are stale, the project structure changed, agents, skills, or rules reference outdated paths, or the user asks to update project documentation.
This skill provides screenplay action and description writing techniques. Covers present tense formatting, visual storytelling, action sequences, and paragraph structure for scene descriptions. Use when: writing scene descriptions, crafting action sequences, describing visual storytelling, or formatting action paragraphs in Fountain format.
Self-evolving context protocol that captures insights, prevents repeated mistakes, and evolves project documentation through structured feedback loops.