agy-superpowers 5.1.1 → 5.1.3

package/template/agent/skills/frontend-design/reference/typography.md

@@ -0,0 +1,124 @@
+# Typography
+
+## Classic Typography Principles
+
+### Vertical Rhythm
+Your line-height should be the base unit for ALL vertical spacing. If body text has `line-height: 1.5` on `16px` type (= 24px), spacing values should be multiples of 24px. This creates subconscious harmony — text and space share a mathematical foundation.
+
+### Modular Scale & Hierarchy
+The common mistake: too many font sizes that are too close together (14px, 15px, 16px, 18px...). This creates muddy hierarchy.
+
+**Use fewer sizes with more contrast.** A 5-size system covers most needs:
+
+| Role | Typical Ratio | Use Case |
+|------|---------------|----------|
+| xs | 0.75rem | Captions, legal |
+| sm | 0.875rem | Secondary UI, metadata |
+| base | 1rem | Body text |
+| lg | 1.25–1.5rem | Subheadings, lead text |
+| xl+ | 2–4rem | Headlines, hero text |
+
+Popular ratios: 1.25 (major third), 1.333 (perfect fourth), 1.5 (perfect fifth). Pick one and commit.
+
+### Readability & Measure
+Use `ch` units for character-based measure (`max-width: 65ch`). Line-height scales inversely with line length — narrow columns need tighter leading, wide columns need more.
+
+**Non-obvious**: Increase line-height for light text on dark backgrounds. The perceived weight is lighter, so text needs more breathing room. Add 0.05–0.1 to your normal line-height.
+
+---
+
+## Font Selection & Pairing
+
+### Choosing Distinctive Fonts
+**Avoid the invisible defaults**: Inter, Roboto, Open Sans, Lato, Montserrat. These are everywhere, making your design feel generic. They're fine for documentation or tools where personality isn't the goal — but if you want distinctive design, look elsewhere.
+
+**Better Google Fonts alternatives**:
+- Instead of Inter → **Instrument Sans**, **Plus Jakarta Sans**, **Outfit**
+- Instead of Roboto → **Onest**, **Figtree**, **Urbanist**
+- Instead of Open Sans → **Source Sans 3**, **Nunito Sans**, **DM Sans**
+- For editorial/premium feel → **Fraunces**, **Newsreader**, **Lora**
+
+**System fonts are underrated**: `-apple-system, BlinkMacSystemFont, "Segoe UI", system-ui` looks native, loads instantly, and is highly readable. Consider for apps where performance > personality.
+
+### Pairing Principles
+**The non-obvious truth**: You often don't need a second font. One well-chosen font family in multiple weights creates cleaner hierarchy than two competing typefaces.
+
+When pairing, contrast on multiple axes:
+- Serif + Sans (structure contrast)
+- Geometric + Humanist (personality contrast)
+- Condensed display + Wide body (proportion contrast)
+
+**Never pair fonts that are similar but not identical** (e.g., two geometric sans-serifs). They create visual tension without clear hierarchy.
+
+### Web Font Loading
+The layout shift problem: fonts load late, text reflows, users see content jump. The fix:
+
+```css
+/* 1. Use font-display: swap for visibility */
+@font-face {
+  font-family: 'CustomFont';
+  src: url('font.woff2') format('woff2');
+  font-display: swap;
+}
+
+/* 2. Match fallback metrics to minimize shift */
+@font-face {
+  font-family: 'CustomFont-Fallback';
+  src: local('Arial');
+  size-adjust: 105%;
+  ascent-override: 90%;
+  descent-override: 20%;
+  line-gap-override: 10%;
+}
+
+body {
+  font-family: 'CustomFont', 'CustomFont-Fallback', sans-serif;
+}
+```
+
+---
+
+## Modern Web Typography
+
+### Fluid Type
+Fluid typography via `clamp(min, preferred, max)` scales text smoothly with the viewport.
+
+**Use fluid type for**: Headings and display text on marketing/content pages.
+**Use fixed `rem` scales for**: App UIs, dashboards, data-dense interfaces. Body text should also be fixed.
+
+### OpenType Features
+Use these for polish — most developers don't know they exist:
+
+```css
+/* Tabular numbers for data alignment */
+.data-table { font-variant-numeric: tabular-nums; }
+
+/* Proper fractions */
+.recipe-amount { font-variant-numeric: diagonal-fractions; }
+
+/* Small caps for abbreviations */
+abbr { font-variant-caps: all-small-caps; }
+
+/* Disable ligatures in code */
+code { font-variant-ligatures: none; }
+
+/* Enable kerning */
+body { font-kerning: normal; }
+```
+
+---
+
+## Typography System Architecture
+
+Name tokens semantically (`--text-body`, `--text-heading`), not by value (`--font-size-16`). Include font stacks, size scale, weights, line-heights, and letter-spacing in your token system.
+
+## Accessibility
+
+- **Never disable zoom**: `user-scalable=no` breaks accessibility
+- **Use rem/em for font sizes**: Respects user browser settings. Never `px` for body text
+- **Minimum 16px body text**: Smaller strains eyes and fails WCAG on mobile
+- **Adequate touch targets**: Text links need padding creating 44px+ tap targets
+
+---
+
+**Avoid**: More than 2–3 font families per project. Skipping fallback font definitions. Ignoring font loading performance (FOUT/FOIT). Using decorative fonts for body text.

