Expert glossary builder who creates comprehensive definitions and descriptions for all terms in a taxonomy. Your goal is to produce clear, accurate, and contextually appropriate definitions that help users understand each concept.
This skill should be used when the user asks "where is X", "how does X work", "explain X", "show me the architecture", "find component", "what handles X", or references C3 IDs (c3-0, c3-1, adr-*). Requires .c3/ to exist. For changes, route to c3-alter instead.
Hierarchical machine-readable documentation - root CLAUDE.md with module index, per-module CLAUDE.md for significant modules
General reference documents by domain. Use when creating architecture docs, strategy documents, specs, or guides.
Coordinate a full accessibility audit workflow across multiple a11y skills. Use this skill when users request "full accessibility audit", "accessibility audit", "remediate accessibility", "fix accessibility issues", "a11y audit", "test and fix accessibility", or any comprehensive accessibility analysis and remediation of code or URLs. This skill manages the three-stage workflow (analysis → remediation → validation) and produces a complete remediation report.
Locate scripts, references, and assets bundled with skills. Use when a skill mentions bundled resources (scripts/, references/, assets/ subdirectories) but you cannot immediately find them. Teaches standard skill directory structure and symlink navigation.
Asistente para el blog de psicología de Viviana Poveda. Ayuda con implementación Supabase, queries de base de datos, gestión de posts, y desarrollo del admin panel. Usa cuando trabajes en blog, psicología, Supabase, o Viviana Poveda.
Dispatch to the right problem-solving technique based on how you're stuck
メモリ管理のベストプラクティス集。推奨パターン、アンチパターン、実践的なヒントを提供。Use when user asks about best practices, recommended patterns, memory tips, or how to write good memory. Also use when user says ベストプラクティス, 推奨, コツ, ヒント, 良い書き方.
Root cause fixing and avoiding workarounds. Use when encountering errors, bugs, or problems. Triggers on "bug", "error", "fix", "debug", "workaround", "wrapper", "hack", "broken", "not working", "failing", "issue", or when tempted to add complexity to avoid fixing the real problem.
Annotation and documentation protocol for rapid-iteration projects (“vibe coding”). Enforces Google Docstring Style plus comment-as-contract: consistency with signatures/types, explicit pre/post-conditions, units/frames/conventions, and rich implementation comments. Use Notes with ASCII + pseudocode for complex algorithms.
Explain code in plain English with visual diagrams. Use when user wants to understand how code works or needs documentation.
代码变更后自动同步开发文档。支持功能文档、技术设计、决策记录的智能更新。当用户提到更新文档、同步文档、完成功能、修改数据结构或新增KPI时激活。
Write Python docstrings following PEP 257 and popular formats (Google, NumPy, Sphinx). WHEN: Writing docstrings for Python functions/classes/modules, choosing docstring format, documenting parameters/returns/exceptions. WHEN NOT: JavaScript documentation (use js-docstring), TypeScript (use ts-docstring), PHP (use php-docstring), general code comments.
Documentation-first development methodology. The goal is AI-ready documentation - when docs are clear enough, code generation becomes automatic. Triggers on "Build", "Create", "Implement", "Document", or "Spec out". Version 3.4 adds complete 13-item Clarity Gate with scoring rubric and self-assessment.
Generate detailed API contracts and specifications including OpenAPI/Swagger definitions, endpoint documentation, and integration guidelines
Remove historical cruft from design docs. Use when docs accumulate outdated content, after major refactorings, or when preparing for releases.
Use when design is complete and you need detailed implementation tasks for engineers with zero codebase context - creates comprehensive implementation plans with exact file paths, complete code examples, and verification steps assuming engineer has minimal domain knowledge
Use this skill when you are creating documentation for an existing Connect feature or updating existing docs
Unity開発の公式ドキュメント検索、最新API情報、パフォーマンス最適化、ベストプラクティスを案内するガイドエージェント。Unity Engine/Editor API、UPM/NuGetパッケージ、YAML設定ファイル編集に関する質問や実装支援で使用される。
文档生成技能：提供标准化的文档编写工作流和模板。 Use when: 需要编写组件文档、API 文档、模块 README、项目文档。 Triggers: "文档", "documentation", "README", "API 文档", "组件文档", "注释"
