60 lines
1.1 KiB
Plaintext
60 lines
1.1 KiB
Plaintext
|
---
|
||
|
|
@agent {
|
||
|
|
role: software architect,
|
||
|
|
llm: claude-opus-4-5-20251101,
|
||
|
|
max_tokens: 4000,
|
||
|
|
temperature: 0.5
|
||
|
|
}
|
||
|
|
|
||
|
|
@input feature: String
|
||
|
|
@input tech_stack?: String
|
||
|
|
|
||
|
|
@validate output {
|
||
|
|
must_contain: ["## Architecture", "## Components", "## Data Flow"],
|
||
|
|
format: markdown,
|
||
|
|
min_length: 500
|
||
|
|
}
|
||
|
|
---
|
||
|
|
|
||
|
|
# Architecture Design Request
|
||
|
|
|
||
|
|
**Feature**: {{ feature }}
|
||
|
|
|
||
|
|
{% if tech_stack %}
|
||
|
|
**Tech Stack**: {{ tech_stack }}
|
||
|
|
{% else %}
|
||
|
|
**Tech Stack**: Choose appropriate technologies based on requirements
|
||
|
|
{% endif %}
|
||
|
|
|
||
|
|
As a senior software architect, design a robust, scalable architecture for this feature.
|
||
|
|
|
||
|
|
Provide:
|
||
|
|
|
||
|
|
## Architecture
|
||
|
|
- High-level system design
|
||
|
|
- Architectural patterns used
|
||
|
|
- Why this approach
|
||
|
|
|
||
|
|
## Components
|
||
|
|
- Key components/modules
|
||
|
|
- Responsibilities of each
|
||
|
|
- Communication patterns
|
||
|
|
|
||
|
|
## Data Flow
|
||
|
|
- How data moves through the system
|
||
|
|
- State management approach
|
||
|
|
- API contracts (if applicable)
|
||
|
|
|
||
|
|
## Technical Considerations
|
||
|
|
- Scalability approach
|
||
|
|
- Performance considerations
|
||
|
|
- Security measures
|
||
|
|
- Trade-offs made
|
||
|
|
|
||
|
|
## Implementation Strategy
|
||
|
|
- Suggested implementation order
|
||
|
|
- Critical path items
|
||
|
|
- Risk mitigation
|
||
|
|
|
||
|
|
Keep it practical and implementation-ready.
|