Docs Gen
Generate and maintain documentation
snipgrapher
by mcollina
Configures and uses snipgrapher to generate polished code snippet images, including syntax-highlighted PNGs, SVGs, and WebP exports with custom themes, profiles, and styling options. Use when the user wants to create code screenshots, turn code into shareable images, generate pretty code snippets for docs or social posts, produce syntax-highlighted images from source files, or explicitly mentions snipgrapher. Supports single-file renders, batch jobs, watch mode, and reusable named profiles via the snipgrapher CLI or npx.
init
by mcollina
Creates, updates, or optimizes an AGENTS.md file for a repository with minimal, high-signal instructions covering non-discoverable coding conventions, tooling quirks, workflow preferences, and project-specific rules that agents cannot infer from reading the codebase. Use when setting up agent instructions or Claude configuration for a new repository, when an existing AGENTS.md is too long, generic, or stale, when agents repeatedly make avoidable mistakes, or when repository workflows have changed and the agent configuration needs pruning. Applies a discoverability filter—omitting anything Claude can learn from README, code, config, or directory structure—and a quality gate to verify each line remains accurate and operationally significant.
write-api-reference
by vercel
Produces API reference documentation for Next.js APIs: functions, components, file conventions, directives, and config options. Auto-activation: User asks to write, create, or draft an API reference page. Also triggers on paths like docs/01-app/03-api-reference/, or keywords like "API reference", "props", "parameters", "returns", "signature". Input sources: Next.js source code, existing API reference pages, or user-provided specifications. Output type: A markdown (.mdx) API reference page with YAML frontmatter, usage example, reference section, behavior notes, and examples.
update-docs
by vercel
This skill should be used when the user asks to "update documentation for my changes", "check docs for this PR", "what docs need updating", "sync docs with code", "scaffold docs for this feature", "document this feature", "review docs completeness", "add docs for this change", "what documentation is affected", "docs impact", or mentions "docs/", "docs/01-app", "docs/02-pages", "MDX", "documentation update", "API reference", ".mdx files". Provides guided workflow for updating Next.js documentation based on code changes.
insight-error-page
by vercel
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/<slug>.mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification against canonical docs, and Vercel technical writing style.
update-docs
by vercel
This skill should be used when the user asks to "update documentation for my changes", "check docs for this PR", "what docs need updating", "sync docs with code", "scaffold docs for this feature", "document this feature", "review docs completeness", "add docs for this change", "what documentation is affected", "docs impact", or mentions "docs/", "docs/01-app", "docs/02-pages", "MDX", "documentation update", "API reference", ".mdx files". Provides guided workflow for updating Next.js documentation based on code changes.
kibana-otel-instrumentation
by elastic
Implement and quality-check OpenTelemetry metric instrumentation in Kibana code that uses @kbn/metrics. Use whenever the user wants to add, change, or review OTel metrics — including any call to metrics.getMeter, meter.createCounter/createUpDownCounter/createGauge/createHistogram/createObservable*/addBatchObservableCallback, edits to kibana.yml telemetry.metrics config, or questions like "is this metric well-designed?", "what should I name this counter?", or "which instrument type is right here?". Trigger this skill even when the user does not say "OTel" or "OpenTelemetry" but is clearly adding observability to Kibana server code and already knows what they want to measure.
fhir-developer-skill
by anthropics
FHIR API development guide for building healthcare endpoints. Use when: (1) Creating FHIR REST endpoints (Patient, Observation, Encounter, Condition, MedicationRequest), (2) Validating FHIR resources and returning proper HTTP status codes and error responses, (3) Implementing SMART on FHIR authorization and OAuth scopes, (4) Working with Bundles, transactions, batch operations, or search pagination. Covers FHIR R4 resource structures, required fields, value sets (status codes, gender, intent), coding systems (LOINC, SNOMED, RxNorm, ICD-10), and OperationOutcome error handling.
deprecate-endpoint
by lightdash
Use when deprecating, sunsetting, or removing a backend HTTP API endpoint in Lightdash — wiring deprecation logging, deadline/sunset dates, response headers, and Sentry alerting onto a TSOA controller route. Also covers making the deprecation visible on docs.lightdash.com and llms.txt (description lead line, x-mint migration banner). Covers the first-party-caller precondition and the shared deprecation middleware.
dust-llm
by dust-tt
Step-by-step guide for adding support for a new LLM in Dust. Use when adding a new model, or updating a previous one.
future-planner
by hushh-labs
Use when evaluating future roadmap ideas, creating planning-only architecture docs, or assessing R&D concepts against Hussh north stars, trust boundaries, and current repo reality.
building-components
by vercel
Guide for building modern, accessible, and composable UI components. Use when building new components, implementing accessibility, creating composable APIs, setting up design tokens, publishing to npm/registry, or writing component documentation.
write-api-docs
by remix-run
Write or audit public API docs for Remix packages. Use when adding or tightening JSDoc on exported functions, classes, interfaces, type aliases, or option objects.
make-changes
by remix-run
Create or update Remix repo change files under packages/*/.changes. Use when a user asks for release notes, changes, a missing changelog entry, a prerelease note, or an update to existing unpublished release notes.
write-ui-module-readme
by remix-run
Write concise module README files for packages/ui/src/lib/* primitives. Use when drafting or revising README docs for UI package modules like popover, press, or other first-party UI helpers, especially when the main goal is agent-friendly usage guidance and a short explanation of each exported value.
make-tracking-issue
by remix-run
Create or revise a GitHub tracking issue for a Remix change, including the target outcome, implementor context, a concise checkbox plan, compatibility concerns, and required gates. Use when the user asks to open, draft, rewrite, or tighten a tracking issue, implementation issue, umbrella issue, or work plan in the Remix repository.
make-decision-doc
by remix-run
Add a numbered decision document under decisions/ to capture a non-obvious architectural choice. Use when the user asks for a decision doc, ADR, design rationale, or wants to record why we picked one approach over alternatives.
write-readme
by remix-run
Write or rewrite package README files in the style used by the Remix repository. Use when drafting a new package README, revising an existing README, or reviewing README structure, examples, installation instructions, and section ordering for Remix packages.
write-guides
by remix-run
Write, rewrite, or audit Remix guide chapters in the voice of docs/guides/app/actions/docs/chapters/01-start-here.md. Use when drafting app guides, revising generated-sounding prose, tightening guide examples, preserving doc anchors, or reviewing Markdown chapters under docs/guides/app/actions/docs/chapters/.
docs-writer-reference
by reactjs
Reference page structure, templates, and writing patterns for src/content/reference/. For components, see /docs-components. For code examples, see /docs-sandpack.
docs-voice
by reactjs
Use when writing any React documentation. Provides voice, tone, and style rules for all doc types.
review-docs
by reactjs
Use when reviewing React documentation for structure, components, and style compliance
docs-writer-blog
by reactjs
Use when writing or editing files in src/content/blog/. Provides blog post structure and conventions.
docs-sandpack
by reactjs
Use when adding interactive code examples to React docs.