
Create a git commit following Conventional Commits. Use when the user asks to commit changes.
Read user's inline notes in plan.md and update the plan accordingly. Never implements code.
Create a HANDOVER.md file summarizing the current session for context continuity. Use when switching sessions or before ending work.
Execute the full implementation plan in plan.md. Implements all tasks, marks progress, and runs checks continuously.
This skill should be used when the user asks to "optimize CLAUDE.md", "review CLAUDE.md", "clean up instructions", "CLAUDE.md最適化", "指示ファイルの見直し", "CLAUDE.mdの無駄を削除".
Create a detailed implementation plan in plan.md. Never implements code. Use after /research or when planning a feature.
Deep-read a codebase area and write findings to research.md. Use for thorough investigation before planning.
Apply UX psychology principles when building UI components, forms, pricing pages, onboarding flows, checkout experiences, modals, or any user-facing interface. Use when designing CTAs, implementing progress indicators, creating loading states, improving user engagement, or reviewing UI for psychological effectiveness.
Research web pages using agent-browser — a headless browser CLI that renders JavaScript and handles dynamic content. Use this skill as a fallback when WebSearch or WebFetch fails, returns insufficient results, or when the target page requires JS rendering (SPAs, dynamic docs). Also use when the user provides a specific URL to investigate, when you need to navigate multi-page documentation, or when summarizing web content that WebFetch cannot parse properly.
Statically investigate latent bugs in existing code. Use on "bug hunt", "latent bugs", "code audit".
Review code for logging quality or add proper logging to code. Use when asked to "add logging", "review logging", "improve logs", "ログ追加", "ログレビュー", "ログ改善", "ログ実装". Also use when the user wants to replace print/console.log with proper logging, improve observability or debuggability, add error context for troubleshooting, or asks about logging best practices. Trigger phrases include "print文を置き換え", "エラーログ", "デバッグログ", "トラブルシュート", "observability", "ログ設計".
Guide TDD workflow with Red-Green-Refactor cycle. Use when the user asks to "write tests first", "TDD", "test-driven", "テスト駆動", "TDDで実装", "テストファースト".