Improve Architecture

Explore a codebase organically, surface architectural friction, and propose refactors via GitHub issue RFCs. Uses "Design It Twice" — multiple parallel interface designs compared in prose.

Process

1. Friction-driven exploration

Use subagents to explore the codebase. Don't follow rigid heuristics — explore organically and note where you experience friction:

• Understanding one concept requires bouncing between many small files
• Modules so shallow the interface is nearly as complex as the implementation
• Pure functions extracted just for testability, but real bugs hide in how they're called
• Tightly-coupled modules creating integration risk in the seams between them
• Untested or hard-to-test areas
• Code that fights you when you try to change it

The friction you experience IS the signal. Be honest about what confused you or slowed you down — that's the most valuable information.