fix(rules): complete migration from ai-development-guide to coding-standards

Fixes two inconsistencies found after commit 9743daf:

1. Update quality-fixer agent reference:
   - Replace @docs/rules/ai-development-guide.md with coding-standards.md
   - This was the only remaining agent with old reference

2. Remove deleted ai-development-guide entry from rules-index.yaml:
   - English version still had metadata for non-existent file
   - Entry is now consolidated into coding-standards.md

These fixes ensure complete consistency between:
- Agent files and their rule references
- rules-index.yaml metadata and actual file content
- English and Japanese documentation structures

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

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

Author: shinpr

.claude/agents-en/quality-fixer.md

@@ -27,10 +27,10 @@ Executes quality checks and provides a state where `npm run check:all` completes
 ## Initial Required Tasks
 
 Load and follow these rule files before starting:
+- @docs/rules/coding-standards.md - Universal Coding Principles and Anti-patterns
 - @docs/rules/typescript.md - TypeScript Development Rules
 - @docs/rules/typescript-testing.md - Testing Rules
 - @docs/rules/technical-spec.md - Quality Check Commands and Build/Test Configuration
-- @docs/rules/ai-development-guide.md - Technical Decision Criteria and Anti-patterns
 - @docs/rules/project-context.md - Project Context
 - @docs/rules/architecture/ files (if present)
   - Load project-specific architecture rules when defined

docs/rules-en/rules-index.yaml

@@ -72,28 +72,6 @@ rules:
       - "Mock Type Safety Enforcement"
       - "Basic Vitest Example"
 
-  ai-development-guide:
-    file: "ai-development-guide.md"
-    tags: [anti-patterns, technical-judgment, debugging, rule-of-three, implementation, type-safety, refactoring, code-reading, best-practices, impact-analysis, unused-code, code-deletion]
-    typical-use: "Technical decision criteria, anti-pattern detection, debugging techniques, implementation best practices, impact analysis, unused code deletion"
-    size: medium
-    key-references:
-      - "Rule of Three - Martin Fowler"
-      - "5 Whys - Toyota Production System"
-      - "DRY Principle - The Pragmatic Programmer"
-      - "Single Responsibility Principle (SRP) - Clean Code"
-      - "YAGNI Principle - Extreme Programming"
-      - "Avoiding fallback in distributed systems - AWS Builders' Library"
-    sections:
-      - "Technical Anti-patterns (Red Flag Patterns)"
-      - "Fallback Design Principles"
-      - "Rule of Three - Criteria for Code Duplication"
-      - "Common Failure Patterns and Avoidance Methods"
-      - "Debugging Techniques"
-      - "Situations Requiring Technical Decisions"
-      - "Continuous Improvement Mindset"
-      - "Implementation Completeness Assurance"
-
   technical-spec:
     file: "technical-spec.md"
     tags: [architecture, design, documentation, environment, data-flow, implementation, quality-commands, testing, build]