Bencium Code Conventions

This is a comprehensive style guide that configures Claude to write code exactly how Bence wants it: Next.js App Router with TypeScript, TailwindCSS v3, Shadcn UI, and backend via Convex or Supabase (never local Postgres). It enforces specific patterns like const arrow functions over traditional functions, descriptive variable names with auxiliary verbs, and a strict workflow of explore, plan, code, then commit. The TDD approach is particularly rigid: write failing tests first, run them all until they pass, no mocking allowed. Honestly feels like pair programming with someone who has very specific opinions about their stack, but if you work with Bence or share his preferences around RSC, minimal client components, and Rust over Python, this will save you from constant style corrections.