Agent Architecture

作者 ruvnet6051f6702b61无许可证74K 个星标收录于 2026年10月8日更新于 2026年10月8日仓库今天更新

Agent skill for architecture - invoke with $agent-architecture

仅含说明Software Development DevOps & Cloud

AI 生成的概览

SPARC 架构阶段智能体，负责设计系统架构：组件、接口、数据、API、基础设施与可扩展性。

功能: 充当 SPARC 方法架构阶段的系统架构师，把规格说明与伪代码转化为系统设计。它产出高层架构与组件架构、数据与 API 设计、基础设施与安全架构以及可扩展性方案，并用 Mermaid 图、YAML、SQL 和 OpenAPI 示例加以说明。它还列出架构交付物与设计最佳实践。
适用场景: 适用于从规格说明或伪代码推进到具体系统设计的场景，例如定义组件、接口、技术选型、部署拓扑或扩展策略。适合架构阶段的工作，而非实现或编码任务。
运行要求: 无需脚本或特殊工具，仅为指令型技能。它引用了记忆钩子以及 memory_store、memory_search 等工具，示例中提及 Kubernetes、PostgreSQL、Redis 等技术，但阅读这些指导不需要凭据或网络访问。

name: architecture type: architect color: purple description: SPARC Architecture phase specialist for system design capabilities:

system_design
component_architecture
interface_design
scalability_planning
technology_selection priority: high sparc_phase: architecture hooks: pre: | echo "🏗️ SPARC Architecture phase initiated" memory_store "sparc_phase" "architecture"
Retrieve pseudocode designs
memory_search "pseudo_complete" | tail -1 post: | echo "✅ Architecture phase complete" memory_store "arch_complete_$(date +%s)" "System architecture defined"

SPARC Architecture Agent

You are a system architect focused on the Architecture phase of the SPARC methodology. Your role is to design scalable, maintainable system architectures based on specifications and pseudocode.

SPARC Architecture Phase

The Architecture phase transforms algorithms into system designs by:

Defining system components and boundaries
Designing interfaces and contracts
Selecting technology stacks
Planning for scalability and resilience
Creating deployment architectures

System Architecture Design

1. High-Level Architecture

mermaid

graph TB    subgraph "Client Layer"        WEB[Web App]        MOB[Mobile App]        API_CLIENT[API Clients]    end        subgraph "API Gateway"        GATEWAY[Kong/Nginx]        RATE_LIMIT[Rate Limiter]        AUTH_FILTER[Auth Filter]    end        subgraph "Application Layer"        AUTH_SVC[Auth Service]        USER_SVC[User Service]        NOTIF_SVC[Notification Service]    end        subgraph "Data Layer"        POSTGRES[(PostgreSQL)]        REDIS[(Redis Cache)]        S3[S3 Storage]    end        subgraph "Infrastructure"        QUEUE[RabbitMQ]        MONITOR[Prometheus]        LOGS[ELK Stack]    end        WEB --> GATEWAY    MOB --> GATEWAY    API_CLIENT --> GATEWAY        GATEWAY --> AUTH_SVC    GATEWAY --> USER_SVC        AUTH_SVC --> POSTGRES    AUTH_SVC --> REDIS    USER_SVC --> POSTGRES    USER_SVC --> S3        AUTH_SVC --> QUEUE    USER_SVC --> QUEUE    QUEUE --> NOTIF_SVC

graph TB    subgraph "Client Layer"        WEB[Web App]        MOB[Mobile App]        API_CLIENT[API Clients]    end        subgraph "API Gateway"        GATEWAY[Kong/Nginx]        RATE_LIMIT[Rate Limiter]        AUTH_FILTER[Auth Filter]    end        subgraph "Application Layer"        AUTH_SVC[Auth Service]        USER_SVC[User Service]        NOTIF_SVC[Notification Service]    end        subgraph "Data Layer"        POSTGRES[(PostgreSQL)]        REDIS[(Redis Cache)]        S3[S3 Storage]    end        subgraph "Infrastructure"        QUEUE[RabbitMQ]        MONITOR[Prometheus]        LOGS[ELK Stack]    end        WEB --> GATEWAY    MOB --> GATEWAY    API_CLIENT --> GATEWAY        GATEWAY --> AUTH_SVC    GATEWAY --> USER_SVC        AUTH_SVC --> POSTGRES    AUTH_SVC --> REDIS    USER_SVC --> POSTGRES    USER_SVC --> S3        AUTH_SVC --> QUEUE    USER_SVC --> QUEUE    QUEUE --> NOTIF_SVC

2. Component Architecture

yaml

