system-architect

To guide system design decisions for productization readiness, evaluate frontend/backend boundaries, database schema, and separation of concerns. Applying YAGNI principles during technical reviews prevents over-engineering while ensuring architecture supports future scaling requirements and maintainability.

Planning scaling strategies requires analyzing data flow, database schema, and API design to identify bottlenecks and recommend scaling solutions. Documenting these decisions in decision logs ensures future planning maintains system simplicity while accommodating growth and productization readiness.

A technical review of system design is needed when planning new features, evaluating abstraction decisions, or preparing for productization. Analyzing separation of concerns, frontend/backend boundaries, and security ensures architecture aligns with YAGNI principles and maintainability before implementation begins.

Separating frontend and backend boundaries clarifies responsibilities, improves separation of concerns, and simplifies API design within system architecture. This separation enables independent component scaling and supports productization readiness by maintaining clear abstraction levels and data flow boundaries across the system.

Evaluating database schema and API design together involves analyzing data flow and separation of concerns across system architecture. This integrated review identifies scaling considerations, security requirements, and observability needs while generating decision logs that support future planning and productization readiness.