@shaykec/app-agent 1.0.8 → 1.0.10

package/.claude/agents/template-selector.md

@@ -1,39 +0,0 @@
----
-name: template-selector
-description: Analyzes user app requirements against CATALOG.md to select the best template. Use when you need to pick a template for a new app. Returns the template name, reasoning, and any hybrid-app recommendations.
-tools: Read, Grep, Glob, LS
-model: haiku
-permissionMode: plan
----
-
-You are a specialised subagent for selecting the best mobile app template. You have deep knowledge of the template catalog and selection criteria.
-
-## Instructions
-
-1. Read `templates/CATALOG.md` thoroughly
-2. Given the user's app description and target platform, evaluate each template:
-   - Score against the "Best-For Keywords" in the decision matrix
-   - Check the "Best match when" criteria for each template
-   - Apply the "NOT a match when" rules to eliminate poor fits
-   - Consider the "Hybrid Apps" table if the app spans categories
-3. If no template is a strong match, follow the "When No Template Fits" guidance — pick the template with the most similar navigation and screen patterns
-
-## Output Format
-
-Return your answer in this exact format:
-
-```
-SELECTED TEMPLATE: {TemplateName}
-CONFIDENCE: high | medium | low
-REASONING: {1-2 sentence explanation}
-BORROW FROM: {other template name, if hybrid} or "none"
-HYBRID NOTES: {what to borrow and why} or "n/a"
-```
-
-## Rules
-
-- Always recommend exactly ONE primary template
-- If confidence is "low", explain what aspects of the user's request don't fit well
-- For hybrid apps, identify which template to START with and what to borrow from the secondary template
-- Do NOT recommend building from scratch — always pick the closest template
-- Consider the platform (iOS vs Android) — some templates have platform-specific presets

package/.claude/skills/module-selector/SKILL.md

@@ -1,81 +0,0 @@
-# Module Selector Skill
-
-Select shared modules based on keyword matching against the user's description.
-
-## When to Use
-
-- Step 0, in parallel with template and design brand selection
-
-## Context You Need
-
-- **User description** — app features
-- **Platform** — `ios` or `android`
-- **Selected template** (if available)
-
-## Instructions
-
-### Step 1 — Read Catalog
-
-Read `templates/shared/MODULES_CATALOG.md`. Note each module's keywords, relevant templates, and dependencies.
-
-### Step 2 — Match by Keywords
-
-For every module: compare "Best-For Keywords" against the user's description. Include if **any keyword matches** or the feature is clearly implied.
-
-**Guidance:** Aim for **5-15 modules**. Don't over-select. Consider implicit needs (shopping → payment, social → sharing).
-
-### Step 3 — Check Dependencies
-
-Verify dependencies are met (Paywall→BiometricAuth, AccountDeletion→ConsentPrivacy, etc.). Add missing dependencies.
-
-### Step 4 — Final List
-
-Produce selected modules with reasoning.
-
-## Report Output
-
-Write to `output/{app-name}/reports/02b-module-selection.md`:
-
-```markdown
-# Module Selection Report
-
-**Step:** 0 (parallel)
-**Skill:** module-selector
-**Timestamp:** {ISO 8601}
-**Result:** PASS
-
-## Selected Modules — {N} total
-
-| Module | Matched Keywords | Reason |
-|--------|-----------------|--------|
-| {name} | {keywords} | {why included} |
-
-## Excluded Modules
-
-| Module | Reason for Exclusion |
-|--------|---------------------|
-
-## Dependencies Added
-
-| Module | Added Because |
-|--------|--------------|
-```
-
-Update `summary.json`:
-
-```json
-{
-  "step": 0,
-  "name": "module-selection",
-  "result": "PASS",
-  "reportFile": "02b-module-selection.md",
-  "modulesSelected": {N}
-}
-```
-
-## Rules
-
-- READ-ONLY — only write report files
-- No auto-include — every module must match via keywords
-- Aim for 5-15 modules
-- Module integration happens later (Steps 4-5), not here

package/.claude/skills/template-selector/SKILL.md

