Bencium Code Conventions

bencium/bencium-claude-code-design-skill

This is Bence's personal coding playbook packaged as a Claude skill. It locks in a specific stack (Next.js App Router, TypeScript, TailwindCSS v3, Shadcn UI) and workflow (TDD with real tests, no mocking, explore then plan then code then commit). The conventions are opinionated: always async/await, const arrow functions with types, no useEffect spam, prefer Rust over Python when possible. Backend is always cloud (Convex or Supabase, never local Postgres). Useful if you're working on Bence's projects or like his preferences enough to adopt them wholesale. The specificity is the point here, it's not trying to be universal.

skills.sh installs: 304
GitHub stars: 267
last updated: Jun 3, 2026

View on GitHub

Install

$ npx -y skills add bencium/bencium-claude-code-design-skill --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)