@jetrabbits/agentic 0.0.1

package/areas/software/mlops/workflows/train-experiment.md

@@ -0,0 +1,56 @@
+---
+name: train-experiment
+type: workflow
+trigger: /train-experiment
+description: Run a reproducible model training experiment with full environment snapshot and automatic evaluation.
+inputs:
+  - model_name
+  - training_config
+outputs:
+  - trained_model_artifact
+  - evaluation_scorecard
+roles:
+  - developer
+  - qa
+execution:
+  initiator: developer
+related-rules:
+  - reproducibility.md
+  - data-integrity.md
+uses-skills:
+  - experiment-tracking
+  - feature-engineering
+quality-gates:
+  - environment fully snapshotted before training starts
+  - training loss decreased monotonically
+  - model artifact logged to MLflow with all metadata
+---
+
+## Steps
+
+### 1. Prerequisites Validation — `@developer`
+- **Input:** model name, config YAML
+- **Actions:** confirm data version exists and quality checks passed; verify training config YAML is valid; check compute resource budget
+- **Output:** validation confirmation
+- **Done when:** all prerequisites met; no blockers
+
+### 2. Environment Snapshot — `@developer`
+- **Input:** validated prerequisites
+- **Actions:** log git commit hash; build/verify training Docker image digest; register data snapshot version in MLflow
+- **Output:** immutable environment record in MLflow run
+- **Done when:** snapshot logged; run is reproducible from this state
+
+### 3. Training Run — `@developer`
+- **Input:** snapshotted environment
+- **Actions:** submit job to training cluster; stream training logs; surface loss curves in real-time; monitor for anomalies (NaN loss, divergence)
+- **Output:** completed training run; model artifact in MLflow
+- **Done when:** all epochs completed; loss decreased; artifact logged
+
+### 4. Validation — `@qa`
+- **Input:** completed run
+- **Actions:** confirm training loss decreased monotonically; verify model artifact logged correctly; run `/evaluate-model` automatically; compare against current champion
+- **Output:** evaluation scorecard; comparison vs. top 3 previous runs
+- **Done when:** evaluation complete; recommendation produced (promote / continue tuning / investigate)
+
+## Exit
+Logged artifact + evaluation scorecard + champion comparison = experiment complete.

package/areas/software/mobile/AGENTS.md

@@ -0,0 +1,58 @@
+# Mobile — guidance index
+
+## What this area covers
+
+iOS, Android, and cross-platform mobile development (React Native, Flutter): offline-first architecture, platform compliance (App Store / Play Store), performance budgets, native module integration, push notifications, OTA update delivery, release builds, and crash triage.
+
+## Guidance chain
+
+1. Project `.agent/` baseline (`AGENTS.md` + `.agent/*`)
+2. `software/general/rules/*` — always active
+3. `mobile/rules/*` — load all for this spec
+4. `mobile/skills/*/SKILL.md` — load only the skill matching the current task
+5. `mobile/workflows/*` — load the workflow matching the triggered command
+
+## Inherited from general
+
+- SDLC methodology and handoff contracts
+- Git / CI / lint and code style baselines
+
+## Mobile-specific constraints
+
+- Offline-first is the default architecture; network availability is assumed intermittent, not guaranteed.
+- Platform compliance rules (HIG for iOS, Material for Android) are enforced before store submission — not negotiable.
+- Performance budget (TTI, frame rate, memory) is defined before implementing any new screen.
+- Crash rate threshold defined in `rules/performance-budget.md` is a release blocker if exceeded.
+
+## Spec map
+
+```text
+mobile/
+├── rules/
+│   ├── offline-first.md          ← local state, sync strategy, conflict resolution
+│   ├── performance-budget.md     ← frame rate, TTI, memory, crash rate thresholds
+│   ├── platform-compliance.md    ← HIG, Material, store review requirements
+│   └── security-mobile.md        ← keychain/keystore, certificate pinning, jailbreak detection
+├── skills/
+│   ├── navigation-patterns/SKILL.md    ← stack, tab, drawer navigation; deep links
+│   ├── state-sync/SKILL.md             ← optimistic UI, background sync, conflict resolution
+│   ├── native-modules/SKILL.md         ← bridging, JSI, platform-specific APIs
+│   ├── push-notifications/SKILL.md     ← APNs, FCM, notification permissions, rich content
+│   ├── mobile-testing/SKILL.md         ← Detox, XCTest, Espresso, device farms
+│   └── app-store-prep/SKILL.md         ← metadata, screenshots, signing, compliance checklist
+├── workflows/
+│   ├── release-build.md       ← /release-build
+│   ├── store-submission.md    ← /store-submission
+│   ├── crash-triage.md        ← /crash-triage
+│   ├── ota-update.md          ← /ota-update
+│   └── device-testing.md      ← /device-testing
+└── prompts/
+    └── *.md
+```
+
+## Discovery patterns
+
+- `rules/*.md`
+- `skills/*/SKILL.md`
+- `workflows/*.md`
+- `prompts/*.md`

