review-frontend-conventionslisted

# Review — Frontend Conventions Reviewer for frontend repository conventions that are more specific than generic React/MobX correctness. Use it alongside `review-frontend`, `review-style`, `review-performance`, and `review-logic`. Before reviewing, read the nearest project guide files if they exist: root `CLAUDE.md`, `AGENTS.md`, `.junie/guidelines.md`, `ARCHITECTURE.md`, and module-level `CLAUDE.md` files. The checklist below is a neutral baseline; local project rules win when they are stricter. --- ## Scope Review changed frontend source, stories, tests, and UI wrapper files for local conventions. Do not flag unrelated generic React/MobX issues unless they also violate a local convention or the baseline below. If no local convention document exists, run only the neutral baseline and state that no project-specific guide was found. --- ## Checklist ### Styling and UI - Prefer the repository's styling system consistently (Tailwind, CSS modules, design tokens, or the established local framework). - Avoid inline `style` except for genuinely dynamic positioning or third-party integration seams. - Theme colors and spacing come from local tokens, not ad hoc literals. - Use the established UI kit and wrapper layer; do not bypass shared wrappers without a reason. - Reuse existing icons/assets before adding new ones. ### TypeScript - Avoid `any` and broad `as` casts. Prefer type guards, discriminated unions, and precise types. - Keep tests and stories typed unless intent