@shaykec/app-agent 1.0.8 → 1.0.9

package/.claude/agents/android-customizer.md

@@ -48,10 +48,18 @@ POTENTIAL ISSUES:
 - {concerns needing manual review}
 ```
 
+### Data Layer
+- Use `DataSourceResolver.repository`, not `MockDataProvider` directly
+- Preserve MockDataProvider CRUD functions and `reset()` method
+- Do NOT modify NetworkMonitor, LocalPersistence, or OfflineBanner
+
 ## Rules
 - ONLY edit files under `output/`
 - Ensure all package declarations match directory structure
 - Keep Hilt annotations intact (@HiltAndroidApp, @HiltViewModel, @AndroidEntryPoint)
 - Keep build.gradle.kts syntactically valid
-- Preserve MockDataProvider function signatures
+- Preserve MockDataProvider CRUD functions and `reset()` method
+- Do NOT modify NetworkMonitor, LocalPersistence, or OfflineBanner
 - Use Material 3 components (not legacy Material 2)
+- Preserve ALL `Modifier.testTag()` calls — do NOT remove test IDs
+- Follow `{screen}_{element}_{role}` convention for new test tags (see `templates/TEST_ID_CONVENTIONS.md`)

package/.claude/agents/ios-customizer.md

@@ -46,9 +46,17 @@ POTENTIAL ISSUES:
 - {concerns needing manual review}
 ```
 
+### Data Layer
+- Use `DataSourceResolver.repository` in ViewModels, not `MockDataProvider.shared` directly
+- Preserve MockDataProvider CRUD methods and `reset()` function
+- Do NOT modify NetworkMonitor, LocalPersistence, or OfflineBanner
+
 ## Rules
 - ONLY edit files under `output/` — never touch `templates/`
 - Ensure all imports resolve after changes
 - Keep `@main` struct and `App` protocol conformance intact
-- Preserve MockDataProvider function signatures
+- Preserve MockDataProvider CRUD methods and `reset()` function
+- Do NOT modify NetworkMonitor, LocalPersistence, or OfflineBanner
 - Use SF Symbols for tab and navigation icons
+- Preserve ALL `.accessibilityIdentifier()` calls — do NOT remove test IDs
+- Follow `{screen}_{element}_{role}` convention for new test IDs (see `templates/TEST_ID_CONVENTIONS.md`)

package/.claude/agents/react-native-customizer.md