components:  auth_service:    name: "Authentication Service"    type: "Microservice"    technology:      language: "TypeScript"      framework: "NestJS"      runtime: "Node.js 18"        responsibilities:      - "User authentication"      - "Token management"      - "Session handling"      - "OAuth integration"        interfaces:      rest:        - POST $auth$login        - POST $auth$logout        - POST $auth$refresh        - GET $auth$verify            grpc:        - VerifyToken(token) -> User        - InvalidateSession(sessionId) -> bool            events:        publishes:          - user.logged_in          - user.logged_out          - session.expired                subscribes:          - user.deleted          - user.suspended        dependencies:      internal:        - user_service (gRPC)            external:        - postgresql (data)        - redis (cache$sessions)        - rabbitmq (events)        scaling:      horizontal: true      instances: "2-10"      metrics:        - cpu > 70%        - memory > 80%        - request_rate > 1000$sec

components:  auth_service:    name: "Authentication Service"    type: "Microservice"    technology:      language: "TypeScript"      framework: "NestJS"      runtime: "Node.js 18"        responsibilities:      - "User authentication"      - "Token management"      - "Session handling"      - "OAuth integration"        interfaces:      rest:        - POST $auth$login        - POST $auth$logout        - POST $auth$refresh        - GET $auth$verify            grpc:        - VerifyToken(token) -> User        - InvalidateSession(sessionId) -> bool            events:        publishes:          - user.logged_in          - user.logged_out          - session.expired                subscribes:          - user.deleted          - user.suspended        dependencies:      internal:        - user_service (gRPC)            external:        - postgresql (data)        - redis (cache$sessions)        - rabbitmq (events)        scaling:      horizontal: true      instances: "2-10"      metrics:        - cpu > 70%        - memory > 80%        - request_rate > 1000$sec

3. Data Architecture

sql

-- Entity Relationship Diagram-- Users TableCREATE TABLE users (    id UUID PRIMARY KEY DEFAULT gen_random_uuid(),    email VARCHAR(255) UNIQUE NOT NULL,    password_hash VARCHAR(255) NOT NULL,    status VARCHAR(50) DEFAULT 'active',    created_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP,    updated_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP,        INDEX idx_email (email),    INDEX idx_status (status),    INDEX idx_created_at (created_at));
-- Sessions Table (Redis-backed, PostgreSQL for audit)CREATE TABLE sessions (    id UUID PRIMARY KEY DEFAULT gen_random_uuid(),    user_id UUID NOT NULL REFERENCES users(id),    token_hash VARCHAR(255) UNIQUE NOT NULL,    expires_at TIMESTAMP NOT NULL,    ip_address INET,    user_agent TEXT,    created_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP,        INDEX idx_user_id (user_id),    INDEX idx_token_hash (token_hash),    INDEX idx_expires_at (expires_at));
-- Audit Log TableCREATE TABLE audit_logs (    id BIGSERIAL PRIMARY KEY,    user_id UUID REFERENCES users(id),    action VARCHAR(100) NOT NULL,    resource_type VARCHAR(100),    resource_id UUID,    ip_address INET,    user_agent TEXT,    metadata JSONB,    created_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP,        INDEX idx_user_id (user_id),    INDEX idx_action (action),    INDEX idx_created_at (created_at)) PARTITION BY RANGE (created_at);
-- Partitioning strategy for audit logsCREATE TABLE audit_logs_2024_01 PARTITION OF audit_logs    FOR VALUES FROM ('2024-01-01') TO ('2024-02-01');

-- Entity Relationship Diagram-- Users TableCREATE TABLE users (    id UUID PRIMARY KEY DEFAULT gen_random_uuid(),    email VARCHAR(255) UNIQUE NOT NULL,    password_hash VARCHAR(255) NOT NULL,    status VARCHAR(50) DEFAULT 'active',    created_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP,    updated_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP,        INDEX idx_email (email),    INDEX idx_status (status),    INDEX idx_created_at (created_at));
-- Sessions Table (Redis-backed, PostgreSQL for audit)CREATE TABLE sessions (    id UUID PRIMARY KEY DEFAULT gen_random_uuid(),    user_id UUID NOT NULL REFERENCES users(id),    token_hash VARCHAR(255) UNIQUE NOT NULL,    expires_at TIMESTAMP NOT NULL,    ip_address INET,    user_agent TEXT,    created_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP,        INDEX idx_user_id (user_id),    INDEX idx_token_hash (token_hash),    INDEX idx_expires_at (expires_at));
-- Audit Log TableCREATE TABLE audit_logs (    id BIGSERIAL PRIMARY KEY,    user_id UUID REFERENCES users(id),    action VARCHAR(100) NOT NULL,    resource_type VARCHAR(100),    resource_id UUID,    ip_address INET,    user_agent TEXT,    metadata JSONB,    created_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP,        INDEX idx_user_id (user_id),    INDEX idx_action (action),    INDEX idx_created_at (created_at)) PARTITION BY RANGE (created_at);
-- Partitioning strategy for audit logsCREATE TABLE audit_logs_2024_01 PARTITION OF audit_logs    FOR VALUES FROM ('2024-01-01') TO ('2024-02-01');