@@ -1,44 +0,0 @@
----
-name: template-selector
-description: Analyzes user app requirements against CATALOG.md to select the best template. Returns the template name, reasoning, confidence level, and hybrid-app recommendations.
-allowed-tools: Read, Grep, Glob, LS
-context: fork
-agent: Explore
----
-
-# Template Selector Skill
-
-Use this skill to select the best mobile app template for the user's requirements.
-
-## When to Use
-
-- At Step 1 of the AppAgent workflow, after prompt validation passes
-- Before cloning any template to output/
-
-## Instructions
-
-### Step 1 — Read the Template Catalog
-
-Read `templates/CATALOG.md`. Understand each template's feature set, "Best-For Keywords", "Best match when" criteria, and "NOT a match when" rules.
-
-### Step 2 — Score Each Template
-
-For each template: score against user description keywords, check match criteria, apply exclusion rules, consider navigation pattern similarity.
-
-### Step 3 — Handle Edge Cases
-
-Check the "Hybrid Apps" table if the app spans categories. Follow "When No Template Fits" guidance if needed.
-
-### Step 4 — Make the Selection
-
-Choose exactly ONE primary template. Determine confidence (high/medium/low).
-
-## Report Output
-
-Write `output/{app-name}/reports/02-template-selection.md` and update `summary.json`.
-
-## Important Rules
-
-- READ-ONLY — only write report files
-- Always recommend exactly ONE primary template
-- Do NOT recommend building from scratch

package/.cursor/agents/template-selector.md

@@ -1,52 +0,0 @@
----
-name: template-selector
-description: Analyzes user app requirements against CATALOG.md to select the best template. Use when you need to pick a template for a new app. Returns the template name, reasoning, and any hybrid-app recommendations.
-tools:
-  - Read
-  - Grep
-  - Glob
-  - LS
-readonly: true
----
-
-# Template Selector
-
-You are a specialised subagent for selecting the best mobile app template. You have deep knowledge of the template catalog and selection criteria.
-
-## Logging Protocol
-
-When you start, print:
-`[SUBAGENT:template-selector] Starting — template selection for "{app description}"`
-
-When you finish, print:
-`[SUBAGENT:template-selector] Completed — selected {TemplateName} (confidence: {high|medium|low})`
-
-## Instructions
-
-1. Read `templates/CATALOG.md` thoroughly
-2. Given the user's app description and target platform, evaluate each template:
-   - Score against the "Best-For Keywords" in the decision matrix
-   - Check the "Best match when" criteria for each template
-   - Apply the "NOT a match when" rules to eliminate poor fits
-   - Consider the "Hybrid Apps" table if the app spans categories
-3. If no template is a strong match, follow the "When No Template Fits" guidance — pick the template with the most similar navigation and screen patterns
-
-## Output Format
-
-Return your answer in this exact format:
-
-```
-SELECTED TEMPLATE: {TemplateName}
-CONFIDENCE: high | medium | low
-REASONING: {1-2 sentence explanation}
-BORROW FROM: {other template name, if hybrid} or "none"
-HYBRID NOTES: {what to borrow and why} or "n/a"
-```
-
-## Rules
-
-- Always recommend exactly ONE primary template
-- If confidence is "low", explain what aspects of the user's request don't fit well
-- For hybrid apps, identify which template to START with and what to borrow from the secondary template
-- Do NOT recommend building from scratch — always pick the closest template
-- Consider the platform (iOS vs Android) — some templates have platform-specific presets

package/.cursor/skills/module-selector/SKILL.md

