docs: add critical rules and perf/ci commit types (#31)

Author: CalvinAllen

CLAUDE.md

@@ -13,8 +13,10 @@ This file provides guidance to Claude Code (claude.ai/code) when working with co
 5. **Branch naming** - Use format: `type/scope/short-description` (e.g., `feat/blog/new-post-script`)
 6. **Working an issue** - Always create a new branch from an updated main branch
 7. **Check branch status before pushing** - Verify the remote tracking branch still exists. If a PR was merged/deleted, create a new branch from main instead
-8. **No co-authors** - Do not add co-author information on commits or pull requests
-9. **No "generated by" statements** - Do not add generated-by statements on pull requests
+8. **Write tests** - All new/refactored code requires tests where applicable
+9. **Run validation before commits** - Run `npm run build` and verify no errors before committing
+10. **No co-authors** - Do not add co-author information on commits or pull requests
+11. **No "generated by" statements** - Do not add generated-by statements on pull requests
 
 ### Conventional Commit Types
 
@@ -26,6 +28,8 @@ This file provides guidance to Claude Code (claude.ai/code) when working with co
 | `refactor` | Code change that neither fixes a bug nor adds a feature |
 | `test` | Adding or updating tests |
 | `chore` | Maintenance tasks |
+| `perf` | Performance improvement |
+| `ci` | CI/CD changes |
 
 ### GitHub CLI Commands