Get an architecture review before you commit to a stack
When to use: You're about to pick a framework and database for a new product and want a sanity check.
Flow
-
Describe the serviceUse the engineering skills. We need a real-time collab API — 10k concurrent users, document sync, presence. Compare Node+WebSocket vs Elixir+Phoenix vs Go+gRPC.✓ Copied→ Comparison grounded in real tradeoffs from the respective skills
-
Probe risksFor the choice you'd recommend, what fails at 100k users?✓ Copied→ Concrete scaling cliffs, not generic platitudes
Outcome: A decision doc with tradeoffs and scaling risks identified.
Pitfalls
- Skill over-recommends the framework it has the deepest skill for — Ask it to explicitly state why NOT each option