package/areas/software/mobile/PROMPTS.md

@@ -0,0 +1,32 @@
+# PROMPTS: mobile
+
+Use these prompts with `AGENTS.md` from the same directory.
+
+## 1) Initialize agent behavior
+
+```text
+Read `mobile/AGENTS.md` and adopt its rules, skills loading strategy, and workflows as hard constraints.
+List the active rules and the selected workflow before implementation.
+```
+
+## 2) Implement a feature
+
+```text
+Using `mobile/AGENTS.md`, implement: <feature description>.
+Before coding: provide architecture notes, risk list, and test plan.
+After coding: run checks and report exact commands and results.
+```
+
+## 3) Incident / debug mode
+
+```text
+Using `mobile/AGENTS.md`, run incident triage for: <incident summary>.
+Return root cause hypotheses, validation steps, fix plan, and rollback plan.
+```
+
+## 4) Release readiness
+
+```text
+Using `mobile/AGENTS.md`, prepare release checklist for: <release scope>.
+Include quality gates, security gates, performance gates, and deployment validation.
+```

package/areas/software/mobile/prompts/crash-triage.md

@@ -0,0 +1,63 @@
+---
+workflow: crash-triage
+---
+
+# Prompt: `/crash-triage`
+
+Use when: a production crash is reported via Crashlytics, Sentry, or user report.
+
+---
+
+## Example 1 — Crashlytics crash with symbolication
+
+**EN:**
+```
+/crash-triage
+
+Crash: NullPointerException in OrderDetailViewModel.loadOrder()
+Platform: Android 13, Samsung Galaxy S23
+Crash rate: 2.3% of sessions (affecting ~4 500 users)
+Crashlytics issue ID: CR-2024-1234
+First seen: 3 days ago (correlates with v2.1.0 release)
+Stack trace: attached from Crashlytics (unsymbolicated)
+Suspected: race condition — user navigating away before async load completes
+```
+
+**RU:**
+```
+/crash-triage
+
+Крэш: NullPointerException в OrderDetailViewModel.loadOrder()
+Платформа: Android 13, Samsung Galaxy S23
+Частота крэшей: 2.3% сессий (~4 500 пользователей)
+Crashlytics issue ID: CR-2024-1234
+Первый раз замечен: 3 дня назад (совпадает с релизом v2.1.0)
+Stack trace: приложен из Crashlytics (без символикации)
+Предположение: race condition — пользователь уходит со страницы до завершения async загрузки
+```
+
+---
+
+## Example 2 — iOS crash on specific device
+
+**EN:**
+```
+/crash-triage
+
+Crash: EXC_BAD_ACCESS in ImageCacheManager
+Platform: iOS 17.2, iPhone 15 Pro only (not reproducible on older devices)
+Crash rate: 8% on iPhone 15 Pro, 0% on other devices
+Suspected: memory pressure on ProMotion display with high-res images
+dSYM available: yes (uploaded to Xcode Organizer)
+```
+
+**RU:**
+```
+/crash-triage
+
+Крэш: EXC_BAD_ACCESS в ImageCacheManager
+Платформа: iOS 17.2, только iPhone 15 Pro (не воспроизводится на старых устройствах)
+Частота крэшей: 8% на iPhone 15 Pro, 0% на других устройствах
+Предположение: memory pressure на ProMotion дисплее с высококачественными изображениями
+dSYM доступен: да (загружен в Xcode Organizer)
+```

package/areas/software/mobile/prompts/device-testing.md

