Loading...
Loading...
Found 2,897 Skills
Provides comprehensive guidance for adding Java code comments following industry standards and best practices. This skill helps add class-level comments, method-level comments, and field-level comments to Java code. Use when the user wants to add comments to Java code, needs to document Java classes/methods/fields, wants to improve code documentation, or needs to generate JavaDoc comments. This skill covers Controller, Service, ServiceImpl, Mapper, Model, Entity, BO (Business Object), DTO, VO, and other common Java component types. The skill follows a systematic workflow: scan codebase, identify components, create todo list, and add comments in order (class comments → method comments → field comments).
System architecture design for Rust/WebAssembly projects. Creates ADRs, designs APIs, plans module structures, and documents architectural decisions. Never writes implementation code - focuses purely on design and documentation.
Create diagrams and visualizations using Mermaid syntax. Use when generating flowcharts, sequence diagrams, class diagrams, entity-relationship diagrams, Gantt charts, or any visual documentation. Triggers on Mermaid, flowchart, sequence diagram, class diagram, ER diagram, Gantt chart, diagram, visualization.
Parses interface/API information from files or directories and generates OpenAPI-compliant documentation with timestamps
Generate API documentation from OpenAPI specs or code.
Maintain project-local reference documentation cached from Context7 and other sources. Use when (1) initializing local docs for a new project, (2) updating or expanding existing reference docs, (3) looking up library documentation — check local cache first, (4) saving useful externally fetched docs for future sessions.
This skill should be used when the user asks to "map documentation links", "extract docs navigation", "get documentation structure", "scrape docs sidebar", or wants to understand the structure of a documentation website before creating skills.
Generate OpenAPI documentation from source code. Analyzes repository to automatically discover API endpoints and create swagger.json and interactive HTML documentation. Use when generating API docs, creating OpenAPI specs, documenting REST APIs, or analyzing API endpoints.
Writes and audits technical documentation using Diataxis, Stripe-style clarity, and the Eight Rules. 52 rules across 9 categories covering voice, structure, clarity, code examples, formatting, navigation, scanability, content hygiene, and review. Use when writing docs, creating READMEs, documenting APIs, writing tutorials, building a docs site, or auditing documentation quality.
Use after modifying existing systems to update blueprint documentation. Read blueprints before changes, update after. Prevents documentation drift.
Generates comprehensive API documentation in Markdown, HTML, or Docusaurus format from Express, Next.js, Fastify, or other API routes. Creates endpoint references, request/response examples, authentication guides, and error documentation. Use when users request "generate api docs", "api documentation", "endpoint documentation", or "api reference".
Create handoff documentation for work-in-progress sessions. Use when handing off work to another agent to supplement history compaction and and progress summarization.