---
description: "Stack summary and product context for LegacyApp"
globs: ["project-brief.yaml", ".cursor/**/*.md", ".cursor/**/*.mdc", "pubspec.yaml"]
alwaysApply: false
---

# Project Context — LegacyApp

## Project identity
- **Name:** LegacyApp
- **Package:** com.test.legacy
- **Description:** Legacy GetX app
- **Scale:** medium

## Technology stack
- **State management:** GetX
- **Architecture:** MVC
- **Routing:** GetX Navigation
- **Backend:** REST API
- **Auth:** JWT / REST Auth
- **Platforms:** ios, android
- **Code generation:** none

## Feature modules
auth, dashboard

## Special capabilities


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

## Design & API references
- Design source: none
- API docs: openapi at `docs/api.yaml`

## 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
- View (Widget) MUST NOT contain business logic
- Controller MUST NOT import Flutter widgets directly
- Model MUST be plain Dart, no framework dependencies

## When generating code for this project
1. Always use GetX patterns — never suggest alternatives
2. Always follow MVC folder structure
3. Always use GetX Navigation for navigation — never `Navigator.push` directly
4. Always target platforms: ios, android
5. If code generation tools are used (none), 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
