Replace manual file commands with automated rake/yarn scripts

Update formatting documentation to use proper automated commands:
- Use `rake autofix` instead of manual `npx prettier --write <files>`
- Use `yarn start format.listDifferent` for checking
- Use `git add .` instead of manual file listing
- Emphasize automated workflow over manual file management

This makes the process much more reliable and less error-prone.

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <[email protected]>

Author: justin808

CLAUDE.md

@@ -40,24 +40,24 @@ These requirements are non-negotiable. CI will fail if not followed.
 
 ### Standard Workflow
 1. Make code changes
-2. Run `npx prettier --write <files>` or `rake autofix`
+2. Run `rake autofix` or `yarn start format`
 3. Commit changes
 
 ### Merge Conflict Resolution Workflow
 **CRITICAL**: When resolving merge conflicts, follow this exact sequence:
 
 1. **Resolve logical conflicts only** - don't worry about formatting
-2. **Add resolved files**: `git add <conflicted-files>`
-3. **Let Prettier format**: `npx prettier --write <conflicted-files>`
-4. **Add formatted files**: `git add <conflicted-files>` (if Prettier made changes)
+2. **Add resolved files**: `git add .` (or specific files)
+3. **Auto-fix everything**: `rake autofix`
+4. **Add any formatting changes**: `git add .`
 5. **Continue rebase/merge**: `git rebase --continue` or `git commit`
 
 **❌ NEVER manually format during conflict resolution** - this causes formatting wars between tools.
 
 ### Debugging Formatting Issues
-- Check current formatting: `npx prettier --check .`
-- Fix all formatting: `npx prettier --write .`
-- If CI fails on formatting, always run Prettier, never manual fixes
+- Check current formatting: `yarn start format.listDifferent`
+- Fix all formatting: `rake autofix`
+- If CI fails on formatting, always run automated fixes, never manual fixes
 
 ### Development Setup Commands
 

docs/contributor-info/coding-agents-guide.md

@@ -356,9 +356,9 @@ git checkout HEAD~1 -- Gemfile package.json  # Rollback versions
 
 **Merge conflict resolution workflow:**
 1. Resolve logical conflicts only (ignore formatting)
-2. `git add <resolved-files>`
-3. `npx prettier --write <resolved-files>`
-4. `git add <resolved-files>` (if Prettier made changes)
+2. `git add .` (or specific files)
+3. `rake autofix` (fixes all formatting + linting)
+4. `git add .` (if autofix made changes)
 5. Continue rebase: `git rebase --continue`
 
 **Never manually format during conflict resolution** - this causes formatting wars.

docs/contributor-info/linters.md

@@ -37,24 +37,23 @@ Autofixing is a **HUGE** time saver!
 
 ```bash
 # Check formatting
-npx prettier --check .
+yarn start format.listDifferent
 
-# Fix formatting
-npx prettier --write .
-
-# Or use project scripts
+# Fix formatting (includes all linters)
 rake autofix
-yarn start format.listDifferent  # check only
+
+# Or format only
+yarn start format
 ```
 
 ### Merge Conflict Resolution
 
 When resolving merge conflicts, **NEVER manually format**. Follow this sequence:
 
 1. Resolve logical conflicts only
-2. `git add <resolved-files>`
-3. `npx prettier --write <resolved-files>`
-4. `git add <resolved-files>` (if Prettier made changes)
+2. `git add .` (or specific files)
+3. `rake autofix` (fixes all formatting + linting)
+4. `git add .` (if autofix made changes)
 5. Continue with `git rebase --continue` or `git commit`
 
 **Why this matters**: Manual formatting during conflict resolution creates "formatting wars" between tools and leads to back-and-forth formatting changes in PRs.