Discover Documentation skills, compare source repositories and read the instructions for each workflow.
Generate API specification from codebase - endpoints, types, schemas. Use when generating API documentation, documenting endpoints, or when user mentions API docs, API仕様, OpenAPI, Swagger, REST API, endpoint...
TypeScript type safety patterns and best practices for maximum type coverage. Use when reviewing TypeScript code for type issues, eliminating `any` types, or when user mentions type safety, 型安全, 型カバレッジ...
Framework-agnostic frontend component design patterns. Use when designing React/Vue/Angular components, applying Container/Presentational pattern, or when user mentions component patterns, フロントエンドパター...
Root cause analysis with 5 Whys methodology. Triggers: root cause, 5 Whys, なぜなぜ分析, 根本原因, 原因分析, symptom fix, 対症療法.
Fundamental software principles - SOLID, DRY, Occam's Razor, Miller's Law, YAGNI, Readable Code. Use when applying design principles, refactoring code, or when user mentions 原則, シンプル, 複雑, リファクタリン...
Command workflow orchestration patterns for /code, /fix, /audit, and other implementation commands. Triggers: workflow, orchestration, command flow, IDR, test generation, RGRC, quality gates, completion criteri...
CSS-first approach - use CSS before JavaScript. Use when implementing layouts, animations, or toggles, or when user mentions レイアウト, スタイル, 位置, アニメーション, 表示/非表示, トグル, レスポンシブ, CSS Gr...
Silent failure detection patterns for frontend code. Use when reviewing error handling, detecting swallowed errors, or when user mentions silent failure, empty catch, エラーハンドリング, 握りつぶし, swallowed e...
Design document review format with 100-point scoring system for SOW/Spec. Use when reviewing SOW or Spec documents, scoring design quality, or when user mentions SOW review, Spec review, 設計書レビュー, 品質ス...
Design document review format with 100-point scoring system for SOW/Spec. Triggers: SOW review, Spec review, document scoring, 設計書レビュー, 品質スコア.
React and Next.js performance optimization guidelines from Vercel Engineering. Use when writing, reviewing, or refactoring React/Next.js code, improving Web Vitals, or when user mentions React performance, Next...
Frontend performance optimization with data-driven approach. Use when optimizing page load times, improving Web Vitals, or when user mentions performance, Web Vitals, LCP, FID, CLS, パフォーマンス最適化, 速度改...
Generate environment setup guide documentation from codebase analysis. Detects package managers, required tools, environment variables, and startup commands. Triggers: setup guide, environment setup, developmen...
CSS-first approach - use CSS before JavaScript. Triggers: レイアウト, スタイル, 位置, アニメーション, 表示/非表示, トグル, レスポンシブ, CSS Grid, Flexbox, transforms, transitions, CSSのみ, JavaScript不要, シン...
Generate domain documentation from codebase analysis - entities, glossary, relationships. Use when analyzing domain models, creating glossaries, or when user mentions domain model, entity diagram, ドメインモデ...
Storybook integration with spec.md. Auto-generates Stories from Component API. Use when creating Storybook stories, defining component APIs, or when user mentions storybook, stories, props, argTypes, variants,...
Browser automation using agent-browser CLI. Best for E2E testing, demos, screenshots. Use when automating browser interactions, creating E2E tests, or when user mentions browser automation, E2E test, ブラウザ操...
TypeScript type safety patterns and best practices for maximum type coverage. Triggers: TypeScript, type safety, any, 型安全, 型カバレッジ, strict mode.
Fundamental software principles - SOLID, DRY, Occam's Razor, Miller's Law, YAGNI, Readable Code. Triggers: 原則, シンプル, 複雑, アーキテクチャ, リファクタリング, 保守性, コード品質, design pattern, best practi...
Command workflow orchestration patterns for /code, /fix, /audit, and other implementation commands. Use when implementing features with /code, /fix, /audit commands, or when user mentions workflow, ワークフロー...
CLI tools guide for git, gh, npm, and other development tools. Triggers: git, gh, npm, CLI, コマンドライン, バージョン管理, ブランチ, コミット.
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
Code readability review based on "The Art of Readable Code" and Miller's Law (7±2). Use when reviewing code clarity, improving naming, or when user mentions 可読性, 理解しやすい, わかりやすい, 明確, 命名, 変数...
Access Google Sheets and Docs via gcloud CLI. Use when user shares a Google Sheets/Docs URL or mentions スプレッドシート, Sheets, Docs, Google ドキュメント.
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.