Cursor rule

1---
2description: "MANDATORY pattern discovery protocol before implementing anything. Search patterns_library/, specs/, and codebase first."
3alwaysApply: true
4---
5 
6# Pattern Discovery Protocol (MANDATORY)
7 
8**Before writing ANY code**, you MUST complete pattern discovery. This is not optional.
9 
10## Step 0: Search Specs Directory (FIRST)
11 
12```bash
13# Find similar implementations in specs
14ls specs/*-spec.md
15 
16# Review SAFe user stories for related work
17grep -r "As a.*I want to" specs/
18 
19# Check patterns referenced by past specs
20cat specs/{{TICKET_PREFIX}}-XXX-similar-spec.md
21```
22 
23## Step 1: Search Pattern Library
24 
25Check `patterns_library/` for an existing pattern that fits your use case.
26 
27**Available categories:**
28 
29| Category   | Path                        | Contents                            |
30|------------|-----------------------------|-------------------------------------|
31| API        | `patterns_library/api/`     | User context, admin, webhooks, Zod  |
32| UI         | `patterns_library/ui/`      | Authenticated pages, forms, tables  |
33| Database   | `patterns_library/database/`| RLS migration, Prisma transactions  |
34| Testing    | `patterns_library/testing/` | API integration, E2E user flows     |
35| Security   | `patterns_library/security/`| Input sanitization, rate limiting   |
36| CI         | `patterns_library/ci/`      | GitHub Actions, deployment pipeline |
37| Config     | `patterns_library/config/`  | Environment config, logging         |
38 
39See `patterns_library/README.md` for the full index of 18+ patterns.
40 
41## Step 2: Search Codebase
42 
43```bash
44# Search for similar functionality
45grep -r "feature_name" app/ lib/ components/
46 
47# Find existing helpers
48ls lib/
49grep -r "helper_pattern" lib/
50 
51# Check for existing components
52grep -r "ComponentName" components/
53```
54 
55## Step 3: Consult Documentation
56 
57Required reading before implementation:
58 
59- `CONTRIBUTING.md` -- Workflow and git process
60- `docs/database/DATA_DICTIONARY.md` -- Database schema (SINGLE SOURCE OF TRUTH)
61- `docs/database/RLS_IMPLEMENTATION_GUIDE.md` -- Row Level Security (MANDATORY for DB ops)
62- `docs/security/SECURITY_FIRST_ARCHITECTURE.md` -- Security patterns
63 
64## Step 4: Architectural Validation
65 
66- Propose your chosen pattern to the System Architect before implementation
67- Get approval before writing code
68- Document the decision in session notes
69 
70## What to Do When No Pattern Exists
71 
721. Do NOT create a new pattern yourself (that is BSA/Architect's job)
732. Report the gap to BSA with: what you need, what you searched, why existing patterns do not fit
743. Wait for BSA to create and Architect to validate the new pattern
754. Then proceed with implementation
76 
77## Pattern Usage Workflow
78 
79Once you have found the right pattern:
80 
811. **Copy** the pattern code from its `.md` file (patterns are copy-paste ready)
822. **Customize** using the pattern's Customization Guide (replace `{placeholders}`)
833. **Validate** using the pattern's validation commands
844. **Commit** with SAFe format referencing the ticket
85