@@ -0,0 +1,83 @@
+---
+workflow: device-testing
+---
+
+# Prompt: `/device-testing`
+
+Use when: executing a structured test run across a device matrix before a release.
+
+---
+
+## Example 1 — Pre-release device matrix
+
+**EN:**
+```
+/device-testing
+
+Release: v3.2.0 (release candidate)
+Platform: iOS + Android
+Test matrix:
+  iOS:     iPhone 15 Pro (iOS 17), iPhone 12 (iOS 16), iPad Air (iPadOS 16)
+  Android: Pixel 8 (Android 14), Samsung Galaxy S21 (Android 13), OnePlus 9 (Android 12)
+Test tool: AWS Device Farm (Detox E2E suite)
+Critical flows: login, checkout, notifications, dark mode
+Accept criteria: zero crashes, all critical flows pass on all devices
+Blocking for release: any P1 crash on a supported device
+```
+
+**RU:**
+```
+/device-testing
+
+Релиз: v3.2.0 (release candidate)
+Платформа: iOS + Android
+Матрица устройств:
+  iOS:     iPhone 15 Pro (iOS 17), iPhone 12 (iOS 16), iPad Air (iPadOS 16)
+  Android: Pixel 8 (Android 14), Samsung Galaxy S21 (Android 13), OnePlus 9 (Android 12)
+Инструмент: AWS Device Farm (Detox E2E suite)
+Критические потоки: вход, оформление заказа, уведомления, тёмная тема
+Критерии приёмки: ноль крэшей, все критические потоки проходят на всех устройствах
+Блокирует релиз: любой P1 крэш на поддерживаемом устройстве
+```
+
+---
+
+## Example 2 — Post-fix focused matrix for a native permissions bug
+
+**EN:**
+```
+/device-testing
+
+Release: v3.2.1-rc1
+Platform: Android only
+Reason: camera permission flow was fixed after crashes on Samsung devices
+Focused matrix:
+  Android 14: Pixel 8, Galaxy S23
+  Android 13: Galaxy S21, Xiaomi 12
+  Android 12: OnePlus 9, Motorola Edge 30
+Critical scenarios:
+- first launch permission prompt
+- deny -> re-open scanner flow
+- grant permission from system settings and resume app
+- background/foreground transition while camera preview is active
+Accept criteria: zero crashes, no frozen preview, and permission state remains correct after process recreation
+```
+
+**RU:**
+```
+/device-testing
+
+Релиз: v3.2.1-rc1
+Платформа: только Android
+Причина: исправлен flow camera permission после крэшей на устройствах Samsung
+Фокусная матрица:
+  Android 14: Pixel 8, Galaxy S23
+  Android 13: Galaxy S21, Xiaomi 12
+  Android 12: OnePlus 9, Motorola Edge 30
+Критические сценарии:
+- первый запуск permission prompt
+- deny -> повторное открытие scanner flow
+- выдача разрешения из system settings и возврат в приложение
+- background/foreground transition при активном camera preview
+Критерии приёмки: ноль крэшей, отсутствие зависшего preview и корректное сохранение permission state после process recreation
+```

package/areas/software/mobile/prompts/ota-update.md

