Loading...
Loading...
Found 2,894 Skills
TDD applied to documentation - create production-ready skills. Use when authoring new skills. Includes writing style guidelines for clear prose.
Adopts the rigorous, witty, and data-dense persona of a Sub-millimetre (sub-mm) Astrophysicist. Ideal for technical documentation, academic summaries, or transforming mundane topics into high-stakes scientific discourse.
API documentation specialist who creates comprehensive OpenAPI/Swagger specifications and technical documentation for RESTful APIs, GraphQL schemas, and microservices architectures. Use when writing API docs, creating OpenAPI specs, or documenting endpoints.
Compress documentation, prompts, and context into minimal tokens for AGENTS.md and CLAUDE.md. Achieves 80%+ token reduction while preserving agent accuracy.
Writes XML doc comments. Tags, inheritdoc, GenerateDocumentationFile, warning suppression.
Systematic documentation audit and maintenance. This skill should be used when documentation may be stale, missing, or misorganized — after feature work, refactors, dependency upgrades, or as a periodic health check. It prescribes folder structure for docs/ and manual/, dispatches haiku subagents for codebase/doc scanning, and routes doc creation to specialized agents (reference-builder, technical-writer, learning-guide) with docs-architect as quality gate.
Guide for creating and maintaining project documentation (README, guides, API specs). Emphasizes doc/code synchronization, consistency checks, and use of the docs-excellence-architect subagent.
Create a tldr page from documentation URLs and command examples, requiring both URL and command name.
Analyzes code repositories and generates hierarchical documentation structures with onboarding guides. Use when the user wants to create a wiki, generate documentation, map a codebase structure, or...
Initialize or update project documentation. Use when setting up docs for a new project (`--init`) or syncing docs to current codebase and architecture changes (`--update`).
Audit and maintain README standards across *-skills repositories with a two-pass workflow (audit first, optional bounded fixes second). Use when running Codex App or CLI automations for skills-repo documentation consistency, profile-aware section schemas, command integrity checks, and discoverability baseline enforcement.
Best practices for validating Dart documentation comments. Covers using `dart doc` to catch unresolved references and macros.