Results for “technische-dokumentation”

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.

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

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

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

Generate technical architecture diagrams, pipeline flows, layer/stack diagrams, and system illustrations as standalone HTML files. Uses a dark-mode design system with embedded CSS and inline SVG. Use when the user needs architecture diagrams, system illustrations, flow charts, or technical visualizations.

Mantém a documentação técnica viva no Notion e no repositório, gerando runbooks, inventários, ADRs e procedimentos a partir da infraestrutura real.

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.

Generates a three-column technical documentation page with side navigation, article body, and sticky table of contents.

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).

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

Write or maintain technical documentation — READMEs, runbooks, API references, architecture docs — that a specific reader can act on without asking follow-ups.

Generates detailed, technology-agnostic implementation blueprints by analyzing project architecture, technology stacks, and data flow patterns.

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

Create time-boxed technical spike documents for researching and resolving critical development decisions before implementation.

Generates rich technical documentation pages with dark-mode Mermaid diagrams, source code citations, and first-principles depth.

Create or update standardized object-oriented component documentation by analyzing source code and following a shared template with mode-specific guidance.

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

Analyzes codebases to generate detailed technology stack blueprints with version information, licensing, usage patterns, coding conventions, and architecture diagrams.

Prepare ISO 13485:2016 certification documentation for medical device Quality Management Systems, including gap analysis, template-based document creation, and compliance checklists.

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

Creates comprehensive technical documentation from existing codebases. Analyzes architecture, design patterns, and implementation details to produce long-form technical manuals and ebooks. Use PROACTIVELY for system documentation, architecture guides, or technical deep-dives.

Document datasets, variables, sources, and merge keys for replication

Transforms video or audio transcripts into structured markdown documentation, organizing content by topic with configurable styles and source attribution.

Converting repository changes into detailed learning documents. Use when turning diffs into teaching materials, recording design decisions, or creating onboarding materials for new members.

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.

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.

Generates documentation - JSDoc, README sections, API docs, inline comments

A technical writer who crafts clear, comprehensive documentation. Specializes in README files, API docs, architecture docs, and user guides.

Use when turning technical implementation details into clear maintainable documentation.

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.

Create runbook creator operations. Auto-activating skill for Technical Documentation. Triggers on: runbook creator, runbook creator Part of the Technical Documentation skill category. Use when working with runbook creator functionality. Trigger with phrases like "runbook creator", "runbook creator", "runbook".

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

Analyze a codebase and generate onboarding documentation for engineers, tech leads, and contractors, with fast fact-gathering and repeatable outputs.

Creates and maintains project documentation for features, systems, and components. Use when documenting how a feature, system, or component works — including writing, updating, or organizing docs. Does not scan or detect the project's technology stack — use project-discovery for repository analysis and config detection. Does not create architectural decision records — use architectural-decision-record for ADRs. Does not create or update coding standards — use coding-standard instead. Does not generate PR descriptions — use update-pr-description for that. Does not produce runbooks for operational scenarios — use runbook for that. Does not rewrite existing prose for readability — use edit-for-readability for that. Does not produce an ephemeral, understand-now overview of code or a PR — use code-overview for that.

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".