Packs

1 pack

Design system skills: component specs, design tokens, naming conventions, spacing and grid systems, accessibility standards, and documentation.

11 skills · pack

Results for “documentation-standards”

44 skills

documentation-standards

documentation-standards

write-coding-standards-from-file

Analyze existing code files to generate a project-specific coding standards document, with options for templates, README insertion, and inconsistency detection.

kintsugi-programmer

python-code-style

Python code style, linting, formatting, naming conventions, and documentation standards. Use when writing new code, reviewing style, configuring linters, writing docstrings, or establishing project standards.

create-tldr-page

Transform verbose documentation into concise, example-driven tldr command references following the tldr-pages project standards.

coding-standard

Creates and updates coding standards, conventions, rules, and guidelines for the current project. Use when creating new standards from scratch, converting existing documents into coding standards, or updating existing standards. Does not create architectural decision records — use architectural-decision-record for ADRs. Does not write feature or system documentation — use project-documentation for that. Does not research open-ended options — use research. Does not produce runbooks for operational scenarios — use runbook for that.

construct-ai-primary

documentation-quality-check

Use before delivering any documentation to validate quality, accuracy, and completeness. This skill provides a checklist for reviewing all documentation deliverables to ensure they meet minimum quality standards before distribution.

More results

construct-ai-primary

taxonomy-standards

Use when creating tags, categories, or organizational structures for knowledge, documentation, or data. This skill provides consistent taxonomy standards across all companies and agents, enabling discoverability and cross-referencing.

documentation-writer

Creates high-quality software documentation following the Diátaxis framework, covering tutorials, how-to guides, reference, and explanation documents.

code-documenter

Generates, formats, and validates technical documentation including docstrings, OpenAPI specs, JSDoc annotations, documentation sites, and user guides.

10.4k · bundle

Creates, structures, and reviews technical documentation using the Diátaxis framework, organizing content into tutorials, how-to guides, reference material, and explanations.

documentation-template

Generate structured documentation templates for components, patterns, or guidelines within a design system.

Updates technical docs for verified behavior, public contracts, commands, configuration, and operations.

documentation-templates

Documentation templates and structure guidelines. README, API docs, code comments, and AI-friendly documentation.

software-architecture

Enforces system design, project structure, dependency management, error handling, testing, and documentation standards at principal-engineer level.

Technical documentation specialist for API docs, tutorials, architecture docs, and developer experienceUse when "documentation, docs, readme, tutorial, api docs, guide, changelog, comments, openapi, documentation, api-docs, tutorials, readme, openapi, swagger, developer-experience, technical-writing, ml-memory" mentioned.

technical-documentation

Build and review high-quality technical documentation, including agent instruction files and contributor-governance files, with support for audits, multilingual parity, and sub-agent orchestration.

Documents, standardizes, and governs a Vue 3 + shadcn-vue design system, including component documentation templates, patterns for forms, empty states, loading states, and feedback, plus a consistency checklist and conventional commit conventions.

documentation-writer

Diátaxis Documentation Expert. An expert technical writer specializing in creating high-quality software documentation, guided by the principles and structure of the Diátaxis technical documentation authoring framework.

kintsugi-programmer

Use when writing technical documentation that needs to be readable by both humans and AI models, converting existing docs to HADS format, validating a HADS document, or optimizing documentation for token-efficient AI consumption.

lang-rust-docs-dev

Rust documentation practices for HASH codebase. Use when writing doc comments, documenting functions/types/traits/modules, creating error sections, using intra-doc links, following rustdoc conventions, or exploring crate APIs with cargo doc.

Generate clear documentation for each task including technical descriptions, architecture diagrams, and usage guides. Use when documenting completed features, creating README files, writing API documentation, generating architecture diagrams, or maintaining project documentation. Ensures knowledge is preserved and accessible.

srednoff888-art

documentation-adrs

Use this skill for README, ADRs, runbooks, changelogs, decision records, operator docs. Trigger when the task involves programming work related to Documentation Adrs, production implementation, audits, debugging, strategy, or validation.

Update docs/index.md and write Google-style docstrings for NeMo-RL documentation changes.

writing-guidelines

Review documentation and prose for compliance with writing guidelines, checking style, voice, and tone against a fetched rule set.

doc-maintenance

Audits top-level documentation against recent git history to detect drift, applies minimal edits, and opens a pull request.

doc-coauthoring

Guides users through a structured three-stage workflow for co-authoring documents, from context gathering to reader testing.

Audits type safety documentation against the live codebase and fixes errors, gaps, or stale information to keep docs authoritative.

code-documentation

Use this skill when the user requests to generate, create, or improve documentation for code, APIs, libraries, repositories, or software projects. Supports README generation, API reference documentation, inline code comments, architecture documentation, changelog generation, and developer guides. Trigger on requests like "document this code", "create a README", "generate API docs", "write developer guide", or when analyzing codebases for documentation purposes.

doc-coauthoring

Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.

doc-coauthoring

Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.

Create, edit, and verify agent skills using test-driven development to ensure agents follow documented procedures correctly.

design-doc-template

Build Doc Template - Auto-activating skill for Technical Documentation. Triggers on: design doc template, design doc template Part of the Technical Documentation skill category. Use when working with design doc template functionality. Trigger with phrases like "design doc template", "design template", "design".

markdown-mermaid-writing

Creates scientific documentation using markdown with embedded Mermaid diagrams as the default format, enforcing a text-based diagram standard with style guides, 24 diagram type references, and document templates.

30.2k · bundle

code-documentation

Automatically generate clear, comprehensive documentation for codebases — including API references, inline docstrings, README files, and usage guides. Use when the user requests code documentation or provides relevant inputs for this workflow.

kintsugi-programmer

doc-coauthoring

Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.

Create developer handoff specifications with measurements, behaviors, assets, and edge cases.