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.

skills.sh installs: 3.4K
GitHub stars: 491
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add bencium/bencium-marketplace --skill bencium-code-conventions --agent claude-code

Installs into .claude/skills of the current project.

Files

Code Conventions

Core Technologies

Frontend: ReactJS, Next.js (App Router structure), TypeScript
Styling: TailwindCSS v3.x (never v4), Shadcn UI
Build Tools: Vite (when applicable)
Backend: Postgres compatible convex.dev or Supabase (always ask, never local postgres)
Deployment: Netlify or Vercel or Fly - suggest
Environment: Mac M2, Python3 with virtual environments, no CUDA, no Docker
Alternative Languages: Avoid python if you can, try using RUST

Code Style & Structure

Use ES modules (import/export) syntax
Destructure imports when possible
Use TypeScript for all new code
Use async/await instead of Promise chains
Prefer const/let over var; use early returns
Use consts instead of functions: const toggle = () =>. Define types.
Use descriptive variable names with auxiliary verbs (e.g., isLoading, hasError)
Use lowercase with dashes for directory names (e.g., components/auth-wizard)