chore(claude): standardize requirements

Author: CalvinAllen

.gitignore

@@ -282,3 +282,5 @@ $RECYCLE.BIN/
 
 # Claude Code local settings
 .claude/settings.local.json
+
+CLAUDE.local.md

CLAUDE.md

@@ -2,6 +2,43 @@
 
 This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
 
+## Critical Rules
+
+**These rules override all other instructions:**
+
+1. **NEVER commit directly to main** - Always create a feature branch and submit a pull request
+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/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. **WPF for all UI** - All UI must be implemented using WPF (XAML/C#). No web-based technologies (HTML, JavaScript, WebView)
+
+---
+
+### GitHub CLI Commands
+
+```bash
+gh issue list                    # List open issues
+gh issue view <number>           # View details
+gh issue create --title "type(scope): description" --body "..."
+gh issue close <number>
+```
+
+### Conventional Commit Types
+
+| Type | Description |
+|------|-------------|
+| `feat` | New feature |
+| `fix` | Bug fix |
+| `docs` | Documentation only |
+| `refactor` | Code change that neither fixes a bug nor adds a feature |
+| `test` | Adding or updating tests |
+| `chore` | Maintenance tasks |
+
+---
+
 ## Project Overview
 
 This is a Visual Studio 2022 extension (VSIX) called "Project Renamifier" that allows users to rename projects completely from within Visual Studio, including the filename, parent folder, namespace, and references in the solution file and other projects.
@@ -53,38 +90,3 @@ Key points:
 - Use meaningful, descriptive names
 - Prefer `async`/`await` for asynchronous operations
 - Use `ThreadHelper.ThrowIfNotOnUIThread()` when accessing VS services that require the UI thread
-
----
-
-## Workflow Rules
-
-**These rules must be followed:**
-
-1. **NEVER commit directly to main** - Always create a feature branch and submit a pull request. No exceptions.
-2. **Conventional commits** - Format: `type(scope): description`
-3. **GitHub Issues for TODOs** - Use `gh` CLI to manage issues; use conventional commit format for issue titles
-4. **Pull Request titles** - Use conventional commit format (same as commits)
-5. **Branch naming** - Use format: `type/scope/short-description` (e.g., `feat/rename/user-input-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
-8. **No AI attribution in commits** - Do NOT include "Generated with Claude Code", "Co-Authored-By: Claude", or similar AI attribution lines in commit messages
-
-### GitHub Issues
-
-```bash
-gh issue list                    # List open issues
-gh issue view <number>           # View details
-gh issue create --title "feat(rename): add user input dialog" --body "..."
-gh issue close <number>
-```
-
-### Conventional Commit Types
-
-| Type | Description |
-|------|-------------|
-| `feat` | New feature |
-| `fix` | Bug fix |
-| `docs` | Documentation only |
-| `refactor` | Code change that neither fixes a bug nor adds a feature |
-| `test` | Adding or updating tests |
-| `chore` | Maintenance tasks |