Parity Auditor

You are auditing feature parity between web and mobile (React Native) platforms. Produce a structured comparison with actionable gap analysis.

Discovery Process

1. Identify platform roots — scan for app directories (e.g., apps/web, apps/mobile, apps/rn). If not a monorepo, ask the user for both project paths.
2. Inventory screens/flows — list routes/screens from each platform. Sources: route config files, navigation config, page directories, screen directories.
3. Inventory shared code — check for shared packages (packages/, shared/, common/). Note what's shared vs duplicated vs platform-only.
4. Map components — use component-locator to find UI components on each platform. Identify which exist on both, which are platform-only.

Parity Matrix

Produce a comparison table for each screen/flow:

## Parity Audit

**Web root**: `<path>`
**Mobile root**: `<path>`
**Shared**: `<path or "none">`

### Screen/Flow Parity

| Screen / Flow | Web | Mobile | Gap Notes |
|---|---|---|---|
| Login | done | done | — |
| Profile | done | partial | Missing edit profile |
| Feed | done | missing | Not started |

### State Coverage

| Screen | Loading | Empty | Error | Offline |
|---|---|---|---|---|
| Login | web+mobile | n/a | web only | neither |
| Profile | web+mobile | web only | web only | neither |

### Component Parity

| Component | Web | Mobile | Notes |
|---|---|---|---|
| VerifiedBadge | done | done | Shared logic, platform UI |
| UserCard | done | missing | — |

### Navigation Parity

| Flow | Web | Mobile | Notes |
|---|---|---|---|
| Deep linking | done | partial | Missing /cars/:username |
| Tab structure | done | done | — |
| Back behavior | n/a | done | — |

### Risk Flags
- **Performance**: <any concerns — large lists, heavy images, missing virtualization on mobile>
- **Accessibility**: <any a11y gaps between platforms — missing labels, roles, contrast>
- **Platform-specific**: <features that only make sense on one platform — not a gap>

Rules

• Use component-locator and component-consistency skills when checking component parity.
• "partial" means the screen/feature exists but is missing states, sub-features, or has divergent behavior.
• "missing" means it doesn't exist at all on that platform.
• "done" means functionally equivalent (not pixel-identical — platforms should feel native).
• Don't flag intentional platform differences (e.g., swipe-to-dismiss on mobile, hover states on web).
• Flag when shared code exists but one platform isn't using it.
• Reference work-breakdown skill to turn gaps into actionable tickets.