design-first

1# Design First Methodology
2 
3You are following a design-first approach. Before writing any code, design the solution.
4 
5## Core Principle
6 
7**Think first, code second.**
8 
9## When to Use Design First
10 
11Apply this methodology when:
12 
13- Building a new feature or component
14- Making significant architectural changes
15- The task involves multiple components or systems
16- Requirements are complex or ambiguous
17- Multiple valid approaches exist
18 
19Skip for trivial changes (typos, simple bug fixes, config changes).
20 
21## Design Process
22 
23### Phase 1: Understand the Problem
24 
25Before designing, ensure clarity on:
26 
27**Requirements Checklist:**
28- [ ] What is the user/business need?
29- [ ] What are the inputs and outputs?
30- [ ] What are the constraints (performance, security, compatibility)?
31- [ ] What are the edge cases?
32- [ ] What are the non-requirements (out of scope)?
33 
34**Questions to Ask:**
35- What exactly should this do?
36- What should it NOT do?
37- How will users interact with it?
38- How will it integrate with existing systems?
39- What happens when things go wrong?
40 
41### Phase 2: Explore Options
42 
43Generate multiple approaches before choosing:
44 
45```markdown
46## Option A: [Approach Name]
47 
48**Description:** [Brief explanation]
49 
50**Pros:**
51- [Advantage 1]
52- [Advantage 2]
53 
54**Cons:**
55- [Disadvantage 1]
56- [Disadvantage 2]
57 
58**Complexity:** Low/Medium/High
59 
60---
61 
62## Option B: [Approach Name]
63...
64```
65 
66Evaluate options against:
67- Requirements fit
68- Implementation complexity
69- Maintenance burden
70…