@@ -0,0 +1,71 @@
+---
+name: react-native-customizer
+description: Specialized React Native/TypeScript subagent for customizing React Native app templates. Handles package config updates, component rewriting, React Navigation adjustments, theme application, and cross-platform features.
+tools: Read, Edit, Write, Grep, Glob, LS, Bash
+model: sonnet
+---
+
+You are an expert React Native developer specializing in TypeScript and modern mobile development. You handle all React Native-specific customization tasks for the AppAgent pipeline.
+
+## Your Expertise
+- React Native 0.73+, TypeScript 5+, React Navigation 6+
+- MVVM architecture with custom hooks (`useXxxViewModel`)
+- StyleSheet.create() for performant styling
+- FlatList / SectionList for virtualized lists
+- React Context for theming and global state
+
+## Tasks You Handle
+
+### Package & Project Renaming
+1. Update `package.json` — `name` field
+2. Update `app.json` — `name` and `displayName`
+3. Update `android/app/build.gradle` — `applicationId`, `namespace`
+4. Update `android/settings.gradle` — `rootProject.name`
+5. Update `android/app/src/main/res/values/strings.xml` — `app_name`
+6. Update `android/app/src/main/java/` — package directories, `MainActivity.kt`, `MainApplication.kt`
+7. Update `ios/Podfile` — project target name
+8. Update all imports if module paths changed
+
+### React Native Component Customization
+- Use functional components with `React.FC` typing
+- Use custom hooks (`useXxxViewModel`) for state and business logic
+- Use `StyleSheet.create()` for all styles — no inline style objects
+- Use `FlatList` / `SectionList` for lists (not `map()` on `ScrollView`)
+- Add `testID` props to ALL interactive elements
+
+### Navigation Structure
+Templates use React Navigation with bottom tabs and native stack. When modifying:
+- Update tab names and components in `AppNavigator.tsx`
+- Update `RootStackParamList` type for type-safe navigation
+- Apply tab labels from content brief and icons from design brief
+
+### Theme Customization
+- Update `ThemeContext.tsx` colors to match brand palette
+- Provide both light and dark mode variants
+- Apply corner radius, spacing, and typography tokens
+
+## Output
+```
+FILES MODIFIED:
+- {path}: {what changed}
+POTENTIAL ISSUES:
+- {concerns needing manual review}
+```
+
+### Data Layer
+- Use `DataSourceResolver.repository` in ViewModel hooks, not `MockDataProvider` directly
+- Preserve MockDataProvider CRUD methods and `reset()` function
+- Do NOT modify NetworkMonitor, LocalPersistence, or OfflineBanner
+
+## Rules
+- ONLY edit files under `output/` — never touch `templates/`
+- Ensure all imports resolve after changes
+- Preserve MockDataProvider CRUD methods and `reset()` function
+- Do NOT modify NetworkMonitor, LocalPersistence, or OfflineBanner
+- Ensure OfflineBanner is integrated into main navigation screens
+- Use `testID` props on ALL interactive elements
+- Follow `{screen}_{element}_{role}` convention for test IDs (see `templates/TEST_ID_CONVENTIONS.md`)
+- Use `StyleSheet.create()` for styles, not inline objects
+- Keep React Navigation structure intact
+- Preserve ThemeContext provider wrapping in App.tsx
+- Do NOT introduce new npm dependencies

package/.claude/skills/android-customizer/SKILL.md

@@ -9,7 +9,7 @@ Use this skill to perform deep Android/Kotlin/Compose customization on a cloned
 
 ## When to Use
 
-- At Step 8 of the AppAgent workflow, when the platform is Android
+- At Step 5 of the AppAgent workflow, when the platform is Android
 - After AppConfig, mock data, and design tokens are already in place
 - When you need to modify Compose screens, navigation, and themes
 
@@ -102,6 +102,17 @@ Android templates use Material 3 dynamic theming in `Theme.kt`:
 - Apply typography scale if the design brief specifies custom fonts
 - Apply shape theme (corner radius) from the design brief
 
+### Step 5.5 — Generate App Launcher Icon
+
+Customize the adaptive icon using the manifest's **App Launcher Icon** section:
+
+1. Read the icon spec: `Android vector keyword` (e.g., `shopping`) and `Background` hex color
+2. Read `templates/android/ICON_VECTORS.md`, find the matching keyword section, copy the XML into `app/src/main/res/drawable/ic_launcher_foreground.xml`
+3. Update `app/src/main/res/values/colors.xml`: set `ic_launcher_background` to the background hex
+4. Verify `ic_launcher.xml` and `ic_launcher_round.xml` reference the correct foreground/background
+
+If `ICON_VECTORS.md` does not exist or the keyword is not found, keep the default icon and only update the background color.
+
 ### Step 6 — Data Layer & Offline Infrastructure
 
 Templates now include an **offline-first data layer**. Understand these components:
@@ -119,19 +130,26 @@ Templates now include an **offline-first data layer**. Understand these componen
   - `reset()` function references correct defaults
 - `data/SyncManager.kt` — if entity types were renamed, update domain methods
 
-**ViewModel/Screen patterns** (how screens consume data):
+**Screen/ViewModel patterns** (how screens consume data):
+
+Screens and ViewModels use the `DataRepository` interface abstraction, not `MockDataProvider` directly:
 ```kotlin
-// Screens collect StateFlow
-val products by MockDataProvider.products.collectAsState()
+// Screens get the repository from DataSourceResolver
+val repository = remember { DataSourceResolver.repository }
+val items by repository.items.collectAsState()
+val categories by repository.categories.collectAsState()
 
-// ViewModels read from MockDataProvider
-val products = MockDataProvider.products.value
+// CRUD via the repository
+repository.addItem(newItem)
+repository.deleteItem(item)
+repository.toggleFavorite(item)
 
-// CRUD via SyncManager
+// If SyncManager exists, it wraps the repository
 SyncManager.addProduct(newProduct)
-SyncManager.deleteProduct(id)
 ```
 
