Skip to main content
Each agent worker is a specialized Cloudflare Worker that generates artifacts for a specific phase of software architecture.

Agent Structure

All agents follow a consistent structure:

Agent Interface

All agents implement the same interface:

System Prompts

Each agent has a specialized system prompt defining:
  • Role: Agent’s expertise (e.g., “Senior Product Manager”)
  • Goal: Primary objective
  • Instructions: Step-by-step process
  • Output Structure: Required format
  • Constraints: Rules and limitations

PRD Agent Prompt

Focuses on:
  • Executive summary
  • User personas
  • Functional requirements
  • MoSCoW roadmap

Data Agent Prompt

Focuses on:
  • Entity identification
  • Relationship modeling
  • Database schema design
  • Migration strategies

Design Agent Prompt

Focuses on:
  • Design tokens
  • Component library
  • UI/UX patterns
  • Accessibility

Logic Agent Prompt

Focuses on:
  • Business rules
  • State machines
  • Validation logic
  • Triggers HITL interrupt

API Agent Prompt

Focuses on:
  • RESTful API design
  • Resource modeling
  • Request/response schemas
  • OpenAPI specification

Frontend Agent Prompt

Focuses on:
  • Component architecture
  • State management
  • Routing structure
  • Performance optimization

Deployment Agent Prompt

Focuses on:
  • Infrastructure as Code
  • CI/CD pipelines
  • Monitoring and observability
  • Security configuration

Request Format

Agents receive requests with:

Response Format

Agents return responses in:

LLM Integration

Agents use Gemini API for LLM calls:

Error Handling

Agents include error handling:

Service Bindings

Agents are called via Cloudflare service bindings: