agent-flutter 0.1.1

package/templates/shared/rules/document-workflow-function.md

@@ -0,0 +1,98 @@
+---
+alwaysApply: false
+---
+# AI Documentation Workflow (Function)
+
+## **Goal**
+To automatically generate and maintain detailed functional documentation in `spec/function-workflow.md`. This documentation bridges the gap between the high-level UI flow (from `ui-workflow.md`) and the technical implementation, focusing on **API integrations, Data Transformations, and State Management logic**.
+
+## **Trigger**
+This workflow is triggered when:
+1.  The `spec/ui-workflow.md` has been updated (Prerequisite).
+2.  Backend integration (API) is implemented for a feature.
+3.  Complex business logic is added (e.g., data validation, caching, error handling).
+4.  The user requests: "Update function workflow for [feature]".
+
+## **Workflow Steps**
+
+### **Step 1: Analyze the Implementation**
+- **Input**: The feature folder (`lib/src/ui/<feature>`) and `spec/ui-workflow.md`.
+- **Action**: Deep dive into the following files:
+    - `bloc/*_bloc.dart`: Identify Events, States, and Side Effects.
+    - `repository/*_repository.dart`: Identify API endpoints, Request/Response models.
+    - `model/*`: Analyze data structures.
+    - `core/managers/*`: Check for global state usage (e.g., Auth, Permission).
+
+### **Step 2: Format the Documentation**
+- **Output File**: `spec/function-workflow.md`
+- **Format**: Append (or Update) a section for EACH feature using the following template:
+
+```markdown
+## [Feature Name] (e.g., Login)
+**Ref UI**: [Link to UI Spec Section]
+
+### **1. Data Model**
+**Request**: `LoginRequest`
+- `email` (String): Required, valid email format.
+- `password` (String): Required, min 6 chars.
+
+**Response**: `LoginResponse`
+- `token` (String): JWT Token.
+- `user` (UserDto): User profile info.
+
+### **2. State Management (BLoC)**
+**Events**:
+- `LoginEvent(email, password)`: Triggers the login process.
+- `LoginReset()`: Resets state to initial.
+
+**States**:
+- `LoginInitial`: Form inputs enabled.
+- `LoginLoading`: Inputs disabled, loading spinner active.
+- `LoginSuccess(user)`: Navigation trigger.
+- `LoginFailure(error)`: Error message display.
+
+### **3. Functional Logic**
+1.  **Validation**:
+    - Check `email` via Regex.
+    - Check `password.length >= 6`.
+    - *If invalid*: Emit `LoginFailure(ValidationError)`.
+
+2.  **API Call**:
+    - Call `AuthRepository.login(request)`.
+    - **Endpoint**: `POST /api/v1/auth/login`
+    - **Headers**: `Content-Type: application/json`
+
+3.  **Error Handling**:
+    - **401 Unauthorized**: "Incorrect credentials".
+    - **500 Server Error**: "System error, try again".
+    - **Network Error**: "Check connection".
+
+4.  **Post-Process**:
+    - Save `token` to `SecureStorage`.
+    - Update `UserManager.currentUser`.
+    - Emit `LoginSuccess`.
+
+### **4. Dependencies & Services**
+- `AuthRepository`: API communication.
+- `SecureStorage`: Token persistence.
+- `UserManager`: Global user state.
+
+### **5. Technical Debt / Optimization**
+- [ ] Add rate limiting on login attempts.
+- [ ] Cache last used email for convenience.
+```
+
+### **Step 3: Verification**
+- **Consistency Check**: Ensure the "Functional Logic" aligns with the "User Flow" in `spec/ui-workflow.md`.
+- **API Check**: Verify that the documented Endpoint and Request/Response models match the actual code in `Repository` and `Retrofit` clients.
+- **Edge Cases**: Ensure error handling (Network, Validation, Server) is documented.
+
+---
+
+## **Prompt for AI**
+
+### **Case 1: Single Feature**
+> "Analyze `lib/src/ui/<feature>` and update `spec/function-workflow.md` based on the UI spec."
+
+### **Case 2: Sync with UI Spec**
+> "Read `spec/ui-workflow.md` and generate the corresponding functional specs in `spec/function-workflow.md`."

