Use when writing a git commit message or a PR title in this repo — the Conventional Commits format (type(scope): subject). Follow this whenever you are about to commit, the user asks to commit changes, or mentions コミット, commit message, or a PR title, even if they do not name the convention. Follows docs/commit.md.
Use when writing or updating a feature design document in this repo — the design-first law that no feature is implemented without a design at docs/ /{ID}slug.md. Follow this whenever you are about to design a feature, assign a feature ID, copy a domain template.md, or the user mentions 設計, 設計ドキュメント, design doc…
Use when filing a GitHub issue in this repo — the multilingual 'English follows Japanese' format with a background/tasks structure. Follow this whenever you open or draft an issue, or the user mentions issue 起票, 課題を立てる, or filing a bug or feature request, even if they do not say 'issue' explicitly. Follows…
Use when handling a pull request in this repo — creating a branch, writing the PR body, review, squash-merge, or post-merge branch cleanup. Follow this whenever you open or draft a PR, or the user mentions PR を出す, プルリク, squash merge, or branch 削除, even if they do not say 'pull request' explicitly. Follows docs/pr.md.
Use when writing production code in this repo via test-driven development — the t-wada style Red -> Green -> Refactor cycle, one test at a time. Follow this whenever you are about to implement a feature or bugfix, write a failing test first, or the user mentions TDD, テスト駆動, Red/Green/Refactor, or テストを先に書く, even if…
Claude Code instructions for haribote/thmh, a project described as: Story-less UI component catalog for the AI era — auto-generated from your code, served by a Vite plugin, exposed to agents via MCP.