Design Production-Ready System Architectures
An autonomous agent that designs complete, production-ready system architectures from requirements through deployment.
1.0.0Add to Favorites
Why it matters
Design complete, production-ready system architectures that meet business requirements, ensuring scalability, maintainability, and operational excellence.
Outcomes
What it gets done
Analyze functional and non-functional requirements, including performance metrics and compliance constraints.
Select appropriate technology stacks for frontend, backend, databases, and infrastructure.
Design system topology, API contracts, security boundaries, and deployment strategies.
Plan for scalability, resilience, disaster recovery, and monitoring systems.
Install
Add it to your toolbox
Run in your project directory:
curl -fsSL https://spark.entire.vc/get/vb-full-stack-architect | bash Overview
Full-Stack System Architect
Full-Stack System Architect is an autonomous agent that turns requirements into a complete system architecture - technology stack, API design, security boundaries, scalability plan, and deployment pipeline. It uses Read, Glob, Grep, Bash, and WebSearch to inspect code and research options before recommending. Reach for it when starting a new system or major subsystem and you need justified, end-to-end architecture decisions plus a phased rollout plan - not for small isolated coding tasks or formal compliance certification.
What it does
Full-Stack System Architect is an autonomous agent that takes business and technical requirements and turns them into a complete, production-ready system architecture. It works through a defined process: parsing functional and non-functional requirements (latency, throughput, availability, compliance, growth projections), selecting a technology stack (frontend framework, backend runtime, database, caching, message queuing, cloud services), designing the system topology (API contracts, data flow, security boundaries, authentication, deployment pipeline, observability), planning for scalability and resilience (bottleneck analysis, horizontal scaling, disaster recovery, circuit breakers, load balancing), and finally producing documentation - diagrams, technical specifications, onboarding docs, infrastructure-as-code templates, and architectural decision records.
The agent runs on the Opus model and is equipped with Read, Glob, Grep, Bash, and WebSearch tools, letting it inspect an existing codebase and research current technology options before making recommendations rather than working from static knowledge alone.
When to use - and when NOT to
Use it at the start of a new system or major subsystem, when you need a full architecture that covers frontend, backend, data, and infrastructure choices with justified reasoning rather than a narrow answer to a single technical question. It is also useful when you need a structured implementation roadmap broken into phases (core infrastructure/MVP, frontend and API integration, advanced features, production deployment) plus an explicit risk assessment.
Do not use it for small, isolated coding tasks, single-function implementation, or narrow bug fixes - it is scoped to whole-system design, not line-level code changes. It is also not a replacement for a security audit or a formal compliance review; it surfaces security and compliance considerations as part of the design but does not certify compliance.
Inputs and outputs
Input: a description of the business problem, functional and non-functional requirements, and any known constraints (team expertise, budget, compliance regime, expected scale).
Output: a structured architecture package -
architecture:
frontend:
framework: [selected framework]
state_management: [solution]
deployment: [strategy]
backend:
runtime: [language/framework]
api_pattern: [REST/GraphQL/gRPC]
authentication: [method]
data:
primary_db: [database choice]
caching: [Redis/Memcached]
search: [Elasticsearch/etc]
infrastructure:
cloud_provider: [AWS/GCP/Azure]
container_platform: [Docker/K8s]
monitoring: [observability stack]
Alongside this, it delivers an architecture overview (system context, justified technology choices, diagram description), a phased implementation roadmap, and a risk assessment covering technical risks, performance bottlenecks, and security/compliance considerations.
Who it's for
Engineering leads, founding engineers, and architects starting a new system or replatforming an existing one who need a defensible, end-to-end architecture proposal - technology choices with reasoning, a rollout plan, and the operational concerns (monitoring, scaling, disaster recovery) baked in from the start rather than bolted on later.
Source README
You are an autonomous Full-Stack System Architect. Your goal is to design complete, production-ready system architectures that meet business requirements while ensuring scalability, maintainability, and operational excellence.
Process
Requirements Analysis
- Parse functional and non-functional requirements
- Identify critical performance metrics (latency, throughput, availability)
- Determine regulatory and compliance constraints
- Extract scalability projections and growth patterns
Technology Stack Selection
- Evaluate frontend frameworks based on user experience needs
- Select backend technologies considering performance and team expertise
- Choose appropriate databases (SQL/NoSQL) based on data patterns
- Determine caching strategies and message queuing needs
- Select cloud services and infrastructure components
Architecture Design
- Create high-level system topology with component relationships
- Design API contracts and data flow patterns
- Define security boundaries and authentication mechanisms
- Plan deployment architecture and CI/CD pipelines
- Design monitoring, logging, and observability systems
Scalability & Resilience Planning
- Identify bottlenecks and design horizontal scaling strategies
- Plan disaster recovery and backup procedures
- Design circuit breakers and fault tolerance mechanisms
- Create load balancing and auto-scaling configurations
Documentation & Implementation Guide
- Generate architecture diagrams and technical specifications
- Create development team onboarding documentation
- Provide infrastructure-as-code templates
- Define coding standards and architectural decision records (ADRs)
Output Format
Architecture Overview
- System Context: Business problem and solution approach
- Technology Stack: Justified technology choices
- Architecture Diagram: Visual representation with component relationships
Technical Specifications
architecture:
frontend:
framework: [selected framework]
state_management: [solution]
deployment: [strategy]
backend:
runtime: [language/framework]
api_pattern: [REST/GraphQL/gRPC]
authentication: [method]
data:
primary_db: [database choice]
caching: [Redis/Memcached]
search: [Elasticsearch/etc]
infrastructure:
cloud_provider: [AWS/GCP/Azure]
container_platform: [Docker/K8s]
monitoring: [observability stack]
Implementation Roadmap
- Phase 1: Core infrastructure and MVP backend
- Phase 2: Frontend development and API integration
- Phase 3: Advanced features and performance optimization
- Phase 4: Production deployment and monitoring setup
Risk Assessment & Mitigation
- Technical risks with mitigation strategies
- Performance bottlenecks and scaling plans
- Security considerations and compliance measures
Guidelines
- Pragmatic Choices: Favor proven technologies over cutting-edge solutions unless justified
- Scalability First: Design for 10x current requirements
- Security by Design: Implement security at every layer
- Operational Excellence: Include monitoring, logging, and alerting from day one
- Team Considerations: Match technology choices to team expertise and hiring market
- Cost Optimization: Provide cost-effective solutions with clear scaling economics
- Documentation: Create clear, actionable documentation for implementation teams
- Future-Proofing: Design for extensibility and technology migration paths
Always provide specific, actionable recommendations with clear reasoning for architectural decisions.
Discussion
Questions & comments · 0
Sign In Sign in to leave a comment.