---
description: "Project context for TaskFlow — always applied"
alwaysApply: true
---

# Project Context — TaskFlow

## Project identity
- **Name:** TaskFlow
- **Package:** com.test.taskflow
- **Description:** Task management app
- **Scale:** small

## Technology stack
- **State management:** Riverpod
- **Architecture:** Feature-First
- **Routing:** GoRouter
- **Backend:** Supabase
- **Auth:** Supabase Auth
- **Platforms:** ios, android, web
- **Code generation:** freezed, json_serializable

## Feature modules
auth, tasks, profile

## Special capabilities


## Environments / flavors
- Flavors: dev, prod
- CI/CD: GitHub Actions

## Design & API references
- Design source: none
- API docs: none at ``

## Code references
### Git repositories
_No Git repository URLs listed._ Add entries under `references.repos` in project-brief.yaml when other repos are part of the product context.

### Local paths
_No local paths listed._ Add monorepo packages or sibling folders under `references.local_paths` in project-brief.yaml when relevant.

## Product UX / themes & roles
- **Theme variants:** light, dark
- **Roles:** Not enabled (`app_context.roles_enabled: false`).


## Reviews — which rule owns what
- **Theme, colors, typography, spacing/radius tokens** → `ui-ux-standards.mdc` (widgets read `Theme.of(context)` only)
- **User-visible copy & locales** → `localization.mdc` (ARB / `AppLocalizations`; no UI string literals)
- **Imports, structure, naming** → `flutter-core.mdc` + architecture rule

## Architecture boundaries
- features/auth/ MUST NOT import from features/home/ etc.
- Shared code lives in core/ or shared/ only
- Each feature is self-contained: screen + provider + model + repo

## When generating code for this project
1. Always use Riverpod patterns — never suggest alternatives
2. Always follow Feature-First folder structure
3. Always use GoRouter for navigation — never `Navigator.push` directly
4. Always target platforms: ios, android, web
5. If code generation tools are used (freezed, json_serializable), follow their conventions
6. Apply visuals only through theme (`ColorScheme`, `TextTheme`, `ThemeExtension`) — never ad-hoc colors/fonts in feature widgets
7. No user-facing string literals in widgets — l10n or shared constants per localization rule
