chore: update README and CLI usage for cursor_gen, version bump to 1.0.1

- Changed CLI usage instructions from `dart run cursor_gen` to `cursor_gen` for global activation.
- Updated project-brief.yaml example and README to reflect new command usage.
- Added app_context section in project-brief.yaml for theme variants and RBAC roles.
- Fixed bundled template resolution for local and global installs to prevent 'Template not found' errors.
- Version bump to 1.0.1 with corresponding updates in CHANGELOG and pubspec.yaml.

flutter-cursor-templates/templates/rules/i18n/localization.mdc.tmpl

@@ -46,6 +46,7 @@ Text(context.l10n.welcomeMessage)  // ✅
 
 ## Rules
 - **NEVER** hardcode user-facing strings as string literals in widget files
+- **Technical keys** (route paths, storage/analytics keys, JSON fields): one shared module (e.g. `lib/core/constants/app_strings.dart`) — no duplicated literals across features
 - All new strings added to ALL locale ARB files simultaneously — broken translations break builds
 - Use ICU message format for plurals and gendered strings
 - Date/time formatting: use `intl` package `DateFormat` — never `date.toString()`

flutter-cursor-templates/templates/rules/universal/project-context.mdc.tmpl

@@ -34,6 +34,23 @@ alwaysApply: true
 - Design source: {{DESIGN_SOURCE}}
 - API docs: {{API_DOCS_FORMAT}} at `{{API_DOCS_PATH}}`
 
+## Code references
+### Git repositories
+{{GIT_REFS_BLOCK}}
+
+### Local paths
+{{LOCAL_PATHS_BLOCK}}
+
+## Product UX / themes & roles
+- **Theme variants:** {{THEME_SUMMARY}}
+- **Roles:** {{ROLES_SUMMARY}}
+
+{{HIGH_CONTRAST_NOTE}}
+## 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
 {{ARCH_IMPORT_RULES}}
 
@@ -43,3 +60,5 @@ alwaysApply: true
 3. Always use {{ROUTING}} for navigation — never `Navigator.push` directly
 4. Always target platforms: {{PLATFORMS_LIST}}
 5. If code generation tools are used ({{CODEGEN_LIST}}), 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

flutter-cursor-templates/templates/rules/universal/ui-ux-standards.mdc.tmpl

@@ -5,6 +5,12 @@ alwaysApply: true
 
 # UI / UX Standards — {{PROJECT_NAME}}
 
+## Theme & design tokens (single source of truth)
+- Define **one** light/dark `ThemeData` (and optional `ThemeExtension`s for brand spacing, radii, semantic colors). Feature code reads `Theme.of(context)` only.
+- **Colors:** `colorScheme` / extensions — never hex/`Color(...)` literals in widgets except inside the theme definition file(s).
+- **Typography:** `textTheme` / `primaryTextTheme` — never raw `TextStyle(fontSize:, fontFamily:)` in feature UI.
+- **Spacing & shapes:** `ThemeExtension` or documented constants consumed consistently — avoid one-off magic numbers for padding/radius.
+
 ## Loading states
 - Every async operation MUST show a loading skeleton (shimmer), NOT a spinner unless < 300ms
 - Use `shimmer` package with a shimmer that matches the final layout shape
@@ -39,3 +45,4 @@ alwaysApply: true
 - All interactive widgets must have a `Semantics` label or `tooltip`
 - Minimum contrast ratio: 4.5:1 (WCAG AA)
 - Test with TalkBack / VoiceOver before each release
+{{HIGH_CONTRAST_UX_LINE}}