chore(docs): add co-author rules and standardize branch naming

- Add critical rules 10-11 prohibiting co-author information and
  generated-by statements on commits and pull requests
- Standardize branch naming to 3-part format: type/scope/short-description

Author: CalvinAllen

CLAUDE.md

@@ -10,11 +10,13 @@ This file provides guidance to Claude Code (claude.ai/code) when working with co
 2. **Conventional commits** - Format: `type(scope): description`
 3. **GitHub Issues for TODOs** - Use `gh` CLI to manage issues, no local TODO files. Use conventional commit format for issue titles
 4. **Pull Request titles** - Use conventional commit format (same as commits)
-5. **Branch naming** - Use format: `type/short-description` (e.g., `feat/settings-dialog`)
+5. **Branch naming** - Use format: `type/scope/short-description` (e.g., `feat/ui/settings-dialog`)
 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. **Microsoft coding guidelines** - Follow [Microsoft C# coding conventions](https://learn.microsoft.com/en-us/dotnet/csharp/fundamentals/coding-style/coding-conventions) and [.NET library design guidelines](https://learn.microsoft.com/en-us/dotnet/standard/design-guidelines/)
 9. **WinUI 3 for all UI** - All UI must use WinUI 3/XAML with modern styling (Fluent Design, theme resources, no hardcoded colors except brand purple #68217A)
+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
 
 ---