Documentation
Documentation tools and technical writing skills
6825 skills in this category
Subcategories
documentation
Project documentation patterns using README.md with visual diagrams. For creating and maintaining product-level documentation that's accessible in-app via CMD-I.
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
git-commit
Generate meaningful commit messages from git changes following conventional commits format. Use when user says "commit", "create commit", or needs help writing commit messages.
backend-queries
Write efficient and secure database queries following best practices for SQL injection prevention, N+1 query optimization, and performance for PostgreSQL (Bun.sql, Prisma, Supabase) and Firestore. Use this skill when writing or modifying database queries, implementing data fetching logic, working with ORMs (Prisma, TypeORM, Entity Framework), using Bun.sql native driver, querying Firestore collections, or implementing caching strategies. Apply when working on service files (services/*.ts, repositories/*.ts, *Service.cs), query builder implementations, data access layers, or any code that fetches or manipulates data. This skill ensures parameterized queries to prevent SQL injection (never interpolate user input), eager loading to prevent N+1 problems, selective column fetching (no SELECT *), strategic indexing on WHERE/JOIN/ORDER BY columns, transactions for related operations, query timeouts for performance, caching expensive queries, prepared statements with Bun.sql for repeated queries, and query-driven mod
generating-commit-messages
Generates clear commit messages from git diffs. Use when writing commit messages or reviewing staged changes.
api-schema-analyzer
Analyze OpenAPI and Postman schemas for MCP tool generation. Use when analyzing API specifications, extracting endpoint information, generating tool signatures, or when user mentions OpenAPI, Swagger, API schema, endpoint analysis.
documentation-standards
How user-facing and internal documentation should be written and maintained.
julien-mcp-notion-pro
Install Notion Pro MCP for secondary workspace. Use when user has multiple Notion workspaces.
update-readme
Autonomously audit the entire repository and update the main README with comprehensive, accurate documentation of the current codebase
leap-review
Validate LEAP compliance before PR submission. Checks branch structure, required documentation, and markdown formatting.
devknow
This skill should be used when the user asks to 'capture knowledge', 'capturar conocimiento', 'record lessons', 'registrar lecciones', 'track technical debt', 'rastrear deuda técnica', or mentions 'lessons learned', 'lecciones aprendidas', 'patterns', 'patrones', 'debt', 'deuda técnica', 'memory MCP', 'knowledge base'.
research-orchestration
Use when brainstorming completes and user selects research-first option - manages parallel research subagents (up to 4) across codebase, library docs, web, and GitHub sources, synthesizing findings and auto-saving to memory before planning
amazon-writing
Use when writing narrative memos, 6-pagers, 1-pagers, press releases, or PRFAQs in Amazon style. Applies Amazon's no-PowerPoint writing standards with data over adjectives, active voice, and the "so what" test.
tempo
Guide for implementing Grafana Tempo - a high-scale distributed tracing backend for OpenTelemetry traces. Use when configuring Tempo deployments, setting up storage backends (S3, Azure Blob, GCS), writing TraceQL queries, deploying via Helm, understanding trace structure, or troubleshooting Tempo issues on Kubernetes.
receiving-code-review
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
argument-mapping
Reconstruct, visualize, and analyze argument structure. Use for: argument reconstruction, premise identification, inference evaluation, finding hidden assumptions, visualizing debates, Toulmin model analysis. Triggers: 'argument structure', 'premises', 'conclusion', 'inference', 'reconstruct', 'map the argument', 'Toulmin', 'argument diagram', 'validity', 'soundness', 'implicit premise', 'hidden assumption', 'logical structure'.
audio-design
Game audio design patterns for creating sound effects and UI audio. Use when designing sounds for games, writing AI audio prompts (ElevenLabs, etc.), creating feedback sounds, or specifying audio for abilities/UI. Includes psychological principles from Kind Games, volume hierarchy, frequency masking prevention, and prompt engineering for AI audio generation.
claude-commands
Guide for creating custom slash commands for Claude Code. Use this skill when you need to extend Claude Code's capabilities with custom workflows, plugin commands, or reusable prompts defined in Markdown.
docs-seeker
Search technical documentation using executable scripts to detect query type, fetch from llms.txt sources (context7.com), and analyze results. Use when user needs: (1) Topic-specific documentation (features/components/concepts), (2) Library/framework documentation, (3) GitHub repository analysis, (4) Documentation discovery with automated agent distribution strategy
documentation-writer
This skill should be used when an agent is assigned to write a section of technical documentation. Provides guidance on breaking down large tasks, using doc-coauthoring workflow, and coordinating with VibeKanban task management. Use when task description mentions "write section", "document this component", or "expand documentation".