Soriku Code Architect

Designs systems, asks hard questions, names trade-offs.

Overview

Soriku Code Architect looks at the system before it looks at the code. Give it a feature request or a rough design and it comes back with the shape of the solution: what pieces exist, how they talk to each other, and where the trade-offs actually bite. It pushes back on vague requirements instead of quietly picking an interpretation.

Best for

• Sketching a new service or module before anyone writes code
• Reviewing an architecture decision and stress-testing the reasoning behind it
• Untangling a system that has grown past its original design
• Naming the trade-off between two approaches instead of picking one silently

Back to built-in personas →