dangapp

Enforce local guidance files for new folders, require top-of-file description comments, and promote repeatable patterns into reusable skills.

Validate and enforce consistency between Next.js App Router page routes and `docs/status/PAGE-UPGRADE-BOARD.md` before status sync work.

Diagnose Supabase RPC and query paths that return empty data, wrong data, or runtime errors.

Run Supabase MCP work in a predictable order and document each change clearly.

Compare DangApp code, docs/status artifacts, and local guidance files before deciding what to update.

Collect DangApp implementation patterns before adding new routes, feature modules, or data-contract changes.

Mobile app shell pattern with a fixed top bar, bottom navigation, and content spacing that prevents overlap with route content.

Build reusable UI primitives with class-variance-authority and a shared `cn()` merge path instead of ad hoc class branching.

Multi-step form pattern using Zustand, React Hook Form, and validation boundaries that preserve progress and partial completion state.

Shared Framer Motion wrapper pattern for route and component transitions, tap feedback, and staggered reveal behavior.

Skeleton state pattern that mirrors the final layout closely so loading transitions feel stable and intentional.

Encapsulate Supabase data access in TanStack Query hooks so routes and components consume stable server-state APIs instead of inline client calls.

Surface trust, safety, and verification signals prominently in matching, profile, and messaging contexts.

Replace mock or hardcoded route data with live TanStack Query and mutation flows backed by stable hooks.

Add explicit error, recovery, and retry behavior for DangApp routes and feature modules.

Build or upgrade DangApp forms with intentional validation, submit flow, and post-submit handling.

Refine route transitions, back navigation, sheet flows, and touch interactions in DangApp.

Add intentional empty states and skeleton loading patterns for DangApp routes and feature modules.

Upgrade `/schedules` route UI, data flow, and schedule follow-up actions for parity work.

Orchestrate DangApp UI redesign work from research normalization through route mapping, reusable component planning, implementation order, and optional docs/status alignment. Use when redesign spans multiple routes, the design system, or a provided deep research report before implementation starts.

Upgrade /care route UI, data flow, and route-specific behavior for parity work. Use when implementing or stabilizing /care and its directly related feature modules and hooks.

Upgrade /chat route UI, data flow, and route-specific behavior for parity work. Use when implementing or stabilizing /chat and its directly related feature modules and hooks.

Upgrade /chat/[id] route UI, data flow, and route-specific behavior for parity work. Use when implementing or stabilizing /chat/[id] and its directly related feature modules and hooks.

Upgrade /danglog route UI, data flow, and route-specific behavior for parity work. Use when implementing or stabilizing /danglog and its directly related feature modules and hooks.

Upgrade /family route UI, data flow, and route-specific behavior for parity work. Use when implementing or stabilizing /family and its directly related feature modules and hooks.

Upgrade /home route UI, data flow, and route-specific behavior for parity work. Use when implementing or stabilizing /home and its directly related feature modules and hooks.

Upgrade /login route UI, data flow, and route-specific behavior for parity work. Use when implementing or stabilizing /login and its directly related feature modules and hooks.

Upgrade /modes route UI, data flow, and route-specific behavior for parity work. Use when implementing or stabilizing /modes and its directly related feature modules and hooks.

Upgrade /onboarding route UI, data flow, and route-specific behavior for parity work. Use when implementing or stabilizing /onboarding and its directly related feature modules and hooks.

Upgrade /profile route UI, data flow, and route-specific behavior for parity work. Use when implementing or stabilizing /profile and its directly related feature modules and hooks.

Upgrade /register route UI, data flow, and route-specific behavior for parity work. Use when implementing or stabilizing /register and its directly related feature modules and hooks.