Cline rules

1# 📖 Cline Rules
2 
3This directory contains rules and guidelines for Cline to follow when working with this project, incorporating the SPARC methodology for structured development.
4 
5## Structure
6 
7- `rules/` - Contains general guidelines and rules for Cline
8- `rules-code/` - Contains code-specific guidelines and rules
9- `tests/` - Contains testing guidelines and rules
10 
11## SPARC Methodology
12 
13The SPARC methodology provides a structured workflow for development:
14 
151. **Specification** - Define goals, scope, constraints, and acceptance criteria
162. **Pseudocode** - Develop high-level logic with TDD anchors
173. **Architecture** - Design modular components with clear interfaces
184. **Refinement** - Implement with TDD, debugging, and optimization
195. **Completion** - Integrate, document, test, and verify against criteria
20 
21## Usage
22 
23Cline automatically processes all Markdown files inside the `.clinerules/` directory, combining them into a unified set of rules. The numeric prefixes (optional) help organize files in a logical sequence.
24 
25## Benefits of the Folder Approach
26 
27- **Contextual Activation**: Copy only relevant rules from the bank to the active folder
28- **Easier Maintenance**: Update individual rule files without affecting others
29- **Team Flexibility**: Different team members can activate rules specific to their current task
30- **Reduced Noise**: Keep the active ruleset focused and relevant
31 
32## Managing Rules with the Toggleable Popover
33 
34Located under the chat input field, the popover UI allows you to:
35 
36- Instantly See Active Rules: View which global rules and workspace rules are currently active
37- Quickly Toggle Rules: Enable or disable specific rule files within your workspace
38- Easily Add/Manage Rules: Create a workspace `.clinerules` file or folder if one doesn't exist
39 
40## Memory Bank
41 
42The Memory Bank files (prefixed with emojis) provide Cline with persistent memory between sessions:
43 
44- 📋 `_projectbrief.md` - Foundation document defining core requirements and goals
45- 🔍 `_productContext.md` - Why this project exists and how it should work
46- 🔄 `_activeContext.md` - Current work focus, recent changes, and next steps
47- 🏗️ `_systemPatterns.md` - System architecture and key technical decisions
48- ⚙️ `_techContext.md` - Technologies used and development setup
49- 📊 `_progress.md` - Project status, completed features, and known issues
50- 🧠 `_memory-bank.md` - Core documentation about the Memory Bank system itself
51