package/template/agent/skills/frontend-design/reference/ux-writing.md

@@ -0,0 +1,127 @@
+# UX Writing
+
+## The Button Label Problem
+
+**Never use "OK", "Submit", or "Yes/No".** These are lazy and ambiguous. Use specific verb + object patterns:
+
+| Bad | Good | Why |
+|-----|------|-----|
+| OK | Save changes | Says what will happen |
+| Submit | Create account | Outcome-focused |
+| Yes | Delete message | Confirms the action |
+| Cancel | Keep editing | Clarifies what "cancel" means |
+| Click here | Download PDF | Describes the destination |
+
+**For destructive actions**, name the destruction:
+- "Delete" not "Remove" (delete is permanent, remove implies recoverable)
+- "Delete 5 items" not "Delete selected" (show the count)
+
+---
+
+## Error Messages: The Formula
+
+Every error should answer: (1) What happened? (2) Why? (3) How to fix it?
+
+- ✅ `"Email address isn't valid. Please include an @ symbol."`
+- ❌ `"Invalid input"`
+
+### Templates per Situation
+
+| Situation | Template |
+|-----------|----------|
+| **Format error** | "[Field] needs to be [format]. Example: [example]" |
+| **Missing required** | "Please enter [what's missing]" |
+| **Permission denied** | "You don't have access to [thing]. [What to do instead]" |
+| **Network error** | "We couldn't reach [thing]. Check your connection and [action]." |
+| **Server error** | "Something went wrong on our end. We're looking into it. [Alternative action]" |
+
+### Don't Blame the User
+Reframe errors:
+- ✅ `"Please enter a date in MM/DD/YYYY format"`
+- ❌ `"You entered an invalid date"`
+
+---
+
+## Empty States Are Opportunities
+
+Empty states are onboarding moments: (1) Acknowledge briefly, (2) Explain the value, (3) Provide a clear action.
+
+- ✅ "No projects yet. Create your first one to get started."
+- ❌ "No items"
+
+---
+
+## Voice vs Tone
+
+**Voice** is your brand's personality — consistent everywhere.
+**Tone** adapts to the moment:
+
+| Moment | Tone Shift |
+|--------|------------|
+| Success | Celebratory, brief: "Done! Your changes are live." |
+| Error | Empathetic, helpful: "That didn't work. Here's what to try..." |
+| Loading | Reassuring: "Saving your work..." |
+| Destructive confirm | Serious, clear: "Delete this project? This can't be undone." |
+
+**Never use humor for errors.** Users are already frustrated. Be helpful, not cute.
+
+---
+
+## Writing for Accessibility
+
+- **Link text** must have standalone meaning — "View pricing plans" not "Click here"
+- **Alt text** describes information, not the image — "Revenue increased 40% in Q4" not "Chart"
+- Use `alt=""` for decorative images
+- **Icon buttons** need `aria-label`
+
+---
+
+## Writing for Translation
+
+### Plan for Expansion
+
+| Language | Expansion |
+|----------|-----------|
+| German | +30% |
+| French | +20% |
+| Finnish | +30–40% |
+| Chinese | −30% (fewer chars, same width) |
+
+### Translation-Friendly Patterns
+- Keep numbers separate ("New messages: 3" not "You have 3 new messages")
+- Use full sentences as single strings (word order varies by language)
+- Avoid abbreviations ("5 minutes ago" not "5 mins ago")
+- Give translators context about where strings appear
+
+---
+
+## Consistency: The Terminology Problem
+
+Pick one term and stick with it:
+
+| Inconsistent | Consistent |
+|--------------|------------|
+| Delete / Remove / Trash | Delete |
+| Settings / Preferences / Options | Settings |
+| Sign in / Log in / Enter | Sign in |
+| Create / Add / New | Create |
+
+Build a terminology glossary and enforce it. Variety creates confusion.
+
+---
+
+## Avoid Redundant Copy
+
+If the heading explains it, the intro is redundant. If the button is clear, don't explain it again. Say it once, say it well.
+
+## Loading States
+
+Be specific: "Saving your draft..." not "Loading...". For long waits, set expectations ("This usually takes 30 seconds") or show progress.
+
+## Confirmation Dialogs: Use Sparingly
+
+Most confirmation dialogs are design failures — **consider undo instead**. When you must confirm: name the action, explain consequences, use specific button labels ("Delete project" / "Keep project", not "Yes" / "No").
+
+---
+
+**Avoid**: Jargon without explanation. Blaming users ("Invalid input" → "Please include @"). Vague errors. Varying terminology for variety. Humor for error states.

