Add git workflow and branch naming guidelines

- Add comprehensive feature branch naming convention to systemPatterns.md
- Include initials extraction rules and 24-character limit
- Add workflow steps with git config user.name requirement
- Add reference to branch naming guidelines in CLAUDE.md
- Ensure all future AI sessions follow consistent branch naming

Co-authored-by: Ona <[email protected]>

Author: geropl

CLAUDE.md

@@ -27,6 +27,7 @@ The `memory-bank/components/` directory contains detailed documentation for each
 2. **Component-specific work** - Refer to the relevant component documentation in `memory-bank/components/`
 3. **Architecture decisions** - Check `memory-bank/systemPatterns.md` for established patterns and conventions
 4. **Current focus** - Review `memory-bank/activeContext.md` for ongoing work and priorities
+5. **Git workflow** - **CRITICAL**: Always use feature branches with proper naming convention (see `memory-bank/systemPatterns.md` for branch naming rules)
 
 ## Key Characteristics
 

memory-bank/systemPatterns.md

@@ -112,6 +112,27 @@ Gitpod follows a microservices architecture designed to be **Scalable**, **Resil
 
 ## Development Workflows
 
+### Git Branch Management
+
+#### Feature Branch Naming Convention
+**CRITICAL**: Always use feature branches from main for all work. Never work directly on main.
+
+**Naming Pattern**: `[initials]/[[issue-id]-][topic-shorthand]`
+
+**Rules**:
+- **Maximum 24 characters total**
+- **Initials**: Extract from `git config user.name` (first letter of each word)
+- **Issue ID**: Numeric part only (e.g., "1592" from "CLC-1592")
+- **Topic**: 2-3 words separated by dashes, describing the work
+- **IMPORTANT**: Always run `git config user.name` first - never assume initials
+
+**Workflow**:
+1. Run `git config user.name` to get actual name
+2. Extract initials from the output
+3. Create feature branch: `git checkout -b [initials]/[topic]`
+4. Push work to feature branch
+5. Create PR against main
+
 ### PRD Workflow
 1. **Requirements Gathering** (Plan): Understand problem, explore components
 2. **PRD Creation** (Plan): Create document with standardized sections