Cursor rule

1---
2alwaysApply: false
3---
4 
5# Infrastructure Design
6 
7## Prerequisites
8- Functional Design must be complete for the unit
9- NFR Design recommended (provides logical components to map)
10- Execution plan must indicate Infrastructure Design stage should execute
11 
12## Overview
13Map logical software components to actual infrastructure choices for deployment environments.
14 
15## Steps to Execute
16 
17### Step 1: Analyze Design Artifacts
18- Read functional design from `aidlc-docs/construction/{unit-name}/functional-design/`
19- Read NFR design from `aidlc-docs/construction/{unit-name}/nfr-design/` (if exists)
20- Identify logical components needing infrastructure
21 
22### Step 2: Create Infrastructure Design Plan
23- Generate plan with checkboxes [] for infrastructure design
24- Focus on mapping to actual services (AWS, Azure, GCP, on-premise)
25- Each step should have a checkbox []
26 
27### Step 3: Generate Context-Appropriate Questions
28**DIRECTIVE**: Thoroughly analyze the functional and NFR design to identify ALL areas where clarification would improve infrastructure decisions. Be proactive in asking questions to ensure comprehensive infrastructure coverage.
29 
30**CRITICAL**: Default to asking questions when there is ANY ambiguity or missing detail that could affect infrastructure quality. It's better to ask too many questions than to make incorrect infrastructure assumptions.
31 
32**MANDATORY**: Evaluate ALL of the following categories by asking targeted questions about each. For each category, determine applicability based on evidence from the functional and NFR design artifacts -- do not skip categories without explicit justification:
33 
34- EMBED questions using [Answer]: tag format
35- Focus on ANY ambiguities, missing information, or areas needing clarification
36- Generate questions wherever user input would improve infrastructure decisions
37- **When in doubt, ask the question** - overconfidence leads to poor infrastructure choices
38 
39**Question categories to evaluate** (consider ALL categories):
40- **Deployment Environment** - Ask about cloud provider preferences, environment setup, and deployment targets
41- **Compute Infrastructure** - Ask about compute service choices, sizing, and scaling requirements
42- **Storage Infrastructure** - Ask about database selection, storage patterns, and data lifecycle needs
43- **Messaging Infrastructure** - Ask about messaging/queuing services, event-driven patterns, and async processing
44- **Networking Infrastructure** - Ask about load balancing, API gateway approach, and network topology
45- **Monitoring Infrastructure** - Ask about observability tooling, alerting strategy, and logging requirements
46- **Shared Infrastructure** - Ask about infrastructure sharing strategy, multi-tenancy, and resource isolation
47 
48### Step 4: Store Plan
49- Save as `aidlc-docs/construction/plans/{unit-name}-infrastructure-design-plan.md`
50- Include all [Answer]: tags for user input
51 
52### Step 5: Collect and Analyze Answers
53- Wait for user to complete all [Answer]: tags
54- Review for vague or ambiguous responses
55- Add follow-up questions if needed
56 
57### Step 6: Generate Infrastructure Design Artifacts
58- Create `aidlc-docs/construction/{unit-name}/infrastructure-design/infrastructure-design.md`
59- Create `aidlc-docs/construction/{unit-name}/infrastructure-design/deployment-architecture.md`
60- If shared infrastructure: Create `aidlc-docs/construction/shared-infrastructure.md`
61 
62### Step 7: Present Completion Message
63- Present completion message in this structure:
64     1. **Completion Announcement** (mandatory): Always start with this:
65 
66```markdown
67# 🏢 Infrastructure Design Complete - [unit-name]
68```
69 
70     2. **AI Summary** (optional): Provide structured bullet-point summary of infrastructure design
71        - Format: "Infrastructure design has mapped [description]:"
72        - List key infrastructure services and components (bullet points)
73        - List deployment architecture decisions and rationale
74        - Mention cloud provider choices and service mappings
75        - DO NOT include workflow instructions ("please review", "let me know", "proceed to next phase", "before we proceed")
76        - Keep factual and content-focused
77     3. **Formatted Workflow Message** (mandatory): Always end with this exact format:
78 
79```markdown
80> **📋 <u>**REVIEW REQUIRED:**</u>**  
81> Please examine the infrastructure design at: `aidlc-docs/construction/[unit-name]/infrastructure-design/`
82 
83 
84 
85> **🚀 <u>**WHAT'S NEXT?**</u>**
86>
87> **You may:**
88>
89> 🔧 **Request Changes** - Ask for modifications to the infrastructure design based on your review  
90> ✅ **Continue to Next Stage** - Approve infrastructure design and proceed to **Code Generation**
91 
92---
93```
94 
95### Step 8: Wait for Explicit Approval
96- Do not proceed until the user explicitly approves the infrastructure design
97- Approval must be clear and unambiguous
98- If user requests changes, update the design and repeat the approval process
99 
100### Step 9: Record Approval and Update Progress
101- Log approval in audit.md with timestamp
102- Record the user's approval response with timestamp
103- Mark Infrastructure Design stage complete in aidlc-state.md
104