package/template/agent/skills/mobile-uiux-promax/SKILL.md

@@ -0,0 +1,139 @@
+---
+name: mobile-uiux-promax
+description: Use when designing or building mobile app UI for iOS, Android, React Native, Flutter, SwiftUI, or Jetpack Compose
+---
+
+# Mobile UI/UX Pro Max
+
+Data-grounded mobile design intelligence. Every design decision is backed by platform-authoritative data from Apple HIG, Material Design 3, and stack-specific best practices.
+
+## When to Activate
+
+Activate this skill when the request involves:
+- Designing any mobile screen, flow, or component
+- Reviewing mobile UI for platform-appropriateness
+- Choosing between navigation patterns for mobile apps
+- Implementing gesture-driven or haptic-rich interactions
+- Advising on iOS vs Android design conventions
+- Building onboarding flows or paywall timing
+- Animation and motion design for mobile
+
+## Workflow
+
+Run the 4-step search sequence from: `.agent/workflows/mobile-uiux-promax.md`
+
+**Read the workflow file before responding.** It contains the exact search commands to run.
+
+## Core Design Principles (Memorize These)
+
+### 1. Platform-First, Not Platform-Only
+- Follow platform conventions by default
+- Deviate only when there's clear UX benefit to users
+- Cross-platform apps must feel native on each platform, not identical
+- iOS users expect swipe-back + tab bar at bottom; Android users expect system back + nav structure
+
+### 2. Thumb Zone Above All
+- Primary actions belong in the bottom 60% of the screen
+- Top-left corner = hardest to reach one-handed
+- Platform back buttons (iOS top-left) are the only justified exception
+
+### 3. Gesture + Haptic + Visual = One Interaction
+- Every interaction should engage all three senses when appropriate
+- Swipe reveals → haptic at threshold + visual action button
+- Toggle → haptic on state change + visual state update simultaneously
+- Pull-to-refresh → haptic on trigger + spinner animation + announce to screen readers
+
+### 4. Accessibility Is Not Optional
+- Minimum touch target: 44pt (iOS) / 48dp (Android)
+- Every tappable element without visible text needs `accessibilityLabel`
+- Every gesture needs an accessible alternative action
+- Test with VoiceOver (iOS) and TalkBack (Android) before shipping
+- Support Dynamic Type / sp font scaling (never lock font size)
+
+### 5. Reduce Motion Is a Hard Requirement
+- Check `UIAccessibility.isReduceMotionEnabled` (iOS) and `LocalReduceMotion` (Compose) everywhere you animate
+- Replace slides with fades; replace springs with eases; reduce or eliminate particle effects
+- Haptics are NOT animation — keep them even when reducing motion
+
+### 6. Safe Area = Non-Negotiable
+- Never hardcode padding for device-specific areas
+- Always use `safeAreaInsets` / `SafeAreaView` / `WindowInsets` APIs
+- Test on iPhone SE (small), iPhone 14 Pro (Dynamic Island), and latest iPad
+
+## Pre-Delivery Checklist
+
+Before presenting any design decision, implementation, or code:
+
+**Layout & Ergonomics**
+- [ ] Touch targets ≥ 44pt / 48dp everywhere
+- [ ] Safe area insets respected on all edges
+- [ ] Primary actions in thumb-reachable zone (bottom 60%)
+- [ ] Content not hidden behind notch / Dynamic Island / home indicator
+- [ ] Keyboard avoidance implemented for any screen with text inputs
+
+**Platform Conventions**
+- [ ] Back navigation: iOS swipe-back enabled + button; Android system back handled
+- [ ] Navigation pattern matches platform idiom (tab bar on iOS; nav bar or drawer on Android)
+- [ ] Status bar style contrasts with content behind it
+- [ ] Haptic feedback added for primary interactions (where hardware supports)
+
+**Accessibility**
+- [ ] VoiceOver/TalkBack labels on all interactive elements
+- [ ] Heading traits applied to screen titles and section headers
+- [ ] Custom gesture actions available via accessibility Actions menu
+- [ ] Dynamic Type / sp units used (no fixed font sizes)
+- [ ] Color contrast ≥ 4.5:1 for body text; ≥ 3:1 for large text / UI
+- [ ] Color information supplemented with shape/icon/text
+
+**Motion**
+- [ ] `reduceMotion` check before every animation
+- [ ] Animation duration appropriate (200-400ms for most; <200ms for micro)
+- [ ] Spring used for natural feel on expand/appear; ease-out for dismiss/collapse
+
+**Dark Mode**
+- [ ] All colors defined as adaptive (no hardcoded hex for any UI color)
+- [ ] Test on OLED (true black matters for pure black backgrounds)
+- [ ] Images and media contrast tested in both appearances
+
+## Stack-Specific Reminders
+
+### React Native
+- Use `react-native-safe-area-context` not built-in SafeAreaView
+- Use `react-native-reanimated` for gesture-driven animations
+- Use `react-native-gesture-handler` for complex touch interactions
+- FlatList not ScrollView for lists with 20+ items
+- `useNativeDriver: true` on every `Animated.timing()`
+
+### Flutter
+- `ListView.builder` not `Column + ForEach` for long lists
+- `const` constructors everywhere possible
+- `GoRouter` for navigation with deep link support
+- `Riverpod` for state management
+- `cached_network_image` for network images
+
+### SwiftUI
+- `NavigationStack` not deprecated `NavigationView` (iOS 16+)
+- `@StateObject` not `@ObservedObject` for own ViewModels
+- `LazyVStack` not `VStack` for long lists
+- `matchedGeometryEffect` for hero-like shared element transitions
+- `@Environment(\.accessibilityReduceMotion)` before any animation
+
+### Jetpack Compose
+- `LazyColumn` with `key = { it.id }` for lists
+- `derivedStateOf` for computed state values
+- `StatefulShellRoute` for tab persistence in GoRouter
+- `collectAsStateWithLifecycle()` in all state collection
+- `WindowCompat.setDecorFitsSystemWindows(window, false)` for edge-to-edge
+
+## Key Data Sources Baked Into Database
+
+| Domain | Authority |
+|--------|-----------|
+| iOS conventions | Apple Human Interface Guidelines |
+| Android conventions | Material Design 3 |
+| React Native patterns | React Navigation docs + RN official docs |
+| Flutter patterns | Flutter official docs + pub.dev best packages |
+| SwiftUI patterns | Apple developer documentation |
+| Compose patterns | Android Jetpack documentation |
+| Accessibility | WCAG 2.1 + iOS Accessibility + Android Accessibility |
+| Animation timing | Platform-standard specs (iOS spring / MD3 motion) |

