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”

63 skills

documentation-standards

documentation-standards

155-zero-0a870ee6

Defines quality standards and validation checklists for agent workflows, Python tools, and documentation, including automated checks and pre-commit gates.

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.

More results

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.

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.

cpp-coding-standards

Enforces modern, safe, and idiomatic C++ coding practices based on the C++ Core Guidelines for writing, reviewing, or refactoring C++ code.

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

software-architecture

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

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.

database-model-standards

database-model-standards

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.

technical-documentation

Build and review high-quality technical docs as well as agent instruction files in your repository.

engineering-standards

Use only when the request concerns standards, responsibility, complexity, smells, naming, refactoring catalogs, or task-plan rules; not routine work.

technical-writer

Expert technical documentation specialist for developer docs, API references, and runbooks. Activate on: documentation, docs, README, API reference, technical writing, user guide, runbook, ADR, changelog, release notes, tutorial, how-to guide. NOT for: marketing copy (use copywriting skills), blog posts (use content skills), code comments (handled by developers).

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.

Create and enforce writing style guides covering voice, tone, terminology, formatting conventions, and editorial rules for consistent documentation. Use when establishing or applying writing standards across a team or project. Also trigger for 'style guide', 'voice and tone', 'writing standards', 'editorial guidelines', 'terminology glossary', 'content standards', or 'brand voice'.

Generate and validate repo docs, READMEs, and OSS doc packs. Triggers: "doc", "generate and validate repo docs", "doc skill".

code-generation-standards

code-generation-standards

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.

Use when creating new skills, editing existing skills, or verifying skills work before deployment