FrontendWebMobile
React/Next.js frontend concerns — the Localz frontend is Next.js 16 App Router + Tailwind v4 + Clerk.
Why we need this / what value this brings
Frontend architecture decisions compound — inconsistent patterns across components make the codebase harder to extend as it grows.
When to use this
Establish conventions early (state management, component structure) since retrofitting them onto an inconsistent codebase is costly.
How to use or implement this
Follow the conventions already established in Localz's frontend (Next.js App Router, the editorial serif/mono design system) rather than introducing new ones ad hoc.
Subtopics
Empty folder — drop notes, links, and findings here as you research.