@@ -0,0 +1,75 @@
+---
+workflow: ota-update
+---
+
+# Prompt: `/ota-update`
+
+Use when: deploying a JavaScript bundle update via Expo EAS Update or CodePush without a store review cycle.
+
+---
+
+## Example 1 — Critical bug fix OTA
+
+**EN:**
+```
+/ota-update
+
+Tool: Expo EAS Update
+Change: hotfix - payment confirmation screen showed wrong total (display bug only, no data corruption)
+Target versions: 3.1.x and 3.2.x (both affected)
+Rollout: 100% immediately (critical display bug, low risk)
+Validation: test on iOS 16+ and Android 12+ before push
+Rollback plan: revert to previous update bundle if error rate increases
+```
+
+**RU:**
+```
+/ota-update
+
+Инструмент: Expo EAS Update
+Изменение: хотфикс - экран подтверждения платежа показывал неверную сумму (только визуальный баг, данные не повреждены)
+Целевые версии: 3.1.x и 3.2.x (обе затронуты)
+Выкатка: 100% сразу (критический визуальный баг, низкий риск)
+Валидация: протестировать на iOS 16+ и Android 12+ перед публикацией
+План отката: откатить к предыдущему bundle если вырастет error rate
+```
+
+---
+
+## Example 2 — Staged OTA for a settings-screen regression
+
+**EN:**
+```
+/ota-update
+
+Tool: CodePush
+Change: JS-only fix for settings screen where toggling push notifications resets language preference
+Target audience: app versions 3.3.0 and 3.3.1, production channel only
+Rollout plan:
+- 5% for 1 hour
+- 50% after crash-free rate and JS error rate stay stable
+- 100% by the next morning if adoption is healthy
+Checks:
+- confirm no native permissions or config plugins changed
+- monitor JS error fingerprints in Sentry during rollout
+- prepare CodePush rollback command before the 5% stage starts
+Output: rollout checklist, validation evidence, and adoption monitoring plan for 48h
+```
+
+**RU:**
+```
+/ota-update
+
+Инструмент: CodePush
+Изменение: JS-only исправление экрана настроек, где переключение push notifications сбрасывает language preference
+Целевая аудитория: версии приложения 3.3.0 и 3.3.1, только production channel
+План выката:
+- 5% на 1 час
+- 50% после того как crash-free rate и JS error rate останутся стабильными
+- 100% к следующему утру, если adoption проходит нормально
+Проверки:
+- подтвердить, что native permissions и config plugins не менялись
+- мониторить JS error fingerprints в Sentry во время rollout
+- подготовить команду CodePush rollback до старта этапа 5%
+Результат: rollout checklist, validation evidence и план мониторинга adoption на 48ч
+```

package/areas/software/mobile/prompts/release-build.md

@@ -0,0 +1,67 @@
+---
+workflow: release-build
+---
+
+# Prompt: `/release-build`
+
+Use when: creating a production-ready build for app store submission or internal distribution.
+
+---
+
+## Example 1 — App Store release build
+
+**EN:**
+```
+/release-build
+
+Platform: iOS + Android
+Version: 3.2.0 (build 145)
+Release type: production App Store / Google Play
+Signing: iOS — Distribution certificate + App Store provisioning profile; Android — release keystore (CI secrets)
+Environment: prod API (https://api.myapp.com)
+Changes since last build: notification center, dark mode, performance fixes
+Required: changelogs for both stores (EN + RU)
+CI: GitHub Actions (fastlane lanes: ios_release, android_release)
+```
+
+**RU:**
+```
+/release-build
+
+Платформа: iOS + Android
+Версия: 3.2.0 (сборка 145)
+Тип релиза: production App Store / Google Play
+Подпись: iOS — Distribution certificate + App Store provisioning profile; Android — release keystore (CI secrets)
+Окружение: prod API (https://api.myapp.com)
+Изменения с прошлой сборки: центр уведомлений, тёмная тема, исправления производительности
+Необходимо: changelogs для обеих магазинов (EN + RU)
+CI: GitHub Actions (fastlane lanes: ios_release, android_release)
+```
+
+---
+
+## Example 2 — Internal/QA distribution build
+
+**EN:**
+```
+/release-build
+
+Platform: Android only
+Version: 3.2.0-rc.2 (build 143)
+Release type: internal testing (Firebase App Distribution)
+Environment: staging API
+Testers: QA team + product managers (distribution group: "qa-team")
+No store screenshots or release notes needed
+```
+
+**RU:**
+```
+/release-build
+
+Платформа: только Android
+Версия: 3.2.0-rc.2 (сборка 143)
+Тип релиза: внутреннее тестирование (Firebase App Distribution)
+Окружение: staging API
+Тестировщики: QA команда + продакт менеджеры (группа: "qa-team")
+Скриншоты для магазина и release notes не нужны
+```

package/areas/software/mobile/prompts/store-submission.md