package/templates/shared/rules/integration-api.md

@@ -0,0 +1,3 @@
+---
+alwaysApply: false
+---

package/templates/shared/rules/new-template-project.md

@@ -0,0 +1,148 @@
+---
+alwaysApply: false
+---
+# Template Project Creation Workflow
+
+This workflow describes the step-by-step process to generate a new Flutter project that matches the architecture and standards of the current codebase.
+
+## 1. Project Initialization (FVM)
+
+### 1.1 FVM Setup & Create Project
+Use FVM (Flutter Version Management) to ensure consistent Flutter versions.
+
+1.  **Install FVM** (if needed):
+    ```bash
+    dart pub global activate fvm
+    ```
+
+2.  **Initialize & Create Project**:
+    ```bash
+    mkdir project_name
+    cd project_name
+    
+    # Initialize FVM with specific version (e.g., 3.38.5)
+    fvm use 3.38.5 --force
+    
+    # Create project using FVM version
+    fvm flutter create . --org com.example
+    ```
+
+### 1.2 IDE Configuration (VS Code)
+Create/Update `.vscode/settings.json` to use the FVM version:
+```json
+{
+  "dart.flutterSdkPath": ".fvm/flutter_sdk",
+  "search.exclude": {
+    "**/.fvm": true
+  },
+  "files.watcherExclude": {
+    "**/.fvm": true
+  }
+}
+```
+
+### 1.3 Update `pubspec.yaml`
+Add the standard dependencies required for the project architecture.
+
+**Core Dependencies:**
+- `get`: ^4.6.x (Routing & DI)
+- `flutter_bloc`: ^8.x.x (State Management)
+- `equatable`: ^2.x.x
+- `dio`: ^5.x.x (Network)
+- `retrofit`: ^4.x.x (API Client)
+- `json_annotation`: ^4.x.x
+- `flutter_dotenv`: (Environment variables)
+- `flutter_svg`: (SVG support)
+- `intl`: (Formatting)
+
+**Dev Dependencies:**
+- `build_runner`: (Code generation)
+- `retrofit_generator`:
+- `json_serializable`:
+
+## 2. Directory Structure Scaffolding
+
+Remove the default `lib/main.dart` and create the following directory structure under `lib/src/`:
+
+```
+lib/
+  main.dart
+  src/
+    api/              # Retrofit API clients & interceptors
+    core/
+      managers/       # System managers (Permission, Connectivity)
+      model/          # Data models (Request/Response)
+      repository/     # Data repositories
+    di/               # Dependency Injection setup
+    enums/            # App-wide enums
+    extensions/       # Dart extensions (Theme, Color, String)
+    helper/           # Utils helpers (Validation, Logger)
+    locale/           # Localization (TranslationManager)
+    ui/               # Feature modules
+      base/           # Base classes (BasePage, BaseViewModel)
+      main/           # Root/Shell Page (BottomNav)
+      home/           # Home Feature
+      widgets/        # Shared UI components (AppInput, AppButton)
+      routing/        # Per-tab Routers
+    utils/            # Constants, Colors, Styles, Assets
+```
+
+## 3. Core Module Setup
+
+### 3.1 Dependency Injection (`lib/src/di/`)
+Create `di_graph_setup.dart` to initialize core services before the app starts.
+- **Components**:
+    - `EnvironmentModule`: Load `.env` config.
+    - `NetworkModule`: Setup Dio client.
+    - `RepositoryModule`: Register Repositories.
+    - `ManagerModule`: Register Global Managers.
+
+### 3.2 Utilities (`lib/src/utils/`)
+Create placeholder files for design system constants:
+- `app_colors.dart`: Define `AppColors` class.
+- `app_styles.dart`: Define `AppStyles` class.
+- `app_assets.dart`: Define `AppAssets` class.
+- `app_pages.dart`: Define `AppPages` (GetX Route definition).
+
+### 3.3 Localization (`lib/src/locale/`)
+Implement `TranslationManager` extending `Translations` from GetX.
+
+## 4. App Entry Point (`main.dart`)
+
+Configure `main.dart` to:
+1. Load Environment variables (`dotenv`).
+2. Initialize Dependencies (`setupDependenciesGraph()`).
+3. Run `GetMaterialApp` with:
+   - `initialRoute`: `AppPages.main`
+   - `getPages`: `AppPages.pages`
+   - `theme`: Custom Theme.
+
+## 5. Main Shell Implementation (Bottom Navigation)
+
+Follow the guide in `create-bottombar.md` to implement the root navigation shell.
+
+1.  **Enums**: Create `BottomNavigationPage` enum in `lib/src/enums/`.
+2.  **Bloc**: Create `MainBloc` in `lib/src/ui/main/bloc/` to manage tab state.
+3.  **UI**: Create `MainPage` using `IndexedStack` and `CupertinoTabView` for nested navigation.
+4.  **Widget**: Create `AppBottomNavigationBar`.
+
+## 6. Base Feature Creation (Home)
+
+Create a standard "Home" feature to verify the setup:
+1.  **Folder**: `lib/src/ui/home/`.
+2.  **Files**:
+    - `home_page.dart`: The UI.
+    - `bloc/home_bloc.dart`: The Logic.
+    - `binding/home_binding.dart`: DI for the module.
+3.  **Routing**:
+    - Add `HomeRouter` in `lib/src/ui/routing/`.
+    - Register in `AppPages`.
+
+## 7. Environment Setup
+
+Create root-level environment files:
+- `.env`
+- `.env.staging`
+- `.env.prod`
+
+Add `.env*` to `.gitignore`.

