Cramer Frontend State and Data
Purpose
Keep frontend state and data flows consistent with the project’s Zustand and API client patterns.
Workflow
- •Read docs first:
- •
docs/library/frontend/STATE_MANAGEMENT.md - •
docs/library/frontend/API_CLIENT.md
- •
- •Review implementation:
- •
frontend/src/stores/ - •
frontend/src/api/ - •
frontend/src/hooks/andfrontend/src/contexts/(if used)
- •
- •Propose changes with a clear rationale.
- •Apply edits after approval.
- •Summarize changes and any follow-up tasks.
Guardrails
- •Prefer existing store and API client patterns over new abstractions.
- •Avoid UI changes unless they are necessary for data flow.