@@ -0,0 +1,79 @@
+---
+workflow: store-submission
+---
+
+# Prompt: `/store-submission`
+
+Use when: submitting a build to App Store Connect or Google Play Console for review.
+
+---
+
+## Example 1 — Full store submission
+
+**EN:**
+```
+/store-submission
+
+Platform: iOS + Android
+Build: v3.2.0 (build 145) - already uploaded to App Store Connect + Play Console
+New features to describe: dark mode, notification center
+New permissions: push notifications (iOS - already in Info.plist)
+Privacy policy: https://myapp.com/privacy (no changes)
+Target regions: worldwide
+Review notes for Apple: test account credentials in submission (email: review@myapp.com / Pass123!)
+Screenshots: updated for iPhone 15 Pro, iPad, Pixel 8 (attached to submission)
+```
+
+**RU:**
+```
+/store-submission
+
+Платформа: iOS + Android
+Сборка: v3.2.0 (build 145) - уже загружена в App Store Connect + Play Console
+Новые функции для описания: тёмная тема, центр уведомлений
+Новые разрешения: push-уведомления (iOS - уже в Info.plist)
+Политика конфиденциальности: https://myapp.com/privacy (изменений нет)
+Целевые регионы: весь мир
+Заметки для ревью Apple: учётные данные тестового аккаунта в заявке (email: review@myapp.com / Pass123!)
+Скриншоты: обновлены для iPhone 15 Pro, iPad, Pixel 8 (приложены к заявке)
+```
+
+---
+
+## Example 2 — Incremental Android rollout after a sensitive permissions change
+
+**EN:**
+```
+/store-submission
+
+Platform: Android
+Build: v3.3.0 (versionCode 211)
+Track: closed testing -> production 20% rollout
+Change summary:
+- added background location usage for courier tracking
+- updated onboarding copy and in-app disclosures
+Compliance requirements:
+- Play Console data safety form must reflect continuous location collection
+- screenshots updated for courier mode and permission education screen
+- support team needs rollout notes and rejection fallback plan
+Post-release monitoring: crash-free rate >= 99.5% for 48h and no spike in 1-star reviews mentioning permissions
+Output: submission checklist, metadata package, and monitoring plan for staged production rollout
+```
+
+**RU:**
+```
+/store-submission
+
+Платформа: Android
+Сборка: v3.3.0 (versionCode 211)
+Трек: closed testing -> production rollout 20%
+Сводка изменений:
+- добавлено использование background location для courier tracking
+- обновлены onboarding copy и in-app disclosures
+Требования compliance:
+- форма Play Console data safety должна отражать постоянный сбор location
+- скриншоты обновлены для courier mode и экрана объяснения permission
+- команде поддержки нужны rollout notes и план действий на случай rejection
+Пострелизный мониторинг: crash-free rate >= 99.5% в течение 48ч и отсутствие всплеска 1-star review с упоминанием permissions
+Результат: submission checklist, пакет metadata и план мониторинга для staged production rollout
+```

package/areas/software/mobile/rules/offline-first.md

@@ -0,0 +1,10 @@
+# Rule: Offline-First Architecture
+
+**Priority**: P1 — Mobile apps must be functional without network connectivity.
+
+1. **Optimistic UI required**: User actions update the UI immediately without waiting for network.
+2. **Network state awareness**: Every screen requiring network data handles offline state with clear UI feedback, not blank screens.
+3. **Sync conflict resolution**: Defined conflict resolution strategy must exist and be documented.
+4. **Queue persistence**: Outgoing action queue must be persisted to disk (not memory) to survive app termination.
+5. **Background sync**: Queued actions synced when connectivity restored, including when app is backgrounded.
+6. **Stale data disclosure**: Cached data older than SLA for that data type must be labeled "Last updated X ago."

package/areas/software/mobile/rules/performance-budget.md

@@ -0,0 +1,20 @@
+# Rule: Mobile Performance Budget
+
+**Priority**: P1 — Poor mobile performance directly correlates with abandonment.
+
+## Thresholds
+
+| Metric | Target | Hard Limit |
+|:---|:---|:---|
+| Cold start | < 2s | < 3s |
+| Time to interactive | < 1s after bundle | < 2s |
+| JS bundle size | < 2 MB | < 4 MB |
+| Memory usage (background) | < 50 MB | < 100 MB |
+| Frame rate | 60 fps | 30 fps minimum |
+
+## Constraints
+
+1. **No blocking the JS thread**: Long computations offloaded to native modules or worker threads.
+2. **FlatList for all lists**: Never `ScrollView` for lists of unknown length. Use `FlatList` or `FlashList`.
+3. **Image optimization**: All images resized to display size before loading. Use `FastImage` for caching.
+4. **Hermes engine**: Must be enabled on both platforms.