package/templates/shared/rules/ui.md

@@ -0,0 +1,268 @@
+---
+alwaysApply: false
+---
+# UI Development Rules & Workflow
+
+## **1. Core Principles (Priority P1)**
+
+### **0. Design Tokens (STRICT)**
+- **Typography**: 1–1 mapping from Figma. Use `AppStyles`; `height = lineHeight / fontSize`. Bundle the exact font family/weight as in Figma.
+- **Colors**: Use `AppColors`. Do not use hex/raw colors (`Color(0xFF...)`, `Colors.red`).
+- **Spacing**: Use `int_extensions` and `AppDimensions`. Do not use arbitrary numeric padding/margin outside tokens.
+- **Numeric Tokens**: Preserve numeric values from Figma for all properties (radius, spacing, border width, shadow blur/spread, font size, line-height, letter-spacing…). Do not round or force presets. If defaults differ, override locally or update tokens per design.
+- **Icon Size**: Icon 24×24; container 44×44 when required by Figma; use `AppAssets`.
+- **Shadows**: Normalize `BoxShadow` closest to CSS box-shadow; do not change blur/spread arbitrarily.
+- **Backgrounds**: Use `DecorationImage` + appropriate `BoxFit` (cover/contain) and correct alignment.
+
+### **Overrides (Per-Component)**
+- App* widgets must allow overriding tokens: `size`, `radius`, `padding/margin`, `backgroundColor`, `textStyle`, `iconSize`, `constraints`.
+- Defaults must come from tokens (`AppStyles`, `AppColors`, `AppDimensions`) and act only as fallbacks; do not hardcode.
+- When overriding numeric tokens, preserve Figma values (radius/spacing/border/shadow/typography); do not round or force presets.
+
+### **Icon Consistency & Deduplication**
+- **Single Source**: Each icon has one SVG file and one constant in `AppAssets`.
+- **No Duplicates**: Do not add different filenames with identical graphics.
+- **Workflow**:
+  - Normalize SVG (remove metadata, sort attributes, flatten stroke→fill, remove masks/filters if unnecessary).
+  - Compute content hash after normalization; if duplicates → consolidate to one file and update references.
+  - Variants (color/size/solid/outline) must be clearly named and considered different when geometry/semantics differ.
+- **CI/Pre-commit**: Recommended duplicate check for `assets/images/icons/`; fail on duplicates.
+
+### **Temporary Policy (Icons)**
+- Current phase: **each screen adds its own icons**, do not reuse icons across screens. Name by screen to avoid confusion. Policy will be updated when moving to project-wide reuse.
+
+### **SVG Color Handling**
+- **Default**: Do not use `color`/`colorFilter` when the SVG already has correct Figma colors.
+- **Allowed**: Only apply `color`/`colorFilter` when design requires recolor (active/inactive…) and the icon is flattened stroke→fill.
+- **Prohibited**: Avoid `colorFilter` for multi-color SVGs; it easily causes color shifts on render.
+### **A. Widget Standardization (App* Prefix)**
+- **Rule**: ALWAYS check `lib/src/ui/widgets/` first.
+- **Convention**: Shared widgets MUST use the `App` prefix.
+- **Usage**:
+  - `AppInput` instead of `TextField`.
+  - `AppButtonBar` instead of `IconButton` (for back/actions).
+  - `AppButton` instead of `ElevatedButton`.
+  - `AppTextGradient` instead of `Text` (when gradient needed).
+  - `AppCardSection` for container groupings.
+
+### **B. Styling Source of Truth**
+- **Colors**: NEVER hardcode hex codes or `Colors.red`. Use `AppColors` from `lib/src/utils/app_colors.dart`.
+- **Typography**: Use `AppStyles` from `lib/src/utils/app_styles.dart`.
+- **Example**:
+  ```dart
+  // ✅ Correct
+  Text('Title', style: AppStyles.h1.copyWith(color: AppColors.primary));
+  
+  // ❌ Incorrect
+  Text('Title', style: TextStyle(fontSize: 20, color: Colors.blue));
+  ```
+
+### **C. Localization (Priority P1)**
+- **No Raw Strings**: All user-facing text MUST be localized.
+- **Implementation**:
+  - Add keys to `lib/src/locale/locale_key.dart` (snake_case: `feature_screen_element`).
+  - Update **ALL** translation files (`lib/src/locale/lang_en.dart`, `lib/src/locale/lang_ja.dart`). Optional modularization by feature:
+    - `lib/src/locale/en/<feature>.dart`
+    - `lib/src/locale/ja/<feature>.dart`
+    - Aggregators `lang_en.dart` / `lang_ja.dart` merge feature maps to reduce conflicts when multiple tasks add keys while keeping `enUs` / `jaJp`.
+  - **Usage**: Use `.tr` extension.
+ - **Integration**: `lib/src/locale/translation_manager.dart` consumes `enUs` and `jaJp`. **Do not rename** these variables in aggregators.
+ - **Common Keys**:
+   - Create common modules: `lib/src/core/localization/en/common.dart` and `ja/common.dart`.
+   - Use `common_*` keys for widespread phrases (Save/Cancel/OK/Back/Next/Loading/Error/Retry…).
+   - When text matches common, **reuse** the common key instead of creating a feature key.
+    ```dart
+    // ✅ Correct
+    Text(LocaleKey.home_title.tr);
+    
+    // ❌ Incorrect
+    Text('Home');
+    ```
+
+### **D. Data Model Layer (Priority P1)**
+- **Separation of Concerns**: Request and Response models MUST be separated.
+- **Folder Structure**:
+  - `lib/src/core/model/request/`: Models sent **TO** the API (e.g., `LoginRequest`).
+  - `lib/src/core/model/response/`: Models received **FROM** the API (e.g., `LoginResponse`).
+  - `lib/src/core/model/`: UI/domain models (e.g., `NotificationModel`, `CalendarEventModel`, `WorkDetailRecord`).
+- **Implementation**:
+  - Do NOT mix UI logic in models.
+  - Use `factory .fromJson` and `Map toJson` when applicable.
+  - **No dynamic data in UI**: Pages/components MUST receive typed models via constructor/BLoC state; do not hardcode demo lists in widgets.
+  - **Demo/Mock Data Location**: Keep all demo/sample data in `lib/src/utils/app_demo_data.dart` only. Import from there when previewing or testing UI.
+- **Reuse-first**: Before creating a new model, check the [Model Registry](../../spec/model-registry.md) and follow [Dart Model Reuse Skill](../skills/dart-model-reuse/SKILL.md). Prefer extending existing models (optional fields) or composition over duplication.
+
+### **E. Composition & State**
+- **State**: Default to `StatelessWidget`. Use `StatefulWidget` only for local UI logic (animations, focus).
+- **Encapsulation**: "Smart Components" should handle their own internal state (e.g., `AppInput` handles password visibility toggle).
+- **Layout**: Use `Flex` (Column/Row) + int extensions (`n.height`/`n.width`) for spacing. Avoid `Padding` for simple gaps.
+
+### **F. Assets Management (Priority P1)**
+- **Rule**: Follow the [Assets Management Skill](../skills/flutter-assets-management/SKILL.md) strictly.
+- **Naming**: MUST match Figma layer names in `snake_case`.
+- **Registry**: All assets MUST be defined in `lib/src/utils/app_assets.dart`.
+- **Usage**:
+  ```dart
+  // ✅ Correct
+  SvgPicture.asset(AppAssets.icons_home_active_svg);
+  
+  // ❌ Incorrect
+  SvgPicture.asset('assets/images/icons/home_active.svg');
+  ```
+- **Workflow**:
+  1. Rename layer in Figma to `snake_case`.
+  2. Export to `assets/images/` or `assets/icons/`.
+  3. Register path in `AppAssets`.
+  4. Use `AppAssets.name` in code.
+ - **SVG Hygiene (Priority P1)**:
+   - Flatten stroke → fill để tint/recolor an toàn.
+   - Remove mask/clip/filter phức tạp; đảm bảo `viewBox` 24×24 cho icon.
+   - Kiểm tra render qua `SvgPicture.asset` trong container 44×44, icon 24×24.
+
+---
+
+## **2. Standard Page Architecture**
+
+Every page must follow this folder structure under `lib/src/ui/`:
+
+```text
+lib/src/ui/<page_name>/
+├── binding/
+│   └── <page_name>_binding.dart  # Dependency Injection
+├── interactor/
+│   └── <page_name>_bloc.dart     # Logic & State (GetX Controller or Bloc)
+├── components/
+│   ├── <page_name>_header.dart   # Local UI parts
+│   └── <page_name>_form.dart
+└── <page_name>_page.dart         # Main Entry Point
+```
+
+---
+
+## **3. New Page Creation Workflow**
+
+Follow these steps when creating a new UI screen:
+
+### **Step 1: Preparation**
+- Check Figma/Design.
+- Identify reusable components -> Are they in `lib/src/ui/widgets`?
+- Identify unique components -> Plan to put them in `components/`.
+
+### **Step 2: Scaffolding**
+- Create the folder structure (See [Lib Src Architecture Skill](../skills/flutter-standard-lib-src-architecture/SKILL.md)):
+  ```bash
+  mkdir -p lib/src/ui/my_new_feature/{binding,interactor,components}
+  ```
+
+### **Step 3: Data Modeling (If API involved)**
+- Create Request model in `lib/src/core/model/request/`.
+- Create Response model in `lib/src/core/model/response/`.
+
+### **Step 4: Logic & Binding**
+- Create the Controller/Bloc in `interactor/` (See [Bloc Skill](../skills/flutter-bloc-state-management/SKILL.md)).
+- Create the Binding in `binding/` to inject the controller.
+
+### **Step 5: Localization**
+- **Identify Strings**: List all text in the new UI (See [GetX Localization Skill](../skills/getx-localization-standard/SKILL.md)).
+- **Update Keys**: Add entries to `locale_key.dart` (e.g., `my_feature_title`).
+- **Update Translations**: Add translations to `lang_en.dart`, `lang_ja.dart`.
+
+### **Step 6: Main Page Implementation**
+- Create `<page_name>_page.dart` (See [UI Widgets Skill](../skills/flutter-ui-widgets/SKILL.md)).
+- Use `AppScaffold` (if available) or standard `Scaffold`.
+- **Import Rules**:
+  - Use `AppColors` / `AppStyles`.
+  - Use `App*` widgets.
+  - Use `LocaleKey.my_key.tr` for text.
+- **Radius & Icon**:
+  - If Figma requires radius = 14, **must** use `BorderRadius.circular(14)` at the corresponding component.
+  - Icon 24×24; if framed, use container 40×40/44×44 per Figma.
+ - **Documentation Comments (STRICT)**:
+   - Add top-of-class `///` description for every Page and Component, summarizing its purpose and main actions.
+   - Generator reads these docs to build `spec/ui-workflow.md` (run `dart run tool/generate_ui_workflow_spec.dart`).
+   - Example:
+     ```dart
+     /// CustomerDetailPage: Shows overview, cases, and inspection history for a customer.
+     class CustomerDetailPage extends StatelessWidget { ... }
+     
+     /// CustomerDetailHeader: Displays customer status badges and next schedule.
+     class CustomerDetailHeader extends StatelessWidget { ... }
+     ```
+
+### **Step 7: Component Extraction**
+- **Rule**: If a widget block is > 50 lines or reused twice, extract it to `components/` (See [Idiomatic Flutter Skill](../skills/idiomatic-flutter/SKILL.md)).
+- Keep the main `build()` method clean and readable.
+
+### **Step 8: Route Registration (Choose One)**
+- See [Navigation Manager Skill](../skills/flutter-navigation-manager/SKILL.md).
+- **Scenario A: Full Screen Page (Hides Bottom Bar)**
+  - Register in `lib/src/utils/app_pages.dart`.
+  - Use `Get.toNamed(AppPages.myFeature)`.
+- **Scenario B: Nested Page (Keeps Bottom Bar Visible)**
+  - Register in `lib/src/ui/routing/<feature>_router.dart` (e.g., `home_router.dart`).
+  - Corresponds to the active tab (Home, Customer, etc.).
+- **Scenario C: Common Shared Page (Accessible from ANY Tab)**
+  - Register in `lib/src/ui/routing/common_router.dart`.
+  - Used for shared screens like Notification, Privacy Policy, etc. that keep the Bottom Bar visible.
+
+### **Step 9: Widget Preview (Priority P1)**
+- **Requirement**: Every page and complex component MUST have a `@Preview` annotation for quick iteration.
+- **Setup**:
+  1. Import `package:flutter/widget_previews.dart`.
+  2. Create a helper class `PreviewTranslations` to map localization keys.
+  3. Create a public top-level function annotated with `@Preview`.
+  4. Wrap the widget in `GetMaterialApp` to provide context, localization, and DI.
+- **Template**:
+  ```dart
+  import 'package:flutter/widget_previews.dart';
+  import 'package:link_home/src/locale/lang_en.dart';
+  import 'package:link_home/src/locale/lang_ja.dart';
+
+  // ... (Page Code) ...
+
+  class PreviewTranslations extends Translations {
+    @override
+    Map<String, Map<String, String>> get keys => {
+          'en_US': enUs,
+          'ja_JP': jaJp,
+        };
+  }
+
+  @Preview(
+    size: Size(390, 844), // iPhone 12 Standard
+  )
+  Widget previewPageName() {
+    // Inject Dependencies if needed
+    if (!Get.isRegistered<PageBloc>()) {
+      Get.put(PageBloc());
+    }
+    
+    return GetMaterialApp(
+      debugShowCheckedModeBanner: false,
+      useInheritedMediaQuery: true, // MUST be true for correct sizing
+      translations: PreviewTranslations(),
+      locale: const Locale('ja', 'JP'), // Default Preview Locale
+      fallbackLocale: const Locale('en', 'US'),
+      home: const PageName(),
+    );
+  }
+  ```
+
+---
+
+## **4. Checklist Before PR**
+- [ ] No hardcoded colors/styles?
+- [ ] No raw strings? (Localization used)
+- [ ] Used `App*` widgets where possible?
+- [ ] Page broken down into `components/`?
+- [ ] Logic separated into `interactor/`?
+- [ ] **Data Models Separated?** (Request/Response in `core/model/`)
+- [ ] File naming matches `<feature>_<type>.dart`?
+- [ ] **Route Registered?**
+  - [ ] If Full Screen: Added to `AppPages`?
+  - [ ] If Nested: Added to `ui/routing/<tab>_router.dart`?
+  - [ ] If Shared: Added to `ui/routing/common_router.dart`?
+- [ ] **Widget Preview Added?** (`@Preview` with correct `Size` and `GetMaterialApp` wrapper)
+ - [ ] **Design Tokens Applied?** (Typography/Colors/Spacing match Figma)
+ - [ ] **Radius preserved from Figma?** (e.g., r14 at relevant components)
+ - [ ] **SVG Hygiene OK?** (viewBox 24×24, tintable, no complex masks/filters)

