writing-trd
Write TRDs documenting how to build and test it. Use when writing TRDs or technical requirements.
Découvrez les skills blockchain technical docs, comparez leurs dépôts et consultez leurs instructions.
Write TRDs documenting how to build and test it. Use when writing TRDs or technical requirements.
Comprehensive guidance for FastAPI, Typer, and SQLModel development including patterns, best practices, API design, CLI development, database integration, testing, and common workflows. Use this skill when buil...
Automatically applies when writing function docstrings. Uses Google-style format with Args, Returns, Raises, Examples, and Security Note sections for proper documentation.
Look up Microsoft API references, find working code samples, and verify SDK code is correct. Use when working with Azure SDKs, .NET libraries, or Microsoft APIs—to find the right method, check parameters, get w...
Guide you through creating a single Red Hat Showroom workshop module from reference materials (URLs, files, docs, or text) with business storytelling and proper AsciiDoc formatting.
Helps locate and navigate project documentation efficiently
Complete documentation organization methodology for repositories. Use when organizing docs, creating reports, naming files, structuring project documentation, or needing guidance on documentation types.
Generate comprehensive README files for 42 School projects. Use when creating or improving project documentation.
Generate comprehensive project analysis documentation for code repositories. Use when Claude needs to analyze a codebase and create detailed documentation covering project architecture, component relationships,...
Explains code with visual diagrams and analogies to help users understand how code works.
Given a Simulabra module, print out a listing of the classes inside with their docstrings, line numbers, and slots
プロジェクト全体のステアリングドキュメント(永続的コンテキスト)の管理ガイド。以下の状況で使用する: (1) ユーザーが「プロジェクト方針を定義したい」「技術スタックを整理したい」と言った時 (2) specs/_steering/ 配下...
Esta skill debe usarse cuando el usuario pide "investiga documentación de", "consulta documentación de", "quiero integrar X en", "cómo integrar", "implementar X en proyecto", "qué librería para", "instalar", "c...
Comprehensive research skill using Exa AI tools for web search and code context retrieval. Use when conducting research on technologies, finding code examples, discovering latest tools, or gathering comprehensi...
Use Codex CLI (OpenAI) for code consultation and review. Triggers: "codex", "ask codex", "code review", "review this" Use cases: (1) Message/copy review, (2) Code review, (3) Design consultation, (4) Bug invest...
Use this skill when the user asks questions about Claude Code CLI, Claude Agent SDK, or Claude API. Provides comprehensive guidance, documentation references, and best practices.
Search library/framework documentation via llms.txt (context7.com). Use for API docs, GitHub repository analysis, technical documentation lookup, latest library features.
Generates feature specification documents based on provided code and functional descriptions. Focuses on system analysis and product logic rather than implementation details. Code is treated as the single sourc...
WHAT: JSDoc and inline documentation standards for React components and hooks. WHEN: documenting components, writing JSDoc for functions, explaining complex logic. KEYWORDS: jsdoc, documentation, comments, @des...
Search markdown documentation efficiently. Use when user asks about docs, guides, setup, configuration, API reference, or says "check the docs". Provides fuzzy search, regex matching, and section extraction.
Esta skill debe usarse cuando el usuario pide "documentar un patrón", "documentar un problema", "documentar una decisión", "documentar guías", "documentar la sesión", "crear documentación de", o quiere capturar...
How to update docs in `./.ai`
Deep knowledge about Ryan's open source projects (openpkg-ts, doccov, secondlayer). Use when users ask about these tools, their features, usage, or output.
Rules and conventions for writing MDX/Markdown documentation in the staystack-ts repository.
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.