package/areas/software/mobile/rules/platform-compliance.md

@@ -0,0 +1,17 @@
+# Rule: Platform Compliance
+
+**Priority**: P0 — Violations cause App Store / Play Store rejection or delisting.
+
+## iOS (App Store)
+
+1. **Privacy nutrition labels**: All data collected declared in App Store Connect privacy section.
+2. **Required capabilities declared**: Every capability (camera, location, microphone) declared in `Info.plist` with usage description.
+3. **In-app purchase compliance**: Digital goods must use Apple IAP. No workarounds for App Store builds.
+4. **Minimum iOS version**: Support iOS 16+ minimum.
+
+## Android (Play Store)
+
+1. **Permissions at runtime**: Request dangerous permissions at point of use, not at app launch.
+2. **Target SDK current**: `targetSdkVersion` within 1 year of latest Android API level.
+3. **64-bit requirement**: All native libraries must provide 64-bit versions.
+4. **Data safety section**: Play Console data safety form must accurately reflect all data collected.

package/areas/software/mobile/rules/security-mobile.md

@@ -0,0 +1,9 @@
+# Rule: Mobile Security
+
+**Priority**: P0 — Mobile security vulnerabilities expose user data directly on device.
+
+1. **No sensitive data in AsyncStorage**: Use `react-native-keychain` (Keychain/Keystore) for tokens, passwords, PII.
+2. **Certificate pinning**: Apps handling financial or health data must implement SSL certificate pinning.
+3. **No sensitive data in logs**: PII scrubbing enabled in logging. Staging-only log levels in production builds.
+4. **Screenshot prevention**: Payment and auth screens must set `FLAG_SECURE` (Android) / `allowScreenshots = false` (iOS).
+5. **Deep link validation**: All deep link handlers must validate URL scheme and path patterns before processing parameters.

package/areas/software/mobile/skills/app-store-prep/SKILL.md

@@ -0,0 +1,27 @@
+# Skill: App Store Submission Preparation
+
+## When to load
+
+When preparing a release build or responding to rejection reasons.
+
+## Pre-Submission Checklist
+
+### Both Platforms
+- [ ] Version code/build number incremented
+- [ ] Release notes written (plain language, user-facing changes)
+- [ ] All new permissions declared with usage descriptions
+- [ ] Deep links tested end-to-end
+- [ ] Crash-free rate > 99.5% in pre-release testing
+- [ ] No debug flags in release build
+
+### iOS Specific
+- [ ] `Info.plist` usage descriptions for all capabilities
+- [ ] Privacy nutrition labels updated in App Store Connect
+- [ ] TestFlight validated on ≥ 5 real devices
+- [ ] Screenshots updated for new features
+
+### Android Specific
+- [ ] `targetSdkVersion` current year's API level
+- [ ] Data safety form updated in Play Console
+- [ ] App Bundle (`.aab`) submitted (not APK)
+- [ ] Internal → Closed → Production promotion flow followed

package/areas/software/mobile/skills/mobile-testing/SKILL.md

@@ -0,0 +1,36 @@
+# Skill: Mobile Testing (Detox)
+
+## When to load
+
+When writing E2E tests for mobile or configuring Detox.
+
+## Detox Test Pattern
+
+```typescript
+describe('Login flow', () => {
+  beforeAll(async () => { await device.launchApp({ newInstance: true }); });
+  beforeEach(async () => { await device.reloadReactNative(); });
+
+  it('should login with valid credentials', async () => {
+    await element(by.id('email-input')).typeText('test@example.com');
+    await element(by.id('password-input')).typeText('password123');
+    await element(by.id('login-button')).tap();
+
+    await waitFor(element(by.id('home-screen')))
+      .toBeVisible()
+      .withTimeout(5000);
+  });
+
+  it('should show error for wrong password', async () => {
+    await element(by.id('email-input')).typeText('test@example.com');
+    await element(by.id('password-input')).typeText('wrongpassword');
+    await element(by.id('login-button')).tap();
+
+    await waitFor(element(by.id('error-message')))
+      .toBeVisible()
+      .withTimeout(3000);
+  });
+});
+```
+
+**Key**: Use `testID` prop on elements for reliable Detox selection. Never rely on text content alone.