global-commenting
Write minimal, helpful code comments that explain why rather than what, prioritizing self-documenting code with clear structure and naming. Use this skill when adding comments to code, documenting complex logic...
Discover tools technical docs skills, compare source repositories and read the instructions for each workflow.
Write minimal, helpful code comments that explain why rather than what, prioritizing self-documenting code with clear structure and naming. Use this skill when adding comments to code, documenting complex logic...
JSDoc documentation standards for JavaScript functions, classes, modules, and web components
General documentation standards for README, AsciiDoc, and technical documentation
CUI JavaDoc documentation standards for Java classes, methods, and code examples
(opencode - Skill) Create and generate new OpenCode skill files with proper YAML frontmatter and Markdown structure. MUST USE when users want to create, build, or define new skills, skill files, SKILL.md files,...
Helps develop and build Docusaurus plugins using this starter template
Create, document, or revise Codex skills, including deciding when to add scripts/references/assets, structuring SKILL.md content, enforcing the 500-line rule, and updating repo references (AGENTS.md, kanban evi...
Automated HTML architecture documentation generator that produces navigable, searchable technical documentation from codebase analysis.
This skill should be used when the user asks to "implement code", "write feature", "create function", "develop component", "code the solution", or requests actual code implementation based on a design. Use for...
This skill should be used when the user asks to "write documentation", "create README", "document API", "add comments", "explain code", "generate docs", or requests documentation creation and maintenance. Use f...
Writing clear, maintainable documentation for code, APIs, and vault documents
Look up Microsoft API references, find working code samples, and verify SDK code is correct. Use when working with Azure SDKs, .NET libraries, or Microsoft APIs—to find the right method, check parameters, get w...
Generate comprehensive end-user documentation from application codebases
Rust documentation conventions (RFC 1574). Apply when writing doc comments on Rust items. Covers summary sentences, section headings, type references, and examples.
Documentation patterns for technical writing. Auto-loads when creating API docs, README files, JSDoc comments, or user guides.
Storybook stories, CSF3 format, autodocs. Use for component documentation.
Check if recent changes need documentation updates and suggest which docs to update.
Derive technical development principles FROM user needs in product.md using evidence-based reasoning. Creates constitution.md with architecture decisions, tech stack choices, and development constraints - all t...
Maintain and update architecture documentation in docs/architecture/. Uses tool-based inspection first, falling back to CLI only when needed.
Provide repository-wide documentation guidelines under `docs/`. Use tool-based inspection first, and keep `README.md` and `docs/` in sync with the current state of the app.
Use when design is complete and you need detailed implementation tasks - creates comprehensive implementation plans with exact file paths, complete code examples, and verification steps assuming minimal codebas...
Keeps narrative framing in docs while keeping code comments structural and stable.
Automated API documentation generation with support for OpenAPI/Swagger specifications, endpoint analysis, request/response examples, authentication methods, rate limiting, and integration guides. Use when Clau...
Create and maintain clear, useful documentation. Use when writing docs, README, API docs, guides, or ADRs.
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.