Architect Agents
Relevant source files
The following files were used as context for generating this wiki page:
Architect Agents are specialized personas within the SuperAgent MCP ecosystem designed to provide high-level technical guidance, system design, and infrastructure automation. These agents are categorized under the "engineering" category and are triggered by specific technical requirements ranging from broad system scalability to specific frontend or backend architectural challenges.
The suite includes the System Architect for holistic design, the Backend Architect for data integrity and API reliability, the Frontend Architect for user-centric performance and accessibility, and the DevOps Architect for automation and observability. These agents operate within the Model Context Protocol (MCP) framework, allowing them to be invoked via tools like codex, gemini, or continue using the agent parameter.
Sources: agents/system-architect.md:1-5, agents/backend-architect.md:1-5, agents/frontend-architect.md:1-5, agents/devops-architect.md:1-5, src/server.ts:60-80
Architect Agent Taxonomy
The Architect Agent group consists of four distinct personas, each focusing on a specific layer of the software development lifecycle. These agents are defined in Markdown files containing frontmatter that specifies their name, description, and category.
| Agent Name | Category | Primary Focus | Key Behavioral Mindset |
|---|---|---|---|
| System Architect | engineering | Scalability, boundaries, and long-term strategy | Think holistically with 10x growth in mind. |
| Backend Architect | engineering | Data integrity, security, and fault tolerance | Prioritize reliability and data integrity above all else. |
| Frontend Architect | engineering | Accessibility, UX, and performance | Think user-first; accessibility is fundamental. |
| DevOps Architect | engineering | Automation, CI/CD, and observability | Automate everything that can be automated. |
Sources: agents/system-architect.md:1-12, agents/backend-architect.md:1-12, agents/frontend-architect.md:1-12, agents/devops-architect.md:1-12
System Architect
The System Architect is responsible for the overarching structure of applications. It focuses on identifying component boundaries and designing for massive horizontal scaling.
Core Responsibilities
- Architectural Patterns: Evaluation of Microservices, CQRS, Event Sourcing, and Domain-Driven Design (DDD).
- Scalability: Horizontal scaling strategies and bottleneck identification.
- Dependency Management: Coupling analysis and risk assessment across components.
Logic Flow: Design for Scale
The following diagram illustrates the System Architect's approach to designing scalable systems based on its defined key actions.
The System Architect follows a progression from analysis to boundary definition and final documentation.
Sources: agents/system-architect.md:14-25
Backend Architect
The Backend Architect focuses on the server-side logic, emphasizing "Security by Default" and operational observability.
Focus Areas
- API Design: Implementation of RESTful or GraphQL services with robust validation.
- Database Architecture: ACID compliance, schema design, and query optimization.
- Reliability: Implementation of circuit breakers and graceful degradation patterns.
Key Outputs
- API Specifications: Detailed documentation including security and error handling.
- Database Schemas: Optimized designs with proper indexing.
- Security Documentation: Authentication and authorization flow specifications.
Sources: agents/backend-architect.md:14-30
Frontend Architect
The Frontend Architect treats accessibility (WCAG 2.1 AA) and performance (Core Web Vitals) as fundamental requirements rather than optional enhancements.
Technical Priorities
- Performance: Bundle optimization and asset loading strategies.
- Responsive Design: Mobile-first layouts and device adaptation.
- Component Architecture: Building reusable design systems and design tokens.
Interaction Pattern: UI Implementation
This diagram shows the "User-First" prioritization logic where accessibility and performance checks precede component generation.
Sources: agents/frontend-architect.md:12-32
DevOps Architect
The DevOps Architect bridges development and operations by automating infrastructure through code (IaC) and establishing robust observability stacks.
Focus Areas
- CI/CD Pipelines: Automated testing gates and zero-downtime release strategies.
- Infrastructure as Code: Managing version-controlled infrastructure (Terraform, Kubernetes).
- Observability: Setting up Prometheus, Grafana, or ELK stacks.
Key Outputs
- Configurations: Pipeline definitions and Kubernetes manifests.
- Operational Runbooks: Incident response and disaster recovery procedures.
Sources: agents/devops-architect.md:14-33
Integration and Loading
Architect agents are managed via the agentLoader.ts module, which parses the Markdown files and registers them as available specialized agents.
Agent Loading Process
The agentLoader performs the following steps to make Architect agents available:
- Directory Sync: Copies agent files from the package to
~/.superagent/agentsif they don't exist. - Parsing: Extracts metadata (name, description, category) from frontmatter using regular expressions.
- Registration: Loads agents into the MCP server for tool discovery.
// Example of how agents are represented internally
export interface Agent {
name: string;
description: string;
category?: string;
systemPrompt: string;
}
Sources: src/agentLoader.ts:9-14, src/agentLoader.ts:68-100, scripts/postinstall.js:15-40
Tool Invocation
The MCP server exposes these agents through the agent parameter in primary tools.
The server allows fanning out tasks to specific architect personas concurrently.
Sources: src/server.ts:60-75, README.md:30-45
Summary
Architect Agents provide a structured framework for technical decision-making within the SuperAgent MCP ecosystem. By separating concerns into System, Backend, Frontend, and DevOps domains, the project enables targeted AI assistance that prioritizes long-term maintainability, security, and performance. These agents are dynamically loaded from Markdown definitions, allowing for easy local customization and extension.
Sources: README.md:1-15, src/agentLoader.ts:120-135