+When customizing screens or ViewModels, ALWAYS use `DataSourceResolver.repository`, never `MockDataProvider` directly. This ensures the app works with any data source.
+
 **OfflineBanner integration** — add to main navigation:
 ```kotlin
 Column {
@@ -151,26 +169,75 @@ class MyApplication : Application() {
 }
 ```
 
-### Step 7 — MockDataProvider Verification
+### Step 7 — Data Layer Verification
 
-Verify MockDataProvider uses the correct patterns:
+Verify the data layer uses the correct patterns:
 
+**DataRepository interface:**
 ```kotlin
-object MockDataProvider {
+interface DataRepository {
+    val items: StateFlow<List<Item>>
+    val categories: StateFlow<List<Category>>
+    val favoriteItems: StateFlow<List<Item>>
+    fun loadData()
+    fun addItem(item: Item)
+    // ... all CRUD + query methods
+}
+```
+
+**MockDataProvider (implements DataRepository):**
+```kotlin
+object MockDataProvider : DataRepository {
     private val _products = MutableStateFlow(defaultProducts)
-    val products: StateFlow<List<Product>> = _products.asStateFlow()
-    
-    val defaultProducts = listOf(...)  // Seed data
-    
-    fun addProduct(product: Product) { ... }  // CRUD
-    fun reset() { ... }  // Reset to defaults
+    override val products: StateFlow<List<Product>> = _products.asStateFlow()
+    val defaultProducts = listOf(...)
+    override fun addProduct(product: Product) { ... }
+    fun reset() { ... }
+}
+```
+
+**DataSourceResolver:**
+```kotlin
+object DataSourceResolver {
+    val repository: DataRepository
+        get() = when (AppConfig.DataSource.active) {
+            AppConfig.DataSource.SourceType.MOCK -> MockDataProvider
+            AppConfig.DataSource.SourceType.LOCAL_STORAGE -> MockDataProvider  // TODO
+        }
 }
 ```
 
-- Verify seed data matches the new domain
-- Ensure CRUD functions reference correct entity types
-- Verify `reset()` works correctly
-- Check that helper functions use `.value` to read from StateFlows
+Verify:
+- DataRepository interface matches MockDataProvider's public members
+- MockDataProvider implements DataRepository with `override` on all members
+- DataSourceResolver returns the correct implementation
+- Screens use `DataSourceResolver.repository`, not `MockDataProvider` directly
+- Seed data matches the new domain
+- CRUD functions reference correct entity types
+
+### Step 7.5 — Apply Animation Modifiers (if animation modules are integrated)
+
+If the customization manifest includes an **"Animation & Sensory Plan"** section:
+
+1. Read the "Per-Screen Animation Modifiers" table from the manifest
+2. For each screen in your batch, apply the assigned modifiers:
+
+```kotlin
+// MicroInteractions — press feedback
+Button(onClick = { }, modifier = Modifier.scaleOnPress().hapticFeedback(HapticFeedbackStyle.IMPACT_MEDIUM))
+
+// ScrollEffects — parallax header
+ParallaxHeader(height = 280.dp, scrollState = scrollState) { AsyncImage(model = item.imageUrl) }
+
+// AnimatedTransitions — staggered list items
+ItemRow(item = item, modifier = Modifier.staggeredAppearance(index = index))
+
+// CelebrationEffects — success overlay
+Box(modifier = Modifier.celebrationOverlay(isActive = showCelebration, style = CelebrationStyle.CONFETTI))
+```
+
+3. Wrap all applied animations with `motionAwareAnimationSpec()` if MotionPreferences is integrated
+4. Do NOT add animation modifiers to screens not listed in the manifest
 
 ## Report Output
 
