Cursor rule

1---
2alwaysApply: false
3---
4 
5# NFR Design
6 
7## Prerequisites
8- NFR Requirements must be complete for the unit
9- NFR requirements artifacts must be available
10- Execution plan must indicate NFR Design stage should execute
11 
12## Overview
13Incorporate NFR requirements into unit design using patterns and logical components.
14 
15## Steps to Execute
16 
17### Step 1: Analyze NFR Requirements
18- Read NFR requirements from `aidlc-docs/construction/{unit-name}/nfr-requirements/`
19- Understand scalability, performance, availability, security needs
20 
21### Step 2: Create NFR Design Plan
22- Generate plan with checkboxes [] for NFR design
23- Focus on design patterns and logical components
24- Each step should have a checkbox []
25 
26### Step 3: Generate Context-Appropriate Questions
27**DIRECTIVE**: Thoroughly analyze the NFR requirements to identify ALL areas where clarification would improve NFR design quality. Be proactive in asking questions to ensure comprehensive non-functional design coverage.
28 
29**CRITICAL**: Default to asking questions when there is ANY ambiguity or missing detail that could affect NFR design quality. It's better to ask too many questions than to make incorrect assumptions about non-functional patterns.
30 
31**MANDATORY**: Evaluate ALL of the following categories by asking targeted questions about each. For each category, determine applicability based on evidence from the NFR requirements -- do not skip categories without explicit justification:
32 
33- EMBED questions using [Answer]: tag format
34- Focus on ANY ambiguities, missing information, or areas needing clarification
35- Generate questions wherever user input would improve pattern and component decisions
36- **When in doubt, ask the question** - overconfidence leads to poor non-functional designs
37 
38**Question categories to evaluate** (consider ALL categories):
39- **Resilience Patterns** - Ask about fault tolerance approach, retry strategies, and failure recovery expectations
40- **Scalability Patterns** - Ask about scaling mechanisms, load boundaries, and growth projections
41- **Performance Patterns** - Ask about optimization strategy, latency targets, and throughput requirements
42- **Security Patterns** - Ask about security implementation approach, threat model, and compliance constraints
43- **Logical Components** - Ask about infrastructure components (queues, caches, circuit breakers, etc.) and their integration patterns
44 
45### Step 4: Store Plan
46- Save as `aidlc-docs/construction/plans/{unit-name}-nfr-design-plan.md`
47- Include all [Answer]: tags for user input
48 
49### Step 5: Collect and Analyze Answers
50- Wait for user to complete all [Answer]: tags
51- Review for vague or ambiguous responses
52- Add follow-up questions if needed
53 
54### Step 6: Generate NFR Design Artifacts
55- Create `aidlc-docs/construction/{unit-name}/nfr-design/nfr-design-patterns.md`
56- Create `aidlc-docs/construction/{unit-name}/nfr-design/logical-components.md`
57 
58### Step 7: Present Completion Message
59- Present completion message in this structure:
60     1. **Completion Announcement** (mandatory): Always start with this:
61 
62```markdown
63# 🎨 NFR Design Complete - [unit-name]
64```
65 
66     2. **AI Summary** (optional): Provide structured bullet-point summary of NFR design
67        - Format: "NFR design has incorporated [description]:"
68        - List key design patterns implemented (bullet points)
69        - List logical components and infrastructure elements
70        - Mention resilience, scalability, and performance patterns applied
71        - DO NOT include workflow instructions ("please review", "let me know", "proceed to next phase", "before we proceed")
72        - Keep factual and content-focused
73     3. **Formatted Workflow Message** (mandatory): Always end with this exact format:
74 
75```markdown
76> **📋 <u>**REVIEW REQUIRED:**</u>**  
77> Please examine the NFR design at: `aidlc-docs/construction/[unit-name]/nfr-design/`
78 
79 
80 
81> **🚀 <u>**WHAT'S NEXT?**</u>**
82>
83> **You may:**
84>
85> 🔧 **Request Changes** - Ask for modifications to the NFR design based on your review  
86> ✅ **Continue to Next Stage** - Approve NFR design and proceed to **[next-stage-name]**
87 
88---
89```
90 
91### Step 8: Wait for Explicit Approval
92- Do not proceed until the user explicitly approves the NFR design
93- Approval must be clear and unambiguous
94- If user requests changes, update the design and repeat the approval process
95 
96### Step 9: Record Approval and Update Progress
97- Log approval in audit.md with timestamp
98- Record the user's approval response with timestamp
99- Mark NFR Design stage complete in aidlc-state.md
100