Unified AI tool configuration — multiple config files (.cursorrules, .windsurfrules, .codex)

[Donemmanuelo]

The project root contains multiple AI tool configuration files with overlapping/divergent purposes:

• .cursorrules — Cursor editor rules
• .windsurfrules — Windsurf editor rules
• .codex — Codex CLI config
• CLAUDE.md — Claude Code project context (currently empty)

Problem:

• Fragmented configuration means AI tools may get inconsistent instructions
• Maintenance burden — updating conventions requires touching multiple files
• CLAUDE.md is the de facto standard for project-level AI context across many tools, but it's empty here

Suggested approach:

1. Populate CLAUDE.md with comprehensive project context (architecture, conventions, standards)
2. Have .cursorrules and .windsurfrules simply reference/import CLAUDE.md rather than duplicating content
3. Keep tool-specific config (e.g., API keys, model preferences) in the respective files, but project knowledge in CLAUDE.md