@@ -1,135 +0,0 @@
-# Module Selector Skill
-
-Select which shared modules to integrate into the user's app based on keyword matching against the user's description.
-
-## When to Use
-
-- At Step 0 of the AppAgent workflow, in parallel with template selection and design brand selection
-- When you need to determine which shared modules to include in the generated app
-
-## Context You Need
-
-- **User description** — what kind of app the user wants to build
-- **Platform** — `ios` or `android`
-- **Selected template** (if available) — helps inform which modules are relevant
-
-## Instructions
-
-### Step 1 — Read the Modules Catalog
-
-Read `templates/shared/MODULES_CATALOG.md` thoroughly. Understand each module's:
-- "Best-For Keywords" in the decision matrix
-- "Relevant Templates" column
-- Module dependencies
-
-### Step 2 — Match Modules by Keywords
-
-For every module in the catalog:
-1. Compare its "Best-For Keywords" against the user's description
-2. Check if the selected template is in the "Relevant Templates" column
-3. If **any keyword matches** OR the feature is clearly implied by the app description → include the module
-
-**Selection guidance:**
-- Aim for **5-15 modules** that genuinely match the app's features
-- Don't over-select — only include modules the app will actually use
-- Don't under-select — if a keyword matches, the module is likely needed
-- Consider implicit needs (e.g., a "shopping app" implies payment, a "social app" implies sharing)
-
-**BaaS module selection (FirebaseProvider, SupabaseProvider, CachedRepository):**
-- Select FirebaseProvider OR SupabaseProvider (not both) when the description mentions: "real data", "users", "auth", "login", "sign up", "accounts", "cloud", "sync", "backend", "database", "multi-device", "server"
-- Default (no BaaS keywords): NO BaaS module. The app uses `localStorage` (Core Data / Room) by default.
-- If SupabaseProvider is selected, also add CachedRepository (Supabase has no built-in offline cache)
-- If FirebaseProvider is selected, do NOT add CachedRepository (Firestore has built-in offline persistence)
-- Prefer Firebase for "Google ecosystem" keywords, Supabase for "PostgreSQL", "open source", "self-hosted" keywords
-- When both would fit equally, prefer Firebase (more mature mobile SDK)
-
-### Step 3 — Check Dependencies
-
-Verify that included modules have their dependencies met:
-- Paywall depends on BiometricAuth (optional)
-- AccountDeletion depends on ConsentPrivacy
-- PushNotifications depends on ConsentPrivacy
-- PaymentMethods depends on Paywall
-- GamificationKit depends on ChartsLibrary
-- NotificationCenter depends on PushNotifications
-- CloudSync depends on NetworkBanner
-- LiveActivities depends on PushNotifications
-- SupabaseProvider depends on CachedRepository (for offline support)
-- FirebaseProvider depends on ErrorHandling (optional), NetworkBanner (optional)
-- SupabaseProvider depends on ErrorHandling (optional), NetworkBanner (optional)
-
-If a dependency is missing, add it.
-
-### Step 4 — Final Module List
-
-Produce the final list of selected modules with reasoning for each.
-
-## Report Output
-
-Write the report to `output/{app-name}/reports/02b-module-selection.md`:
-
-```markdown
-# Module Selection Report
-
-**Step:** 0 (parallel)
-**Skill:** module-selector
-**Timestamp:** {ISO 8601}
-**Result:** PASS
-
-## Selected Modules — {N} total
-
-| Module | Matched Keywords | Reason |
-|--------|-----------------|--------|
-| {name} | {keywords} | {why included} |
-...
-
-## Excluded Modules
-
-| Module | Reason for Exclusion |
-|--------|---------------------|
-...
-
-## Dependencies Added
-
-| Module | Added Because |
-|--------|--------------|
-| {name} | Required by {other module} |
-...
-```
-
-Update `output/{app-name}/reports/summary.json` — append this step entry:
-
-```json
-{
-  "step": 0,
-  "name": "module-selection",
-  "result": "PASS",
-  "reportFile": "02b-module-selection.md",
-  "modulesSelected": {N}
-}
-```
-
-## Important Rules
-
-- This skill is READ-ONLY — do NOT create, edit, or delete any app source files
-- The ONLY files you write are the report files in `reports/`
-- No modules are auto-included — every module must earn its place via keyword matching (exception: MotionPreferences is auto-included when any animation/sensory module is selected)
-- Aim for 5-15 modules — be selective, not exhaustive
-- Module integration happens later during customization (Steps 4-5) — this skill only produces the selection list
-
-### Animation & Sensory Module Selection Heuristics
-
-When the user description contains words like **"stunning", "beautiful", "premium feel", "polished", "delightful", "smooth", "animated"**, consider these signal-word matches:
-
-| Signal Word | Consider Modules |
-|---|---|
-| stunning, beautiful, premium, polished | MicroInteractions, AnimatedTransitions, CelebrationEffects |
-| haptic, tactile, vibration, feedback | HapticEngine |
-| sound, audio, click sound, chime | AudioFeedback |
-| parallax, scroll effect, header animation | ScrollEffects |
-| confetti, celebration, achievement | CelebrationEffects |
-| onboarding, walkthrough, tutorial | AnimatedOnboarding |
-| transitions, hero, card flip, animated navigation | AnimatedTransitions |
-| micro-animations, bounce, press, stagger | MicroInteractions |
-
-**Auto-include rule:** When ANY of HapticEngine, AudioFeedback, ScrollEffects, CelebrationEffects, MicroInteractions, AnimatedTransitions, or AnimatedOnboarding is selected, **MotionPreferences is automatically added** (it provides the accessibility foundation — reduce motion support).

package/.cursor/skills/template-selector/SKILL.md