package/template/agent/skills/subagent-driven-development/implementer-prompt.md

@@ -32,7 +32,10 @@ Task tool (general-purpose):
     1. Implement exactly what the task specifies
     2. Write tests (following TDD if task says to)
     3. Verify implementation works
-    4. Commit your work
+    4. Commit your work (if auto_commit is enabled)
+       - Read `.agent/config.yml` to check the `auto_commit` setting
+       - If `auto_commit: true` (or not set): `git add` changed files + `git commit`
+       - If `auto_commit: false`: skip commit and staging entirely. Print: "Skipping commit (auto_commit: false in .agent/config.yml). Files left as modified for manual commit."
     5. Self-review (see below)
     6. Report back
 

package/template/agent/skills/verification-before-completion/SKILL.md

@@ -99,6 +99,17 @@ Skip any step = lying, not verifying
 ❌ "Tests pass, phase complete"
 ```
 
+**`.agent/.tests/` check (if applicable):**
+
+If work involved modifying any `.agent/skills/<skill>/` or `.agent/.shared/<tool>/`, run tests before claiming done:
+```bash
+python3 .agent/.tests/run_tests.py <skill-name>
+```
+```
+✅ Run command → Paste full verbose output → All pass → Claim done
+❌ "Should still pass" / Skip running because "I didn't change the data"
+```
+
 **Agent delegation:**
 ```
 ✅ Agent reports success → Check VCS diff → Verify changes → Report actual state

