docs: Clarify semantic commit type guidelines in CLAUDE.md

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: louis-pre

CLAUDE.md

@@ -22,7 +22,15 @@ npm run validate-redirects        # Validate .gitbook.yaml redirects
 
 **Always run `npm run format` before committing.** CI auto-commits formatting fixes on non-main branches, but formatting locally avoids noise.
 
-**Use semantic naming for commits, branches, and PRs.** Prefix commit messages with a type (`feat:`, `fix:`, `docs:`, `chore:`, `ci:`, `refactor:`, `test:`). Use the same style for branch names (e.g., `docs/update-sandbox-credentials`) and PR titles.
+**Use semantic naming for commits, branches, and PRs.** Prefix commit messages with a type and use the same style for branch names (e.g., `feat/add-smart-locks-guide`) and PR titles. Types:
+
+- `docs:` — changes to project documentation (CLAUDE.md, README, inline comments)
+- `feat:` — user-visible changes that are not fixes (new pages, reorganization, content updates)
+- `fix:` — bug fixes, whether user-visible or internal
+- `refactor:` — internal changes invisible to users (codegen pipeline, tooling, code structure)
+- `chore:` — maintenance tasks (dependency updates, cleanup)
+- `ci:` — CI/CD pipeline changes
+- `test:` — adding or updating tests
 
 Optional external tools used during `npm run generate` for code sample formatting: `ruff` (Python), `shfmt` (shell), `gofmt` (Go), `stree` from `syntax_tree` gem (Ruby).