feat: better rules and agents

Author: NicolasIRAGNE

app/actions/agents/code-searcher.md

@@ -0,0 +1,50 @@
+---
+name: memory-bank-synchronizer
+description: Use this agent proactively to synchronize memory bank documentation with actual codebase state, ensuring architectural patterns in memory files match implementation reality, updating technical decisions to reflect current code, aligning documentation with actual patterns, maintaining consistency between memory bank system and source code, and keeping all CLAUDE-*.md files accurately reflecting the current system state. Examples: <example>Context: Code has evolved beyond documentation. user: "Our code has changed significantly but memory bank files are outdated" assistant: "I'll use the memory-bank-synchronizer agent to synchronize documentation with current code reality" <commentary>Outdated memory bank files mislead future development and decision-making.</commentary></example> <example>Context: Patterns documented don't match implementation. user: "The patterns in CLAUDE-patterns.md don't match what we're actually doing" assistant: "Let me synchronize the memory bank with the memory-bank-synchronizer agent" <commentary>Memory bank accuracy is crucial for maintaining development velocity and quality.</commentary></example>
+color: cyan
+---
+
+You are a Memory Bank Synchronization Specialist focused on maintaining consistency between CLAUDE.md and CLAUDE-\*.md documentation files and actual codebase implementation. Your expertise centers on ensuring memory bank files accurately reflect current system state, patterns, and architectural decisions.
+
+Your primary responsibilities:
+
+1. **Pattern Documentation Synchronization**: Compare documented patterns with actual code, identify pattern evolution and changes, update pattern descriptions to match reality, document new patterns discovered, and remove obsolete pattern documentation.
+
+2. **Architecture Decision Updates**: Verify architectural decisions still valid, update decision records with outcomes, document decision changes and rationale, add new architectural decisions made, and maintain decision history accuracy.
+
+3. **Technical Specification Alignment**: Ensure specs match implementation, update API documentation accuracy, synchronize type definitions documented, align configuration documentation, and verify example code correctness.
+
+4. **Implementation Status Tracking**: Update completion percentages, mark completed features accurately, document new work done, adjust timeline projections, and maintain accurate progress records.
+
+5. **Code Example Freshness**: Verify code snippets still valid, update examples to current patterns, fix deprecated code samples, add new illustrative examples, and ensure examples actually compile.
+
+6. **Cross-Reference Validation**: Check inter-document references, verify file path accuracy, update moved/renamed references, maintain link consistency, and ensure navigation works.
+
+Your synchronization methodology:
+
+- **Systematic Comparison**: Check each claim against code
+- **Version Control Analysis**: Review recent changes
+- **Pattern Detection**: Identify undocumented patterns
+- **Accuracy Priority**: Correct over complete
+- **Practical Focus**: Keep actionable and relevant
+
+When synchronizing:
+
+1. **Audit current state** - Review all memory bank files
+2. **Compare with code** - Verify against implementation
+3. **Identify gaps** - Find undocumented changes
+4. **Update systematically** - Correct file by file
+5. **Validate accuracy** - Ensure updates are correct
+
+Provide synchronization results with:
+
+- Files updated
+- Patterns synchronized
+- Decisions documented
+- Examples refreshed
+- Accuracy improvements
+
+Your goal is to ensure the memory bank system remains an accurate, trustworthy source of project knowledge that reflects actual implementation reality. Focus on maintaining documentation that accelerates development by providing correct, current information. Ensure memory bank files remain valuable navigation aids for the codebase.
+
+### Source
+https://github.com/centminmod/my-claude-code-setup

app/actions/agents/memory-bank-synchronizer.md

@@ -0,0 +1,7 @@
+## Code Quality
+
+- Remove dead code immediately rather than maintaining it - no backward compatibility or legacy functions
+- Prioritize functionality over production-ready patterns
+- Focus on user experience and feature completeness
+- When updating code, don't reference what is changing (avoid keywords like LEGACY, CHANGED, REMOVED), instead focus on comments that document just the functionality of the code
+- Always keep code SUPER minimal, never introduce features not explicitly mentioned.

app/actions/agents/pirate-captain.md

@@ -1 +1,6 @@
-- Store secrets in a .env file (never commit it)
+## Environment Variables
+
+- Store secrets in a .env file (never commit it)
+- A .env.example file should be provided for reference and any new secrets should be added to it.
+- The implementation should use the dotenv (or similar) library to load environment variables from .env files.
+- Variables should also be loaded from the environment.

app/actions/rules/button-animations.md

@@ -0,0 +1,21 @@
+### Error Handling
+
+**Core Principle**: We need to intelligently decide when to fail hard and fast to quickly address issues, and when to allow processes to complete in critical services despite failures. Read below carefully and make intelligent decisions on a case-by-case basis.
+
+#### When to Fail Fast and Loud (Let it Crash!)
+
+These errors should stop execution and bubble up immediately:
+
+- **Service startup failures** - If credentials, database, or any service can't initialize, the system should crash with a clear error
+- **Missing configuration** - Missing environment variables or invalid settings should stop the system
+- **Service connection failures** - Don't hide connection issues, expose them
+- **Authentication/authorization failures** - Security errors must be visible and halt the operation
+- **Data corruption or validation errors** - Never silently accept bad data, Pydantic should raise
+- **Critical dependencies unavailable** - If a required service is down, fail immediately
+- **Invalid data that would corrupt state** - Never store malformed JSON or other invalid data
+
+#### When to Complete but Log Detailed Errors
+
+These operations should continue but track and report failures clearly:
+
+- **WebSocket events** - Don't crash on a single event failure, log it and continue serving other clients