package/template/agent/skills/writing-plans/SKILL.md

@@ -95,12 +95,15 @@ def function(input):
 Run: `pytest tests/path/test.py::test_name -v`
 Expected: PASS
 
-- [ ] **Step 5: Commit**
+- [ ] **Step 5: Commit (if auto_commit enabled)**
 
+Check `.agent/config.yml` for `auto_commit` setting:
+- If `auto_commit: true` (default):
 ```bash
 git add tests/path/test.py src/path/file.py
 git commit -m "feat: add specific feature"
 ```
+- If `auto_commit: false`: skip commit and staging. Print: "Skipping commit (auto_commit: false)."
 ````
 
 ## Remember

package/template/agent/workflows/mobile-uiux-promax.md

@@ -0,0 +1,137 @@
+---
+description: Plan and implement mobile app UI (iOS, Android, React Native, Flutter, SwiftUI, Compose)
+---
+
+# Mobile UI/UX Pro Max
+
+Data-driven mobile design intelligence. Runs a 4-step search sequence — style layer (web tool) → mobile behavior layer → stack guidelines → synthesize — before presenting any mobile UI design.
+
+## Prerequisites
+
+```bash
+python3 --version  # 3.8+ required
+```
+
+## When to Use
+
+When asked to design, build, or review mobile app UI. Activate for any request involving:
+- Mobile app screen design
+- iOS or Android UI
+- React Native, Flutter, SwiftUI, or Jetpack Compose UI
+- Navigation, gestures, onboarding, or mobile-specific UX patterns
+
+## 4-Step Search Sequence
+
+### Step 1 — Style Layer (web tool, same as web flow)
+
+Search for style, color, typography, and product inspiration:
+
+```bash
+python3 .agent/.shared/ui-ux-pro-max/scripts/search.py "<app type>" --domain product
+python3 .agent/.shared/ui-ux-pro-max/scripts/search.py "<style keywords>" --domain style
+python3 .agent/.shared/ui-ux-pro-max/scripts/search.py "<industry mood>" --domain color
+python3 .agent/.shared/ui-ux-pro-max/scripts/search.py "<mood>" --domain typography
+```
+
+### Step 2 — Mobile Behavior Layer (mobile tool)
+
+Search for mobile-specific UX patterns and platform conventions:
+
+```bash
+# Step 2: Mobile behavior (navigation, gestures, components, layout, platform, animation, onboarding, accessibility, ux-laws)
+python3 .agent/.shared/mobile-uiux-promax/scripts/mobile-search.py "<nav pattern>" --domain navigation
+python3 .agent/.shared/mobile-uiux-promax/scripts/mobile-search.py "<gesture>" --domain gestures
+python3 .agent/.shared/mobile-uiux-promax/scripts/mobile-search.py "<component>" --domain components
+python3 .agent/.shared/mobile-uiux-promax/scripts/mobile-search.py "<layout topic>" --domain layout
+python3 .agent/.shared/mobile-uiux-promax/scripts/mobile-search.py "<platform difference>" --domain platform
+python3 .agent/.shared/mobile-uiux-promax/scripts/mobile-search.py "<animation type>" --domain animation
+python3 .agent/.shared/mobile-uiux-promax/scripts/mobile-search.py "<onboarding pattern>" --domain onboarding
+python3 .agent/.shared/mobile-uiux-promax/scripts/mobile-search.py "<a11y concern>" --domain accessibility
+python3 .agent/.shared/mobile-uiux-promax/scripts/mobile-search.py "<psychology principle>" --domain ux-laws
+```
+
+### Step 3 — Stack Guidelines
+
+Search for your specific stack's implementation patterns:
+
+```bash
+# React Native
+python3 .agent/.shared/mobile-uiux-promax/scripts/mobile-search.py "<topic>" --stack react-native
+
+# Flutter
+python3 .agent/.shared/mobile-uiux-promax/scripts/mobile-search.py "<topic>" --stack flutter
+
+# SwiftUI
+python3 .agent/.shared/mobile-uiux-promax/scripts/mobile-search.py "<topic>" --stack swiftui
+
+# Jetpack Compose
+python3 .agent/.shared/mobile-uiux-promax/scripts/mobile-search.py "<topic>" --stack jetpack-compose
+```
+
+Use `-n 5` to get more results: `--domain navigation -n 5`
+
+### Step 4 — Synthesize and Design
+
+Combine all search results to inform:
+- Visual style (from Step 1)
+- Navigation structure and gestures (from Step 2)
+- Platform conventions and component choices (from Step 2)
+- Stack-specific implementation patterns (from Step 3)
+
+Present as **screen flows** not isolated component lists.
+
+## Pre-Delivery Checklist
+
+Before presenting any mobile UI design or implementation:
+
+- [ ] All touch targets ≥ 44pt (iOS) / 48dp (Android)
+- [ ] Safe areas respected (notch, Dynamic Island, home indicator)
+- [ ] Haptic feedback for key interactions (selection toggle success error)
+- [ ] `prefers-reduced-motion` / Reduce Motion respected on both platforms
+- [ ] Platform back navigation supported (iOS swipe-back + Android system back)
+- [ ] Accessibility labels on all interactive elements
+- [ ] Dark mode tested on both platforms
+- [ ] No hardcoded pixel values (use responsive units: pt/sp not px)
+
+## Domain Reference
+
+| Domain | When to search |
+|--------|---------------|
+| `navigation` | Nav structure, tab bar vs drawer, modals, deep links |
+| `gestures` | Swipe pull-to-refresh long press pinch |
+| `components` | Bottom sheet FAB snackbar chips skeleton |
+| `layout` | Safe areas thumb zone spacing keyboard |
+| `platform` | iOS vs Android conventions HIG vs MD3 |
+| `animation` | Transitions micro-interactions haptic timing |
+| `onboarding` | First-time flow permissions paywall signup timing |
+| `accessibility` | Touch targets screen reader labels contrast |
+| `ux-laws` | Psychology principles: Fitts Hick Miller Jakob Goal-Gradient Peak-End Doherty etc. |
+
+## Stack Reference
+
+| Stack | When to use |
+|-------|------------|
+| `react-native` | React Native (iOS + Android) |
+| `flutter` | Flutter (iOS + Android) |
+| `swiftui` | SwiftUI (iOS native) |
+| `jetpack-compose` | Jetpack Compose (Android native) |
+
+## Example: Fitness Tracker App (Dark Mode, RN)
+
+```bash
+# Step 1: Style
+python3 .agent/.shared/ui-ux-pro-max/scripts/search.py "fitness health tracker" --domain product
+python3 .agent/.shared/ui-ux-pro-max/scripts/search.py "dark energetic bold sport" --domain style
+python3 .agent/.shared/ui-ux-pro-max/scripts/search.py "fitness sport energy" --domain color
+python3 .agent/.shared/ui-ux-pro-max/scripts/search.py "bold dynamic" --domain typography
+
+# Step 2: Mobile behavior
+python3 .agent/.shared/mobile-uiux-promax/scripts/mobile-search.py "tab bar navigation bottom" --domain navigation
+python3 .agent/.shared/mobile-uiux-promax/scripts/mobile-search.py "swipe gesture workouts list" --domain gestures
+python3 .agent/.shared/mobile-uiux-promax/scripts/mobile-search.py "progress card stat tracker component" --domain components
+python3 .agent/.shared/mobile-uiux-promax/scripts/mobile-search.py "dark mode" --domain platform
+python3 .agent/.shared/mobile-uiux-promax/scripts/mobile-search.py "spring animation progress" --domain animation
+
+# Step 3: Stack
+python3 .agent/.shared/mobile-uiux-promax/scripts/mobile-search.py "list performance animation" --stack react-native
+```