Results for “documentation”

Answers questions about a codebase by searching and reading source files, providing answers with inline citations and structured responses.

Locates files by intent using semantic search, ideal for finding implementations, definitions, or documentation in medium to large repositories.

Generate an llms.txt file from repository structure, following the llms.txt specification to help LLMs navigate and understand the project.

Create ASP.NET Minimal API endpoints with proper types and comprehensive OpenAPI/Swagger documentation.

Guides writing effective pull request descriptions focused on motivation, public API changes, and user impact while avoiding implementation details.

Compacts the current conversation into a handoff document for another agent to continue the work, saving it to the OS temporary directory.

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.

Provides guidance on using Neon Serverless Postgres, including setup, connection methods, features like branching and autoscaling, and references to official documentation.

Create Earth2Studio prognostic model wrappers that time-step weather forecasts forward, with triple-inheritance classes, tests, and documentation.

Provides guidelines for building with Botpress's Agent Development Kit (ADK), covering primitives, project structure, CLI usage, and documentation lookups.

Guides installation of dbt Core or dbt Cloud CLI and points to official documentation for getting started with dbt.

Creates and manages Product Requirements Documents (PRDs) with structured user stories, acceptance criteria, and progress tracking for feature planning.

Continues deep iteration on an existing planning document: detects explicit file-loading intent, provides status summaries, and supports on-demand in-depth exploration.

Creates a technical journey retrospective document from a coding session, capturing decisions, tradeoffs, and debugging moments in a developer blog post style.

Generates a complete IEEE 830-compliant Software Requirements Specification from approved plan files, producing one file per section with no word limit.

Documenta, versiona y cierra proyectos de análisis de datos para que queden ordenados y reproducibles en el futuro.

Manages shadcn/ui components and projects, providing context, documentation, and usage patterns for building modern design systems.

Analyzes codebases in depth and produces structured markdown analysis documents covering architecture, module design, call flows, data models, and design patterns.

Generates a complete IEEE 830-compliant software requirements specification from approved plan files, producing one file per section with no word limit.

Generates an IEEE 830 software requirements specification from raw client input, guiding users through structured clarification rounds and producing a compliant document.

Answers questions about a codebase by searching and reading source files, then synthesizing answers with inline citations and a key files table.

Generate clean, minimal technical SVG diagrams in a consistent Cloudflare-inspired style. Use when creating architecture diagrams, flow diagrams, or component diagrams for blog posts and documentation.

Use this skill when a driver does not meet federal medical standards and needs to apply for a variance. Covers application steps, required documentation, and review timeline.

Design RESTful and GraphQL APIs with proper validation, versioning, and documentation. Use when creating new endpoints, designing request/response models, or reviewing API contracts.

Produces durable, structured documentation in codebases with sparse docs — readable by humans and agents alike. Two invocation modes — `survey` proposes a doc plan; `draft` writes one specific doc end-to-end with a factcheck-then-persona review gate. Triggered by phrases like "doxcavate this repo", "doxcavate the X", "doxcavate `runbook-deploy`", "what should be documented?", "document this code", "write a how-it-works for X", or any request to inventory or write project documentation.

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.

Scans codebases for GDPR/DSGVO compliance issues, generates DPIA documentation, and tracks data subject rights requests with deadline management.

Generate design tokens, color palettes, typography scales, component systems, and developer handoff documentation for UI design systems.

Verifies that blockchain code implements exactly what documentation specifies, identifying gaps between specs and implementation for audit engagements.

Guides users through installing dbt Core or the dbt Cloud CLI and points to official dbt documentation and community resources.

Answers questions about a codebase by searching and reading source files, then synthesizing answers with inline citations and a key files table.

Provides reference documentation and code patterns for using Biopython to handle biological sequences, file formats, database access, alignments, structures, and phylogenetics.

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.

Writes or updates a HANDOFF.md document to preserve context for the next agent, including goal, progress, what worked, what didn't, and next steps.

Synthesizes the current conversation and codebase context into a structured PRD and publishes it to the project issue tracker with a triage label.

Guides the agent through structured protocols for writing technical specifications, implementation plans, and summaries, with file naming and task directory conventions.