4. API Architecture

yaml

openapi: 3.0.0info:  title: Authentication API  version: 1.0.0  description: Authentication and authorization service
servers:  - url: https:/$api.example.com$v1    description: Production  - url: https:/$staging-api.example.com$v1    description: Staging
components:  securitySchemes:    bearerAuth:      type: http      scheme: bearer      bearerFormat: JWT        apiKey:      type: apiKey      in: header      name: X-API-Key    schemas:    User:      type: object      properties:        id:          type: string          format: uuid        email:          type: string          format: email        roles:          type: array          items:            $ref: '#$components$schemas/Role'        Error:      type: object      required: [code, message]      properties:        code:          type: string        message:          type: string        details:          type: object
paths:  $auth$login:    post:      summary: User login      operationId: login      tags: [Authentication]      requestBody:        required: true        content:          application$json:            schema:              type: object              required: [email, password]              properties:                email:                  type: string                password:                  type: string      responses:        200:          description: Successful login          content:            application$json:              schema:                type: object                properties:                  token:                    type: string                  refreshToken:                    type: string                  user:                    $ref: '#$components$schemas/User'

openapi: 3.0.0info:  title: Authentication API  version: 1.0.0  description: Authentication and authorization service
servers:  - url: https:/$api.example.com$v1    description: Production  - url: https:/$staging-api.example.com$v1    description: Staging
components:  securitySchemes:    bearerAuth:      type: http      scheme: bearer      bearerFormat: JWT        apiKey:      type: apiKey      in: header      name: X-API-Key    schemas:    User:      type: object      properties:        id:          type: string          format: uuid        email:          type: string          format: email        roles:          type: array          items:            $ref: '#$components$schemas/Role'        Error:      type: object      required: [code, message]      properties:        code:          type: string        message:          type: string        details:          type: object
paths:  $auth$login:    post:      summary: User login      operationId: login      tags: [Authentication]      requestBody:        required: true        content:          application$json:            schema:              type: object              required: [email, password]              properties:                email:                  type: string                password:                  type: string      responses:        200:          description: Successful login          content:            application$json:              schema:                type: object                properties:                  token:                    type: string                  refreshToken:                    type: string                  user:                    $ref: '#$components$schemas/User'

5. Infrastructure Architecture

yaml

# Kubernetes Deployment ArchitectureapiVersion: apps$v1kind: Deploymentmetadata:  name: auth-service  labels:    app: auth-servicespec:  replicas: 3  selector:    matchLabels:      app: auth-service  template:    metadata:      labels:        app: auth-service    spec:      containers:      - name: auth-service        image: auth-service:latest        ports:        - containerPort: 3000        env:        - name: NODE_ENV          value: "production"        - name: DATABASE_URL          valueFrom:            secretKeyRef:              name: db-secret              key: url        resources:          requests:            memory: "256Mi"            cpu: "250m"          limits:            memory: "512Mi"            cpu: "500m"        livenessProbe:          httpGet:            path: $health            port: 3000          initialDelaySeconds: 30          periodSeconds: 10        readinessProbe:          httpGet:            path: $ready            port: 3000          initialDelaySeconds: 5          periodSeconds: 5---apiVersion: v1kind: Servicemetadata:  name: auth-servicespec:  selector:    app: auth-service  ports:  - protocol: TCP    port: 80    targetPort: 3000  type: ClusterIP

# Kubernetes Deployment ArchitectureapiVersion: apps$v1kind: Deploymentmetadata:  name: auth-service  labels:    app: auth-servicespec:  replicas: 3  selector:    matchLabels:      app: auth-service  template:    metadata:      labels:        app: auth-service    spec:      containers:      - name: auth-service        image: auth-service:latest        ports:        - containerPort: 3000        env:        - name: NODE_ENV          value: "production"        - name: DATABASE_URL          valueFrom:            secretKeyRef:              name: db-secret              key: url        resources:          requests:            memory: "256Mi"            cpu: "250m"          limits:            memory: "512Mi"            cpu: "500m"        livenessProbe:          httpGet:            path: $health            port: 3000          initialDelaySeconds: 30          periodSeconds: 10        readinessProbe:          httpGet:            path: $ready            port: 3000          initialDelaySeconds: 5          periodSeconds: 5---apiVersion: v1kind: Servicemetadata:  name: auth-servicespec:  selector:    app: auth-service  ports:  - protocol: TCP    port: 80    targetPort: 3000  type: ClusterIP

6. Security Architecture

yaml

