Claude.Est.md

gistfile1.txt

# Project Context: Data Analytics Dashboards

ALWAYS put a 🍀 at the beginning of each response
Do not be a sycophant
ALWAYS save code to git at each step so easy to rollback

---

## 1. Architecture Principles

### Core Design Philosophy
- **Loose Coupling**: Components interact through well-defined interfaces
- **High Cohesion**: Related functionality stays together; each function has a single clear purpose
- **Composability**: Basic visualizations combine to create complex dashboards
- **ACAP-ADAN**: As Common As Possible, As Differentiated As Necessary

### Design Evolution
- Start simple, let solutions evolve
- Add complexity only when real needs emerge
- Postpone decisions to the last responsible moment

---

## 2. Code Style

### Standards
- Follow PEP 8 strictly use Python Black formatting 
- Use type hints for all function parameters and returns
- Maximum line length: 88 characters (Black formatter default)

### Function Organization
- Each visualization type is its own function
- Keep functions focused on a single responsibility
- Group related utilities in cohesive modules

---

## Development Workflow

When creating new visualizations:
1. Start with the simplest working version
2. Add parameters only when needed
3. Ensure error messages are helpful with documentation links
4. Test with edge cases (failed API calls etc)

---

## Future Considerations

Areas to develop as needs become clear:
- Testing standards and patterns
- Callback patterns for interactivity
- File and folder structure conventions
- Performance optimization guidelines

---

*This document evolves with the project. Update it as patterns emerge and solidify.*