package/templates/shared/rules/unit-test.md

@@ -0,0 +1,3 @@
+---
+alwaysApply: false
+---

package/templates/shared/rules/widget-test.md

@@ -0,0 +1,3 @@
+---
+alwaysApply: false
+---

package/templates/shared/skills/dart-best-practices/SKILL.md

@@ -0,0 +1,20 @@
+---
+name: Dart Best Practices
+description: General purity standards for Dart development.
+---
+
+# Dart Best Practices
+
+## **Priority: P1**
+
+- **Scoping**:
+  - No global variables.
+  - Private globals (if required) must start with `_`.
+- **Immutability**: Use `const` > `final` > `var`.
+- **Config**: Use `--dart-define` for secrets. Never hardcode API keys.
+- **Naming**: Follow [effective-dart](https://dart.dev/guides/language/effective-dart) (PascalCase classes, camelCase members).
+
+```dart
+import 'models/user.dart'; // Good
+import 'package:app/models/user.dart'; // Avoid local absolute
+```

package/templates/shared/skills/dart-language-patterns/SKILL.md

@@ -0,0 +1,47 @@
+---
+name: Dart Language Patterns
+description: Modern Dart standards (3.x+) including null safety and patterns.
+---
+
+# Dart Language Patterns
+
+## **Priority: P0 (CRITICAL)**
+
+Modern Dart standards for safety, performance, and readability.
+
+## Implementation Guidelines
+
+- **Null Safety**: Avoid `!`. Use `?.`, `??`, or short-circuiting. Use `late` only if necessary.
+- **Immutability**: Use `final` for all variables. Prefer plain immutable classes with `const` constructors; use `Equatable` only when value equality is needed.
+- **Pattern Matching (3.x)**: Use `switch (value)` with patterns and destructuring.
+- **Records**: Use Records (e.g., `(String, int)`) for returning multiple values.
+- **Sealed Classes**: Use `sealed class` for exhaustive state handling in domain logic.
+- **Extensions**: Use `extension` to add utility methods to third-party types.
+- **Wildcards (3.7+)**: Use `_` for unused variables in declarations and patterns.
+- **Tear-offs**: Prefer using tear-offs (e.g., `list.forEach(print)`) over anonymous lambdas (e.g., `list.forEach((e) => print(e))`).
+- **Asynchrony**: Prefer `async/await` over raw `Future.then`. Use `unawaited` for fire-and-forget logic if necessary.
+- **Collections**: Use `collection-if`, `collection-for`, and spread operators `...`.
+
+## Anti-Patterns
+
+- **No ! Operator**: Do not use the bang operator `!` unless you can prove the value is non-null via `if` or `assert`.
+- **No var for members**: Do not use `var` for class members; use `final` or explicit types.
+- **No logic in constructors**: Do not perform complex calculations or async work inside constructors.
+
+## Code
+
+```dart
+// Sealed class and Switch expression
+sealed class Result {}
+class Success extends Result { final String data; Success(this.data); }
+class Failure extends Result {}
+
+String message(Result r) => switch (r) {
+  Success(data: var d) => "Got $d",
+  Failure() => "Error",
+};
+```
+
+## Related Topics
+
+feature-based-clean-architecture | tooling

package/templates/shared/skills/dart-model-reuse/SKILL.md

@@ -0,0 +1,38 @@
+---
+name: "Dart Model Reuse & Evolution"
+description: "Guides model reuse/composition and safe extension. Invoke when adding/updating UI/domain models or preventing duplicate screen-specific models."
+---
+
+# Dart Model Reuse & Evolution
+
+## Goal
+Prevent duplicate models across features and keep UI data strongly typed. Reuse existing models where possible; evolve them safely when needed.
+
+## Where Models Live
+- Request: `lib/src/core/model/request/`
+- Response: `lib/src/core/model/response/`
+- UI/Domain: `lib/src/core/model/`
+- Demo/Mock Data: `lib/src/utils/app_demo_data.dart` (only)
+
+## Reuse-first Policy
+- Before adding a new model:
+  - Check the Model Registry: `spec/model-registry.md` for existing shared models and their purposes.
+  - Also check `lib/src/core/model/` for an existing model with overlapping fields.
+  - Prefer reuse if ≥70% fields overlap and semantics match.
+  - If needed, add optional fields to the existing model (keep backward compatibility).
+  - If semantics differ, compose: nest existing model rather than duplicating fields.
+
+## Evolution Rules
+- Additive changes only on active branches (append fields, keep constructors compatible).
+- Use optional fields (`Type?`) and sensible defaults to avoid breaking code.
+- Keep `fromJson`/`toJson` aligned when applicable.
+
+## Naming & Ownership
+- Names must reflect domain, not screens (`CustomerProjectInfo`, not `CustomerProjectListItem`).
+- Shared models are owned at `lib/src/core/model/`; screens cannot fork them.
+
+## Checklist (Mandatory)
+- Reuse considered?
+- Composition preferred over duplication?
+- Demo data added to `app_demo_data.dart`, not UI?
+- Request/Response models separated?

package/templates/shared/skills/dart-tooling-ci/SKILL.md

@@ -0,0 +1,38 @@
+---
+name: "Dart Tooling & CI"
+description: Standards for analysis, linting, formatting, and automation.
+---
+
+# Tooling & CI
+
+## **Priority: P1 (HIGH)**
+
+Standards for code quality, formatting, and generation.
+
+## Implementation Guidelines
+
+- **Linter**: Use `analysis_options.yaml`. Enforce `always_use_package_imports` and `require_trailing_commas`.
+- **Formatting**: Use `dart format . --line-length 80`. Run on every commit.
+- **DCM**: Use `dart_code_metrics` for complexity checks (Max cyclomatic complexity: 15).
+- **Build Runner**: Always use `--delete-conflicting-outputs` with code generation.
+- **CI Pipeline**: All PRs MUST pass `analyze`, `format`, and `test` steps.
+- **Imports**: Group imports: `dart:`, `package:`, then relative.
+- **Documentation**: Use `///` for public APIs. Link symbols using `[Class]`.
+
+## Code
+
+```yaml
+# analysis_options.yaml
+analyzer:
+  errors:
+    todo: ignore
+    missing_required_param: error
+linter:
+  rules:
+    - prefer_single_quotes
+    - unawaited_futures
+```
+
+## Related Topics
+
+language | testing