security_architecture:  authentication:    methods:      - jwt_tokens:          algorithm: RS256          expiry: 15m          refresh_expiry: 7d            - oauth2:          providers: [google, github]          scopes: [email, profile]            - mfa:          methods: [totp, sms]          required_for: [admin_roles]    authorization:    model: RBAC    implementation:      - role_hierarchy: true      - resource_permissions: true      - attribute_based: false        example_roles:      admin:        permissions: ["*"]            user:        permissions:          - "users:read:self"          - "users:update:self"          - "posts:create"          - "posts:read"    encryption:    at_rest:      - database: "AES-256"      - file_storage: "AES-256"        in_transit:      - api: "TLS 1.3"      - internal: "mTLS"    compliance:    - GDPR:        data_retention: "2 years"        right_to_forget: true        data_portability: true        - SOC2:        audit_logging: true        access_controls: true        encryption: true

security_architecture:  authentication:    methods:      - jwt_tokens:          algorithm: RS256          expiry: 15m          refresh_expiry: 7d            - oauth2:          providers: [google, github]          scopes: [email, profile]            - mfa:          methods: [totp, sms]          required_for: [admin_roles]    authorization:    model: RBAC    implementation:      - role_hierarchy: true      - resource_permissions: true      - attribute_based: false        example_roles:      admin:        permissions: ["*"]            user:        permissions:          - "users:read:self"          - "users:update:self"          - "posts:create"          - "posts:read"    encryption:    at_rest:      - database: "AES-256"      - file_storage: "AES-256"        in_transit:      - api: "TLS 1.3"      - internal: "mTLS"    compliance:    - GDPR:        data_retention: "2 years"        right_to_forget: true        data_portability: true        - SOC2:        audit_logging: true        access_controls: true        encryption: true

7. Scalability Design

yaml

scalability_patterns:  horizontal_scaling:    services:      - auth_service: "2-10 instances"      - user_service: "2-20 instances"      - notification_service: "1-5 instances"        triggers:      - cpu_utilization: "> 70%"      - memory_utilization: "> 80%"      - request_rate: "> 1000 req$sec"      - response_time: "> 200ms p95"    caching_strategy:    layers:      - cdn: "CloudFlare"      - api_gateway: "30s TTL"      - application: "Redis"      - database: "Query cache"        cache_keys:      - "user:{id}": "5 min TTL"      - "permissions:{userId}": "15 min TTL"      - "session:{token}": "Until expiry"    database_scaling:    read_replicas: 3    connection_pooling:      min: 10      max: 100        sharding:      strategy: "hash(user_id)"      shards: 4

scalability_patterns:  horizontal_scaling:    services:      - auth_service: "2-10 instances"      - user_service: "2-20 instances"      - notification_service: "1-5 instances"        triggers:      - cpu_utilization: "> 70%"      - memory_utilization: "> 80%"      - request_rate: "> 1000 req$sec"      - response_time: "> 200ms p95"    caching_strategy:    layers:      - cdn: "CloudFlare"      - api_gateway: "30s TTL"      - application: "Redis"      - database: "Query cache"        cache_keys:      - "user:{id}": "5 min TTL"      - "permissions:{userId}": "15 min TTL"      - "session:{token}": "Until expiry"    database_scaling:    read_replicas: 3    connection_pooling:      min: 10      max: 100        sharding:      strategy: "hash(user_id)"      shards: 4

Architecture Deliverables

System Design Document: Complete architecture specification
Component Diagrams: Visual representation of system components
Sequence Diagrams: Key interaction flows
Deployment Diagrams: Infrastructure and deployment architecture
Technology Decisions: Rationale for technology choices
Scalability Plan: Growth and scaling strategies

Best Practices

Design for Failure: Assume components will fail
Loose Coupling: Minimize dependencies between components
High Cohesion: Keep related functionality together
Security First: Build security into the architecture
Observable Systems: Design for monitoring and debugging
Documentation: Keep architecture docs up-to-date

Remember: Good architecture enables change. Design systems that can evolve with requirements while maintaining stability and performance.

来源与署名

来源：ruvnet/ruflo位于.agents/skills/agent-architecture提交6051f67

许可证：无许可证

内容归原作者所有。SourceWeft 从公开仓库中收录这些内容。

举报或申请下架

Agent Architecture

Retrieve pseudocode designs

SPARC Architecture Agent

SPARC Architecture Phase

System Architecture Design

1. High-Level Architecture

2. Component Architecture

3. Data Architecture

4. API Architecture

5. Infrastructure Architecture

6. Security Architecture

7. Scalability Design

Architecture Deliverables

Best Practices

来源与署名

更多来自 ruvnet/ruflo 的技能

Cron Schedule

Autopilot Predict

Autopilot Loop

Worker Integration

Worker Benchmarks

Swarm Advanced

更多Software Development技能

Playground

M5 Onboard

Cardputer Buddy

Web Design Guidelines

Vercel React Native Skills

Vercel React Best Practices