rahXephonz

Trace bugs using repository graph before broad source scanning

Understand repository architecture with graph-first navigation

Plan and verify refactors using dependency and flow analysis

Perform risk-aware review using changes, impact, flows, and tests

Token architecture, component specifications, and slide generation. Three-layer tokens (primitive→semantic→component), CSS variables, spacing/typography scales, component specs, strategic slide creation. Use for design tokens, systematic design, brand-compliant presentations.

Create beautiful, accessible user interfaces with shadcn/ui components (built on Radix UI + Tailwind), Tailwind CSS utility-first styling, and canvas-based visual designs. Use when building user interfaces, implementing design systems, creating responsive layouts, adding accessible components (dialogs, dropdowns, forms, tables), customizing themes and colors, implementing dark mode, generating visual designs and posters, or establishing consistent styling patterns across applications.

Use when writing or refactoring any TypeScript in this repo. Enforces the project's functional-programming style: pure functions, immutability, data-last pipe composition, Option/Result over null-and-throw, and exhaustive ts-pattern matching. Names the sanctioned FP libraries (ts-pattern, @mobily/ts-belt, effect) and where each belongs.

Development workflows and invariants for the wirenav codebase — extracting React Native navigation graphs via static analysis. Use this skill whenever working on ANY of - the Graph IR types, the .nav serializer or differ in @wirenav/core, the Expo Router extractor, the React Navigation extractor, edge inference, ParamList type extraction, screen previews (definePreview, snap-web, SnapshotMap, mock registry), fixture/golden-file tests, or the CLI. Also trigger when the user mentions "extractor", ".nav file", "navCheck", "IR", "golden files", "preview", "snapshot", or asks to add support for a new router, navigation pattern, or native-module mock.