@@ -179,7 +246,7 @@ Write the report to `output/{app-name}/reports/05-customization.md` (append Andr
 ```markdown
 # Customization Report
 
-**Step:** 8
+**Step:** 5
 **Skill:** android-customizer
 **Timestamp:** {ISO 8601}
 **Result:** PASS
@@ -214,6 +281,11 @@ Android (Kotlin / Jetpack Compose)
 - SyncManager methods updated: {list or "no changes needed"}
 - Data persistence verified: {yes/no}
 
+## Animation Modifiers Applied
+
+- {modifier}: applied to {screen} — {description}
+- MotionPreferences respected: {yes/no/N/A}
+
 ## Potential Issues
 
 - {any concerns or items needing manual review}
@@ -225,7 +297,7 @@ Update `output/{app-name}/reports/summary.json` — read the file, append this s
 
 ```json
 {
-  "step": 8,
+  "step": 5,
   "name": "android-customization",
   "startedAt": "{ISO 8601 timestamp}",
   "durationSeconds": 0,

package/.claude/skills/ios-customizer/SKILL.md

@@ -9,7 +9,7 @@ Use this skill to perform deep iOS/SwiftUI customization on a cloned template.
 
 ## When to Use
 
-- At Step 8 of the AppAgent workflow, when the platform is iOS
+- At Step 5 of the AppAgent workflow, when the platform is iOS
 - After AppConfig, mock data, and design tokens are already in place
 - When you need to modify SwiftUI views, navigation, and themes
 
@@ -100,6 +100,16 @@ iOS templates use a `Colors.swift` theme file:
 - Use semantic colors where possible (`Color.primary`, `Color.secondary`)
 - Apply corner radius and spacing tokens from the design brief
 
+### Step 4.5 — Generate App Launcher Icon
+
+Generate a domain-specific app icon using the manifest's **App Launcher Icon** section:
+
+1. Read the icon spec: `iOS SF Symbol` (e.g., `bag.fill`) and `Background` hex color
+2. Run: `swift scripts/generate-app-icon.swift "{symbol}" "{background}" "output/{app-name}/{AppName}/Resources/Assets.xcassets/AppIcon.appiconset/"`
+3. Verify `AppIcon-1024.png` exists in the output directory
+
+If `scripts/generate-app-icon.swift` does not exist or fails, skip — the template's default icon will be used.
+
 ### Step 5 — Data Layer & Offline Infrastructure
 
 Templates now include an **offline-first data layer**. Understand these components:
@@ -118,18 +128,31 @@ Templates now include an **offline-first data layer**. Understand these componen
 - `Data/SyncManager.swift` — if entity types were renamed, update domain methods
 
 **ViewModel patterns** (how views consume data):
+
+ViewModels use the `DataRepository` protocol abstraction, not `MockDataProvider` directly:
 ```swift
-// ViewModels observe MockDataProvider.shared
-@ObservedObject var store = MockDataProvider.shared
+// ViewModels depend on the DataRepository protocol
+private let repository: any DataRepository
+
+init(repository: any DataRepository = DataSourceResolver.repository) {
+    self.repository = repository
+}
+
+// Read data via the protocol
+let items = repository.items
+let categories = repository.categories
 
-// Or use EnvironmentObject if injected
-@EnvironmentObject var store: MockDataProvider
+// CRUD via the protocol
+repository.addItem(newItem)
+repository.deleteItem(item)
+repository.toggleFavorite(item)
 
-// CRUD via SyncManager
+// If SyncManager exists, it wraps the repository
 SyncManager.shared.addProduct(newProduct)
-SyncManager.shared.deleteProduct(id)
 ```
 
+When customizing ViewModels, ALWAYS use `repository` (from `DataSourceResolver`), never `MockDataProvider.shared` directly. This ensures the app works with any data source.
+
 **OfflineBanner integration** — add to main navigation views:
 ```swift
 VStack(spacing: 0) {
@@ -138,27 +161,78 @@ VStack(spacing: 0) {
 }
 ```
 
-### Step 6 — MockDataProvider Verification
+### Step 6 — Data Layer Verification
 
-Verify the MockDataProvider uses the correct patterns:
+Verify the data layer uses the correct patterns:
 
+**DataRepository protocol:**
 ```swift
-class MockDataProvider: ObservableObject {
+protocol DataRepository: AnyObject {
+    var items: [Item] { get }
+    var categories: [Category] { get }
+    var favoriteItems: [Item] { get }
+    func loadData()
+    func addItem(_ item: Item)
+    // ... all CRUD + query methods
+}
+```
+
+**MockDataProvider (conforms to DataRepository):**
+```swift
+class MockDataProvider: ObservableObject, DataRepository {
     static let shared = MockDataProvider()
-    
-    @Published var products: [Product]  // Reactive, mutable
-    
-    static let defaultProducts: [Product] = [...]  // Seed data
-    
-    func addProduct(_ product: Product) { ... }  // CRUD
-    func reset() { ... }  // Reset to defaults
+    @Published var products: [Product]
+    static let defaultProducts: [Product] = [...]
+    func addProduct(_ product: Product) { ... }
+    func reset() { ... }
+}
+```
+
+**DataSourceResolver:**
+```swift
+enum DataSourceResolver {
+    static var repository: any DataRepository {
+        switch AppConfig.DataSource.active {
+        case .mock: return MockDataProvider.shared
+        case .localStorage: return MockDataProvider.shared  // TODO: LocalStorageProvider
+        }
+    }
 }
 ```
 
-- Verify seed data matches the new domain
-- Ensure CRUD methods reference correct entity types
-- Verify `reset()` works correctly
-- Check that `@Published` properties are being observed by ViewModels
+Verify:
+- DataRepository protocol matches MockDataProvider's public interface
+- MockDataProvider conforms to DataRepository
+- DataSourceResolver returns the correct implementation
+- ViewModels use `DataSourceResolver.repository`, not `MockDataProvider.shared` directly
+- Seed data matches the new domain
+- CRUD methods reference correct entity types
+
+### Step 6.5 — Apply Animation Modifiers (if animation modules are integrated)
+
+If the customization manifest includes an **"Animation & Sensory Plan"** section:
+
+1. Read the "Per-Screen Animation Modifiers" table from the manifest
+2. For each screen in your batch, apply the assigned modifiers:
+
+```swift
+// MicroInteractions — press feedback
+Button("Add to Cart") { ... }
+    .scaleOnPress()
+    .hapticFeedback(.impact(.medium))
+
+// ScrollEffects — parallax header
+ParallaxHeaderView(height: 280) { AsyncImage(url: item.imageURL) }
+
+// AnimatedTransitions — staggered list items
+ItemRow(item: items[index]).staggeredAppearance(index: index)
+
+// CelebrationEffects — success overlay
+.celebrationOverlay(isPresented: $showCelebration, style: .confetti)
+```
+
+3. Wrap all applied animations with `.motionAware()` if MotionPreferences is integrated
+4. Do NOT add animation modifiers to screens not listed in the manifest
 
 ## Report Output
 
@@ -167,7 +241,7 @@ Write the report to `output/{app-name}/reports/05-customization.md` (append iOS
 ```markdown
 # Customization Report
 
-**Step:** 8
+**Step:** 5
 **Skill:** ios-customizer
 **Timestamp:** {ISO 8601}
 **Result:** PASS
@@ -201,6 +275,11 @@ iOS (Swift / SwiftUI)
 - SyncManager methods updated: {list or "no changes needed"}
 - Data persistence verified: {yes/no}
 
+## Animation Modifiers Applied
+
+- {modifier}: applied to {screen} — {description}
+- MotionPreferences respected: {yes/no/N/A}
+
 ## Potential Issues
 
 - {any concerns or items needing manual review}
@@ -212,7 +291,7 @@ Update `output/{app-name}/reports/summary.json` — read the file, append this s
 
 ```json
 {
-  "step": 8,
+  "step": 5,
   "name": "ios-customization",
   "startedAt": "{ISO 8601 timestamp}",
   "durationSeconds": 0,

package/.claude/skills/react-native-customizer/SKILL.md

@@ -91,27 +91,88 @@ React Native templates use a `ThemeContext.tsx`:
 - Apply corner radius and spacing tokens
 - Apply typography settings (font sizes, weights)
 
-### Step 5 — Data Layer & Mock Data
+### Step 5 — Data Layer & Offline Infrastructure
+
+Templates include an **offline-first data layer**:
 
 **Files you should NOT modify** (generic infrastructure):
 - `src/data/DataRepository.ts` — interface definition
+- `src/data/NetworkMonitor.ts` — connectivity detection
+- `src/data/LocalPersistence.ts` — JSON file persistence
+- `src/components/OfflineBanner.tsx` — offline status banner
 - `src/theme/ThemeContext.tsx` — theme provider
 
 **Files you MAY need to update** (domain-specific):
-- `src/mock/MockDataProvider.ts` — seed data already updated in Step 4. Verify:
-  - Seed data matches the new domain
-  - All CRUD methods work with correct entity types
-  - Subscription/onChange pattern is working
-  - Reset method references correct defaults
+- `src/mock/MockDataProvider.ts` — seed data already updated in Step 4. Verify seed data, CRUD methods, subscription pattern, and reset defaults
+- `src/data/SyncManager.ts` — if entity types were renamed, update domain methods
+
+**ViewModel patterns** — use `DataSourceResolver`, not `MockDataProvider` directly:
+```tsx
+import { DataSourceResolver } from '../data/DataSourceResolver';
+
+export function useHomeViewModel() {
+  const repository = DataSourceResolver.repository;
+  const [items, setItems] = useState<Item[]>([]);
+  useEffect(() => {
+    setItems(repository.getItems());
+    const unsubscribe = repository.subscribe(() => setItems(repository.getItems()));
+    return unsubscribe;
+  }, []);
+  return { items };
+}
+```
+
+**OfflineBanner integration** — add to main navigation screens:
+```tsx
+<View style={{ flex: 1 }}>
+  <OfflineBanner />
+  {/* ... rest of screen content */}
+</View>
+```
 
-### Step 6 — MockDataProvider Verification
+### Step 6 — Data Layer Verification
 
-Verify the MockDataProvider uses correct patterns:
-- Implements all DataRepository methods
-- ViewModel hooks use MockDataProvider correctly
+Verify:
+- `DataRepository` interface matches MockDataProvider's public methods
+- MockDataProvider implements DataRepository
+- `DataSourceResolver` returns the correct implementation
+- ViewModel hooks use `DataSourceResolver.repository`, not `MockDataProvider` directly
 - Seed data matches the new domain
 - CRUD methods reference correct entity types
 
+### Step 6.5 — Apply Animation Modifiers (if animation modules are integrated)
+
+If the manifest includes an **"Animation & Sensory Plan"** section:
+
+1. Read the "Per-Screen Animation Modifiers" table
+2. Apply the assigned modifiers using imported module hooks/components:
+
+```typescript
+// MicroInteractions — press feedback
+import { useScaleOnPress } from '../shared/MicroInteractions';
+import { useHapticEngine } from '../shared/HapticEngine';
+const { animatedStyle, handlers } = useScaleOnPress();
+
+// ScrollEffects — parallax header
+import { ParallaxHeader } from '../shared/ScrollEffects';
+<ParallaxHeader height={280} imageSource={item.imageUrl} />
+
+// CelebrationEffects — success overlay
+import { CelebrationOverlay } from '../shared/CelebrationEffects';
+<CelebrationOverlay isActive={showCelebration} style="confetti" />
+```
+
+3. Wrap with `useMotionPreferences` checks if MotionPreferences is integrated
+4. Do NOT add animation modifiers to screens not listed in the manifest
+
+### Step 6.7 — App Icon (if applicable)
+
+React Native apps target both iOS and Android. App icon customization is handled per-platform:
+- **iOS**: If `scripts/generate-app-icon.swift` exists, run it with SF Symbol + background color from manifest
+- **Android**: If `templates/android/ICON_VECTORS.md` exists, update `ic_launcher_foreground.xml` and `ic_launcher_background` color
+
+If scripts/resources are not available, skip — default icons will be used.
+
 ## Report Output
 
 Write the report to `output/{app-name}/reports/05-customization.md`:
@@ -144,6 +205,17 @@ React Native (TypeScript)
 - Empty states: {count}
 - CTAs updated: {count}
 
+## Offline Infrastructure
+
+- OfflineBanner integrated: {yes/no}
+- SyncManager methods updated: {list or "no changes needed"}
+- Data persistence verified: {yes/no}
+
+## Animation Modifiers Applied
+
+- {modifier}: applied to {screen} — {description}
+- MotionPreferences respected: {yes/no/N/A}
+
 ## Potential Issues
 
 - {any concerns}
@@ -191,8 +263,10 @@ Templates include `testID` props on all interactive elements and a `TESTING_MANI
 - ONLY edit files under `output/` — never touch `templates/`
 - Ensure all imports resolve after your changes
 - Preserve `MockDataProvider` CRUD methods and `reset()` function
+- Do NOT modify NetworkMonitor, LocalPersistence, or OfflineBanner
+- Ensure OfflineBanner is integrated into main navigation screens
 - Use `testID` props on ALL interactive elements
-- Follow `{screen}_{element}_{role}` convention for new test IDs
+- Follow `{screen}_{element}_{role}` convention for new test IDs (see `templates/TEST_ID_CONVENTIONS.md`)
 - Use `StyleSheet.create()` for styles, not inline objects
 - Use functional components with TypeScript
 - Keep React Navigation structure intact

package/.cursor/agents/android-customizer.md

@@ -123,18 +123,19 @@ private val LightColorScheme = lightColorScheme(
 - Use Material 3 color roles (primary, secondary, tertiary, surface, etc.)
 - Keep `dynamicColor` support if present
 
-### MockDataProvider Updates
-Android MockDataProvider uses companion object with functions:
+### Data Layer
+Templates use a `DataRepository` interface with `DataSourceResolver`:
 ```kotlin
-object MockDataProvider {
-    fun getServices(): List<Service> = listOf(...)
-    fun getProviders(): List<Provider> = listOf(...)
-}
+// Screens get the repository from DataSourceResolver
+val repository = remember { DataSourceResolver.repository }
+val items by repository.items.collectAsState()
+repository.addItem(newItem)
 ```
-- Keep the same function signatures
-- Update return values with domain-specific data
-- Use `UUID.randomUUID().toString()` for IDs
-- Use `LocalDateTime.now()` and `LocalDate` for dates
+- ALWAYS use `DataSourceResolver.repository`, never `MockDataProvider` directly
+- Preserve MockDataProvider CRUD functions and `reset()` method
+- Do NOT modify NetworkMonitor, LocalPersistence, or OfflineBanner
+- Verify NetworkMonitor is registered in the Application class
+- Ensure OfflineBanner is integrated into main navigation composables
 
 ## Output
 
@@ -155,5 +156,8 @@ POTENTIAL ISSUES:
 - Ensure all `import` statements resolve after renaming
 - Keep `@HiltAndroidApp`, `@HiltViewModel`, `@AndroidEntryPoint` intact
 - Keep `build.gradle.kts` syntactically valid Kotlin DSL
-- Preserve `MockDataProvider` function signatures
+- Preserve `MockDataProvider` CRUD functions and `reset()` method
+- Do NOT modify NetworkMonitor, LocalPersistence, or OfflineBanner
 - Use Material 3 components (not legacy Material 2)
+- Preserve ALL `Modifier.testTag()` calls — do NOT remove test IDs
+- Follow `{screen}_{element}_{role}` convention for new test tags (see `templates/TEST_ID_CONVENTIONS.md`)