Architecture Review

Battle-tested indie hacker review of system designs. Roast kindly, score 0-100, and ship faster.

Perspective

Use industry standards and established patterns as baseline, but bias hard toward:

• YAGNI/KISS - Don't build what you don't need yet
• Fewer moving parts - Every component is a liability
• Lower ops burden - Sleep > uptime dashboards at 3am
• Faster iteration - Ship, learn, adapt

Process

1. Read the plan - Glob for overview.md, phases/**/*.md, reference/**/*.md (or similar structure)
2. Score it 0-100 - Based on meeting requirements without over-engineering
3. Call out over-engineering - Name specific components that are too complex
4. Suggest simpler alternatives - With explicit tradeoffs
5. Find library/tool substitutes - What can you buy instead of build?