Documentation

Use after writing-plans to decompose monolithic plan into individual task files and identify tasks that can run in parallel (up to 2 subagents simultaneously)

Expert guidance for reliable bash script directory navigation and path handling. Use when writing new bash scripts, reviewing existing scripts, debugging directory-related failures, or when mentioned 'directory handling', 'bash paths', 'cd errors', 'script location', or 'git root'. Provides deterministic patterns to eliminate silent failures from unhandled cd, missing set -e, and path resolution issues.

JavaScript and TypeScript coding standards, conventions, and best practices. Use when writing, reviewing, or testing JS/TS code.

Applies Fabric AI prompt patterns for summarization, analysis, extraction, code review, and content creation. Use when asked to summarize content, analyze documents, extract insights, review code, create documentation, or transform text. Patterns are in data/patterns/.

Homeostatic sensor detecting requirements without implementation or test coverage. Scans for REQ-* keys in requirements docs and checks if they have corresponding code and tests. Use to find coverage gaps.

Provides web search capability for finding current information, documentation, and resources from external sources when local knowledge is insufficient

Complete Godot Engine knowledge base combining official documentation and source code analysis

Convert docstrings to NumPy/Sphinx style with proper Parameters, Returns, and Examples sections. This skill should be used when improving documentation quality across Python modules.

Use this skill when contributing code to open source projects. The skill covers proper pull request creation, avoiding common mistakes that annoy maintainers, cleaning up personal development artifacts before submission, writing effective PR descriptions, following project conventions, and communicating professionally with maintainers. It prevents 16 common contribution mistakes including working on main branch, not testing before PR submission, including unrelated changes, submitting planning documents, session notes, temporary test files, screenshots, and other personal artifacts. Includes 3 Critical Workflow Rules that must NEVER be skipped: (1) Always work on feature branches, (2) Test thoroughly with evidence before PR, (3) Keep PRs focused on single feature. The skill includes automation scripts to validate PRs before submission, templates for PR descriptions and commit messages, and comprehensive checklists. This skill should be used whenever creating pull requests for public repositories, contributing

Technical leadership guidance for engineering teams, architecture decisions, and technology strategy. Includes tech debt analyzer, team scaling calculator, engineering metrics frameworks, technology evaluation tools, and ADR templates. Use when assessing technical debt, scaling engineering teams, evaluating technologies, making architecture decisions, establishing engineering metrics, or when user mentions CTO, tech debt, technical debt, team scaling, architecture decisions, technology evaluation, engineering metrics, DORA metrics, or technology strategy.

Specialized codebase understanding agent for multi-repository analysis, searching remote codebases, retrieving official documentation, and finding implementation examples using GitHub CLI, Context7, and Web Search.

Code review best practices including review checklists (functionality, tests, documentation, security, performance), providing constructive feedback, automated checks integration, and handling review comments. Use when reviewing pull requests, providing code feedback, responding to review comments, or setting up review processes.

Comprehensive REST and GraphQL API design patterns, best practices, OpenAPI specifications, versioning, authentication, error handling, pagination, rate limiting, and security. Use when designing APIs, creating endpoints, reviewing specifications, implementing authentication, or building scalable backend services.

Advanced Git operations including rebasing, conflict resolution, history rewriting, worktrees, bisect, submodules, hooks, and complex workflows. Use for sophisticated Git challenges beyond basic add/commit/push, including fixing repository states, optimizing history, and managing complex branching strategies.

Expert knowledge for Application Layer modeling in Documentation Robotics

Research latest library documentation, industry best practices, and technical knowledge to automatically generate project-level skills. Use when asked to: (1) Research and create a skill for a library/framework, (2) Build a skill based on architectural patterns, (3) Generate skills from technical research, (4) Create domain-specific technical skills from web research, or (5) Any request combining research with skill creation.

Use this skill when the user is writing CSS for Divi 5, creating styles for WordPress/Divi, working with Divi modules, or mentions Divi theme development. Provides CSS patterns, class naming conventions, selector specificity guidance, and Divi-specific best practices.

ドキュメント・テスト品質レビュー - コメント品質、API仕様、テストの意味、カバレッジを統合評価

Use when writing or changing tests, adding mocks, or tempted to add test-only methods to production code - prevents testing mock behavior and production pollution

Patterns for testing pure functions using Deno's test framework. Covers unit tests, property-based testing, test organization, and assertion patterns. Use when writing tests. Includes script for generating test boilerplate.