mobile-ai-agents 1.0.31 → 1.0.33

package/cli/index.js

@@ -245,6 +245,10 @@ const PLATFORM_SKILLS = {
 // Workflows are always installed regardless of platform selection
 const ALL_WORKFLOWS = Object.keys(WORKFLOWS);
 
+function workflowCommandName(name) {
+  return (AGENTS[name] || SKILLS[name]) ? `${name}-workflow` : name;
+}
+
 const PRIMARY_MEMORY_DIR = '.mobile-ai-agents';
 const LEGACY_MEMORY_DIR = '.mobile-agency';
 const MEMORY_DIR = fs.existsSync(path.join(process.cwd(), LEGACY_MEMORY_DIR)) &&
@@ -881,9 +885,10 @@ async function installForClaude(platforms) {
   await Promise.all(ALL_WORKFLOWS.map(async (name) => {
     const meta = WORKFLOWS[name];
     if (!meta) return;
-    const dest = path.join(CLAUDE_COMMANDS_DIR, `${name}.md`);
+    const commandName = workflowCommandName(name);
+    const dest = path.join(CLAUDE_COMMANDS_DIR, `${commandName}.md`);
     await downloadFile(meta.file, [dest]);
-    ok(name);
+    ok(commandName === name ? name : `${name} → ${commandName}`);
   }));
 
   console.log('');
@@ -923,9 +928,10 @@ async function installForCursor(platforms) {
   await Promise.all(ALL_WORKFLOWS.map(async (name) => {
     const meta = WORKFLOWS[name];
     if (!meta) return;
-    const dest = path.join(rulesDir, `${name}.mdc`);
+    const commandName = workflowCommandName(name);
+    const dest = path.join(rulesDir, `${commandName}.mdc`);
     await downloadFile(meta.file, [dest]);
-    ok(name);
+    ok(commandName === name ? name : `${name} → ${commandName}`);
   }));
 
   console.log('');
@@ -1181,10 +1187,11 @@ async function cmdAdd(args) {
       process.exit(1);
     }
     ensureDir(CLAUDE_COMMANDS_DIR);
-    const dest = path.join(CLAUDE_COMMANDS_DIR, `${name}.md`);
+    const commandName = workflowCommandName(name);
+    const dest = path.join(CLAUDE_COMMANDS_DIR, `${commandName}.md`);
     log(`Fetching ${bold(name)} workflow...`);
     await downloadFile(meta.file, [dest]);
-    ok(`${name} → ${dim(dest)}`);
+    ok(`${commandName} → ${dim(dest)}`);
   } else {
     err(`Unknown type: ${type}. Use 'agent', 'skill', or 'workflow'.`);
     process.exit(1);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "mobile-ai-agents",
-  "version": "1.0.31",
+  "version": "1.0.33",
   "description": "AI agents, skills, and Loop Engineering workflows for building, testing, auditing, and releasing mobile apps.",
   "bin": {
     "mobile-ai-agents": "cli/index.js",

package/skills/cross-platform/mobile-mcp-qa.md

@@ -10,7 +10,7 @@
 
 Use Mobile MCP to run AI-assisted QA on a real device, emulator, or simulator. This skill turns a feature flow into a repeatable device test plan using screenshots, accessibility snapshots, element inspection, taps, typing, swipes, app install, app launch, and device orientation checks.
 
-Mobile MCP is best used after implementation, during APPFORGE Stage 7 Full QA, or before store submission.
+Mobile MCP is best used after implementation, during APPFORGE Stage 7 Full QA, after `/mobile-app-design` reskins, or before store submission.
 
 ---
 
@@ -61,6 +61,30 @@ EDGE_CASES:
 <offline, invalid input, rotation, restart, permissions, api errors>
 ```
 
+### Reskin QA Input
+
+Use this format when verifying a `/mobile-app-design` redesign or reskin:
+
+```text
+COMMAND: /mobile-mcp-qa
+MODE: RESKIN_QA
+PLATFORM: <Android | iOS | Flutter | React Native>
+APP_ID: <Android package name or iOS bundle id>
+BUILD_PATH: <optional apk/ipa/app path>
+DEVICE: <optional target device name>
+SUPPORTED_THEMES: <light | dark | light,dark | custom themes>
+SCREEN_INVENTORY:
+| Screen/State | Decision | Expected Change | Route/Tab |
+|---|---|---|---|
+| <screen + state> | REDESIGN | <layout/hierarchy/state change> | <route/tab> |
+BASELINE_EVIDENCE:
+<before screenshots, screenshot paths, or "capture before from current build">
+EXPECTED_REDESIGN:
+<approved reskin plan, navigation changes, theme changes, and state coverage>
+REGRESSION_RISKS:
+<tab reorder, renamed copy, deep links, dark mode, keyboard, safe area, analytics, etc.>
+```
+
 ---
 
 ## Skill Prompt
@@ -68,6 +92,8 @@ EDGE_CASES:
 ```text
 Run a Mobile MCP QA pass for the provided mobile app flow.
 
+If MODE is RESKIN_QA, run the Reskin QA flow instead of ordinary flow QA.
+
 STEP 1 — VERIFY SETUP
 - List available devices.
 - Select the requested device, or choose the first available emulator/simulator.
@@ -101,7 +127,79 @@ Check:
 - App restart preserves required state
 - Offline/API error behavior is user-safe
 
-STEP 5 — REPORT
+RESKIN QA FLOW
+Use this flow when MODE is RESKIN_QA or when the user provides a `/mobile-app-design` screen inventory.
+
+STEP R1 — VERIFY RESKIN INPUTS
+- Read SCREEN_INVENTORY and EXPECTED_REDESIGN.
+- Preserve each inventory decision exactly: REDESIGN, RESTYLE, or LEAVE.
+- Confirm SUPPORTED_THEMES. If the app supports light and dark, both are required.
+- If baseline screenshots are missing and the current build is already the after build, mark before evidence as missing instead of inventing it.
+
+STEP R2 — CAPTURE OR REGISTER BASELINE
+- For each inventory row, attach the provided before screenshot or capture a before screenshot if the baseline build is available.
+- Name evidence predictably: before-<theme>-<screen>-<state>.
+- A screen/state without before evidence is still testable after the edit, but its before/after comparison status is UNVERIFIED.
+
+STEP R3 — CAPTURE AFTER STATE
+- Launch the after build.
+- Visit every screen/state in SCREEN_INVENTORY.
+- Capture after screenshots for every supported theme.
+- For loading, empty, error, offline, permission-denied, and success states, use controlled test data, network toggles, permissions, or documented setup steps when available.
+- Name evidence predictably: after-<theme>-<screen>-<state>.
+
+STEP R4 — VERIFY STRUCTURAL CHANGE
+For each inventory row:
+- REDESIGN must show layout, hierarchy, grouping, density, information-priority, or state-layout changes. Token-only changes are FAIL.
+- RESTYLE may show token/component updates only, but must have a justification.
+- LEAVE should remain intentionally unchanged except for unavoidable global shell or token updates.
+- Mark missing before or after screenshots as UNVERIFIED.
+
+STEP R5 — VERIFY REGRESSIONS
+Check:
+- clipped or overlapping text
+- safe areas, status bar, navigation bar, and notches
+- keyboard avoidance
+- minimum 44pt/48dp touch targets
+- light/dark contrast and invisible text risk
+- tab order, selected state, route names, deep links, and back behavior
+- renamed screen/tab copy across labels, empty states, prompts, and accessibility text
+- loading, empty, error, offline, disabled, permission-denied, and success states
+- orientation when the app supports it
+
+STEP R6 — REPORT RESKIN QA
+Return:
+MOBILE MCP RESKIN QA REPORT
+===========================
+Platform:
+Device:
+App:
+Themes:
+Result: PASS | FAIL | PARTIAL | BLOCKED
+
+Screen Evidence:
+| Screen/State | Decision | Theme | Before | After | Result |
+|---|---|---|---|---|---|
+
+Structural Verification:
+| Screen/State | Decision | Expected Change | Observed Change | Result |
+|---|---|---|---|---|
+
+Regression Checks:
+| Check | Screen/State | Result | Evidence |
+|---|---|---|---|
+
+Issues:
+| Severity | Screen/State | Issue | Evidence | Fix |
+|---|---|---|---|---|
+
+Evidence For PRD Verification:
+- <compact screenshot list and report summary that can be pasted into /prd-verification>
+
+Recommended Next Action:
+<single concrete fix or next test>
+
+STEP 5 — REPORT ORDINARY FLOW QA
 Return:
 MOBILE MCP QA REPORT
 ====================
@@ -129,6 +227,81 @@ Recommended Next Action:
 <single concrete fix or next test>
 ```
 
+### Reskin QA Example
+
+#### Input
+
+```text
+COMMAND: /mobile-mcp-qa
+MODE: RESKIN_QA
+PLATFORM: React Native
+APP_ID: com.example.habits
+SUPPORTED_THEMES: light,dark
+SCREEN_INVENTORY:
+| Screen/State | Decision | Expected Change | Route/Tab |
+|---|---|---|---|
+| Today/populated | REDESIGN | grouped morning/afternoon/evening sections | Today |
+| Today/empty | REDESIGN | coaching empty state with primary action | Today |
+| Insights/populated | REDESIGN | KPI strip + weekly chart + compact history | Insights |
+| Settings/default | RESTYLE | tokenized surfaces and clearer typography | Settings |
+BASELINE_EVIDENCE:
+before-light-today-populated.png, before-dark-today-populated.png,
+before-light-insights-populated.png, before-dark-insights-populated.png
+EXPECTED_REDESIGN:
+Tabs reordered to Today, Insights, Coach, Settings. Today and Insights require structural layout changes. Settings is restyle only.
+REGRESSION_RISKS:
+dark mode contrast, renamed Strategy copy, tab selected state, safe areas
+```
+
+#### Output
+
+```text
+MOBILE MCP RESKIN QA REPORT
+===========================
+Platform: React Native
+Device: iPhone 15 Simulator
+App: com.example.habits
+Themes: light, dark
+Result: FAIL
+
+Screen Evidence:
+| Screen/State | Decision | Theme | Before | After | Result |
+|---|---|---|---|---|---|
+| Today/populated | REDESIGN | light | before-light-today | after-light-today | PASS |
+| Today/populated | REDESIGN | dark | before-dark-today | after-dark-today | PASS |
+| Insights/populated | REDESIGN | light | before-light-insights | after-light-insights | PASS |
+| Insights/populated | REDESIGN | dark | before-dark-insights | after-dark-insights | FAIL |
+| Settings/default | RESTYLE | dark | missing | after-dark-settings | UNVERIFIED |
+
+Structural Verification:
+| Screen/State | Decision | Expected Change | Observed Change | Result |
+|---|---|---|---|---|
+| Today/populated | REDESIGN | grouped sections | sections visible | PASS |
+| Insights/populated | REDESIGN | KPI + chart + history | chart clipped in dark | FAIL |
+| Settings/default | RESTYLE | token updates | no before evidence | UNVERIFIED |
+
+Regression Checks:
+| Check | Screen/State | Result | Evidence |
+|---|---|---|---|
+| Dark contrast | Insights | FAIL | chart label unreadable |
+| Tab selected state | All tabs | PASS | selected indicator moves |
+| Renamed copy | Today | PASS | no stale Strategy copy |
+
+Issues:
+| Severity | Screen/State | Issue | Evidence | Fix |
+|---|---|---|---|---|
+| WARNING | Insights/dark | Chart label has low contrast | after-dark-insights | Use onSurface token |
+| INFO | Settings/default | Missing baseline | after-dark-settings | Capture before image next run |
+
+Evidence For PRD Verification:
+- Today populated: light/dark before-after PASS.
+- Insights dark: FAIL due chart contrast.
+- Settings: UNVERIFIED because baseline missing.
+
+Recommended Next Action:
+Fix Insights dark chart label contrast and rerun Reskin QA for Insights and Settings.
+```
+
 ---
 
 ## Example

package/skills/cross-platform/prd-verification.md

@@ -27,6 +27,10 @@ IMPLEMENTATION:
 <changed files, relevant source code, repo tree, or diff>
 EVIDENCE:
 <test output, build output, screenshots, Mobile MCP QA report, logs, accessibility report, security report>
+RESKIN_PLAN:
+<optional /mobile-app-design plan with REDESIGN, RESTYLE, and LEAVE screen inventory rows>
+RESKIN_QA:
+<optional /mobile-mcp-qa Reskin QA report, before/after screenshots, state coverage, and theme evidence>
 KNOWN_LIMITATIONS:
 <optional explicit constraints, skipped checks, unavailable device, unavailable backend>
 ```
@@ -45,11 +49,13 @@ Read these inputs in order:
 1. PRD.md or product requirements
 2. TASKS.md acceptance criteria
 3. DESIGN.md or design plan
-4. DEPENDENCIES.md and ROADMAP.md when provided
-5. MOBILE_MEMORY.md or project context when provided
-6. Relevant source code, diff, and file tree
-7. Test/build output
-8. Screenshots, videos, accessibility reports, security reports, or Mobile MCP QA reports
+4. /mobile-app-design reskin plan and screen inventory when provided
+5. DEPENDENCIES.md and ROADMAP.md when provided
+6. MOBILE_MEMORY.md or project context when provided
+7. Relevant source code, diff, and file tree
+8. Test/build output
+9. Screenshots, videos, accessibility reports, security reports, or Mobile MCP QA reports
+10. /mobile-mcp-qa Reskin QA report when provided
 
 Verification rules:
 
@@ -61,6 +67,10 @@ Verification rules:
 - Separate confirmed gaps from assumptions.
 - Do not expand scope beyond the approved PRD unless it creates release risk.
 - Do not mark release-ready if critical requirements, security blockers, crash risks, or required tests are missing.
+- For mobile reskins, compile/build/test success is not UI proof by itself.
+- For mobile reskins, every required screen inventory row needs screenshot, video, or Mobile MCP evidence.
+- Mark missing required reskin evidence as UNVERIFIED, or PARTIAL only when some states/themes are proven.
+- Reject shallow rethemes: a REDESIGN screen fails when it only inherits token, color, font, spacing, or theme changes.
 
 Check these areas:
 
@@ -81,17 +91,28 @@ Check these areas:
 - Layout, hierarchy, content, states, responsiveness, and accessibility evidence.
 - Screenshot or Mobile MCP evidence when available.
 
-4. TEST AND DEVICE EVIDENCE
+4. MOBILE RESKIN VERIFICATION
+Use this section when RESKIN_PLAN is provided or the scope mentions /mobile-app-design, reskin, redesign, tab reorder, navigation rename, visual refresh, or restyle.
+- Read every screen inventory row and preserve its decision: REDESIGN, RESTYLE, or LEAVE.
+- REDESIGN must show structural change: layout, hierarchy, grouping, density, information architecture, state layout, tab order, or interaction model.
+- RESTYLE must include justification and must not be counted as structurally redesigned.
+- LEAVE must be intentionally out of scope and should not be reported as a missed redesign unless the PRD required it.
+- Compare before/after screenshots or Mobile MCP evidence for each required screen, state, orientation, and light/dark theme listed in the plan.
+- If navigation changed, verify routes, deep links, selected tab state, back behavior, accessibility labels, tests, snapshots, and docs.
+- If tabs or screens were renamed, verify user-facing copy changed consistently in UI, tests, screenshots, and docs.
+- Use per-screen status values: PASS, FAIL, PARTIAL, or UNVERIFIED.
+
+5. TEST AND DEVICE EVIDENCE
 - Unit, integration, UI, golden/snapshot, E2E, and manual QA evidence.
 - Build/install/launch proof.
 - Device, emulator, simulator, or Mobile MCP proof when available.
 
-5. SECURITY AND RELEASE BLOCKERS
+6. SECURITY AND RELEASE BLOCKERS
 - Security audit findings that affect release.
 - Sensitive data, auth, storage, network, permissions, deep links, WebViews, logging, and payment/subscription behavior when relevant.
 - Performance blockers that affect launch readiness.
 
-6. CONTEXT CONTINUITY
+7. CONTEXT CONTINUITY
 - MOBILE_MEMORY.md or project context reflects the current state.
 - Remaining gaps and next action are captured for future sessions.
 
@@ -127,6 +148,10 @@ UI Match:
 | Screen/State | Source | Status | Evidence |
 |---|---|---|---|
 
+Mobile Reskin Verification:
+| Screen/State | Decision | Evidence | Status | Reason |
+|---|---|---|---|---|
+
 Test And Device Evidence:
 | Check | Status | Evidence |
 |---|---|---|
@@ -157,7 +182,7 @@ Test Gaps:
 - <gap or "None">
 
 Release Readiness:
-PASS only if all required PRD items and acceptance criteria are PASS, no critical UI/security/test gaps remain, and unknowns are documented or risk-accepted.
+PASS only if all required PRD items and acceptance criteria are PASS, no critical UI/security/test gaps remain, required reskin evidence is PASS or risk-accepted, and unknowns are documented or risk-accepted.
 
 Next Action:
 1. <single highest priority action>
@@ -299,6 +324,54 @@ Next Action:
 
 ---
 
+## Mobile Reskin Example
+
+Use this guidance when `/mobile-app-design` produced a reskin plan and `/mobile-mcp-qa` produced device evidence.
+
+```text
+RESKIN_PLAN:
+- Home: REDESIGN. Replace feed cards with grouped Today, Progress, and Next Action sections.
+- Profile: RESTYLE. Keep structure, update typography and spacing only.
+- Billing: LEAVE. Out of scope for this release.
+
+RESKIN_QA:
+- Mobile MCP Reskin QA has before/after screenshots for Home light and dark.
+- Profile screenshot exists only for light theme.
+- No Billing screenshot because it is marked LEAVE.
+```
+
+Expected verification behavior:
+
+```text
+Mobile Reskin Verification:
+| Screen/State | Decision | Evidence | Status | Reason |
+|---|---|---|---|---|
+| Home light/dark | REDESIGN | MCP screenshots | PASS | Structure changed |
+| Profile light | RESTYLE | Screenshot | PARTIAL | Dark missing |
+| Billing | LEAVE | Plan row | PASS | Out of scope |
+
+Verification Details:
+### UI-001 — Home redesign is proven
+- Source: /mobile-app-design RESKIN_PLAN.
+- Evidence: /mobile-mcp-qa before/after screenshots show new grouped sections.
+- Status: PASS.
+- Confirmed gap: None.
+- Assumption: None.
+- Required fix: None.
+
+### UI-002 — Profile restyle has incomplete evidence
+- Source: /mobile-app-design RESKIN_PLAN.
+- Evidence: Only light theme screenshot was provided.
+- Status: PARTIAL.
+- Confirmed gap: Dark theme evidence is missing.
+- Assumption: Profile was intentionally restyled, not redesigned.
+- Required fix: Capture Profile dark theme screenshot or risk-accept the gap.
+```
+
+If Home only changed colors, fonts, or tokens, mark it FAIL because a REDESIGN requires structural proof.
+
+---
+
 ## Composition Example
 
 ```text

package/workflows/mobile-mcp-qa.md

@@ -1,6 +1,7 @@
 # Workflow — Mobile MCP QA
 
 **Type:** Device automation QA  
+**Slash Command:** `/mobile-mcp-qa-workflow` when installed alongside the `/mobile-mcp-qa` skill
 **Agents Used:** APPFORGE, AXIOM / SWIFT / DART / BRIDGE, CRASHER, PERF, Mobile Memory
 **Skills Used:** /mobile-mcp-qa, /accessibility-audit, /perf-audit, /mobile-memory-save