Loading...
Loading...
Found 3,036 Skills
Enforcement skill for consistent documentation standards
Author RFC documents for proposed technical changes with clear problem framing, options, tradeoffs, and decision path. Use when proposal alignment and review sign-off are needed before implementation; do not use for post-decision implementation-only docs.
Technical documentation patterns for READMEs, ADRs, API docs (OpenAPI 3.1), changelogs, and writing style guides. Use when creating project documentation, writing architecture decisions, documenting APIs, or maintaining changelogs.
Use when you need to generate or improve Java project documentation — including README.md files, package-info.java files, and Javadoc enhancements — through a modular, step-based interactive process that adapts to your specific documentation needs. Part of the skills-for-java project
Static site generators, documentation platforms, and deployment workflows for technical documentation
Sync spec files with code changes. Triggers when modifying code that affects .kiro/specs/*/requirements.md or .kiro/specs/*/design.md. Use after implementing features, fixing bugs, or refactoring that changes behavior documented in specs.
Review and modernize Agent OS product documentation to ensure quantifiable value propositions and workspace-hub standards compliance.
Maintain organized project documentation with metadata headers. Update existing docs before creating new ones. Use when writing or editing any project documentation.
Generates clear, example-driven documentation with runnable code samples and progressive complexity. Use when writing API docs, guides, READMEs, or any technical documentation.
Use when API code changes (routes, endpoints, schemas). Enforces Swagger/OpenAPI sync. Pauses work if documentation has drifted, triggering documentation-audit skill.
Comprehensive documentation systems design including structure, generation, maintenance, and automation. Use when designing documentation systems, automating documentation generation, or managing large-scale documentation projects.
Write or update backend feature documentation that follows a repo's DOCUMENTATION_GUIDELINES.md (or equivalent) across any project. Use when asked to create/update module docs, API contracts, or backend documentation that must include architecture, endpoints, payloads, Mermaid diagrams, and seeding instructions.