@@ -1,123 +0,0 @@
----
-name: template-selector
-description: Analyzes user app requirements against CATALOG.md to select the best template. Returns the template name, reasoning, confidence level, and any hybrid-app recommendations.
----
-
-# Template Selector Skill
-
-Use this skill to select the best mobile app template for the user's requirements.
-
-## When to Use
-
-- At Step 1 of the AppAgent workflow, after prompt validation passes
-- When you need to pick a starting template from the catalog
-- Before cloning any template to `output/`
-
-## Context You Need
-
-- **User description** — what kind of app the user wants to build
-- **Platform** — `ios`, `android`, or `react-native`
-- **Sanitized description** — from the prompt-validator skill (if available)
-
-## Instructions
-
-### Step 1 — Read the Template Catalog
-
-Read `templates/CATALOG.md` thoroughly. Understand each template's:
-- Feature set and architecture
-- "Best-For Keywords" in the decision matrix
-- "Best match when" criteria
-- "NOT a match when" exclusion rules
-
-### Step 2 — Score Each Template
-
-For each template in the catalog:
-1. Score it against the user's description using the "Best-For Keywords"
-2. Check the "Best match when" criteria — how many match?
-3. Apply the "NOT a match when" rules — does any exclusion trigger?
-4. Consider navigation pattern similarity (tabs, lists, detail screens)
-
-### Step 3 — Handle Edge Cases
-
-- If the app spans multiple categories, check the "Hybrid Apps" table in the catalog
-- If no template is a strong match, follow the "When No Template Fits" guidance — pick the template with the most similar navigation and screen patterns
-- Consider the platform (iOS vs Android vs React Native) — all 16 templates are available on all three platforms. The same template names exist under `templates/ios/`, `templates/android/`, and `templates/react-native/`
-
-### Step 4 — Make the Selection
-
-Choose exactly ONE primary template. Determine confidence:
-- **high** — multiple criteria match, clear winner
-- **medium** — good fit but some aspects don't align perfectly
-- **low** — no great match, picking the closest option
-
-If hybrid is needed, identify what to borrow from a secondary template.
-
-## Report Output
-
-Write the report to `output/{app-name}/reports/02-template-selection.md`:
-
-```markdown
-# Template Selection Report
-
-**Step:** 1
-**Skill:** template-selector
-**Timestamp:** {ISO 8601}
-**Result:** PASS
-
-## Selection
-
-**Selected Template:** {TemplateName}
-**Confidence:** high | medium | low
-
-## Reasoning
-
-{2-3 sentences explaining why this template was chosen}
-
-## Scoring
-
-| Template | Score | Match Criteria | Exclusions |
-|----------|-------|---------------|------------|
-| {name}   | {/10} | {matched}     | {any}      |
-
-## Hybrid Recommendation
-
-**Borrow From:** {other template name} or "none"
-**Hybrid Notes:** {what to borrow and why} or "n/a"
-```
-
-Update `output/{app-name}/reports/summary.json` — read the file, append this step.
-
-**Timing:** Record the current timestamp when you begin this skill. When writing the step entry, set `"startedAt"` to that timestamp (ISO 8601) and `"durationSeconds"` to the elapsed seconds.
-
-```json
-{
-  "step": 1,
-  "name": "template-selection",
-  "startedAt": "{ISO 8601 timestamp}",
-  "durationSeconds": 0,
-  "result": "PASS",
-  "reportFile": "02-template-selection.md",
-  "template": "{TemplateName}",
-  "confidence": "high|medium|low",
-  "borrowFrom": "{other template or null}"
-}
-```
-
-Also update the top-level `"template"` field in summary.json.
-
-## Shared Modules
-
-After selecting a template, note that **shared modules** from `templates/shared/MODULES_CATALOG.md` will be integrated separately by the `module-selector` skill. The template selection is independent of module selection — templates provide the app skeleton, modules add cross-cutting features (consent, paywall, biometric auth, charts, etc.).
-
-If the user's description mentions features that are covered by shared modules rather than the template itself (e.g., "with subscription support", "biometric login", "push notifications"), do NOT let those features influence template selection — they will be handled by module integration.
-
-## Important Rules
-
-- This skill is READ-ONLY — do NOT create, edit, or delete any app source files during this step
-- The ONLY files you write are the report files in `reports/`
-- Always recommend exactly ONE primary template
-- If confidence is "low", explain what aspects don't fit well
-- Do NOT recommend building from scratch — always pick the closest template
-- Consider the platform when relevant — all templates are available on iOS, Android, and React Native
-- For React Native, templates use TypeScript + React Navigation + custom hooks (MVVM-hook pattern)
-- Features covered by shared modules (consent, paywall, push notifications, etc.) should NOT affect template scoring — they are integrated separately