Review an existing CLAUDE.md, identify gaps, and refine it through targeted questions. Then ask broader project questions to capture learnings in MEMORY.md. Use after /cmd-generator or whenever the CLAUDE.md feels incomplete. Triggers: "clarify", "確認", "深掘り", "CLAUDE.md確認", "もっと詳しく", "refine CLAUDE.md".
Session retrospective: review what was done, identify reusable patterns worth turning into skills. Use at the end of a session to extract learnings and skill candidates. Triggers: "振り返り", "retrospective", "retro", "セッション振り返り", "スキル化できるものある?", "今日の振り返り".
Generate effective CLAUDE.md files for Claude Code projects. Use when the user wants to create, improve, or review a CLAUDE.md file. Triggers: "CLAUDE.md", "Claude Code設定", "プロジェクト設定ファイルを作りたい", requests to set up Claude Code for a repository, or mentions of making Claude Code understand a project better.
Build verification → Type check → Tests → Git commit workflow. Use when the user wants to commit changes with quality gates. Triggers: "コミット", "commit", "変更をコミットして", "push前の確認".
Comprehensive code review: security, edge cases, performance, maintainability. Use before public release, major versions, or production deployment. Triggers: "レビュー", "review", "セキュリティ監査", "公開前チェック", "リリース準備", "コードレビューして".
Test-driven development: write tests first, implement until they pass. Use when implementing features with complex logic that benefits from test-first approach. Triggers: "TDDで", "テスト駆動", "テストファーストで実装", "tdd", "バグを防ぎたい", "テストから書いて".
Verify full-stack connectivity: backend running, proxy configured, endpoints responding. Use when the user implements full-stack features or reports connection errors. Triggers: "スタック確認", "接続確認", "verify stack", "サーバー動いてる?", "ERR_CONNECTION_REFUSED", "API繋がらない", "プロキシ設定".