bencium-code-conventions

Bencium Code Conventions is a personal coding-standards skill that captures one developer's (Bence's) preferred tech stack, code style, and workflow so that an assistant produces code matching those conventions. It solves the problem of an AI generating technically valid but stylistically off-target code by encoding concrete choices up front—to be applied when writing code or setting up projects for this developer.

The single SKILL.md specifies a stack (React, Next.js App Router, TypeScript, TailwindCSS v3 with shadcn UI, Vite, Postgres via convex.dev or Supabase, deployment on Netlify/Vercel/Fly, a Mac M2 environment with no Docker and a preference for Rust over Python) and detailed code-style rules (ES modules, destructured imports, async/await, const arrow functions with defined types, descriptive boolean names, dash-case directories). It also covers framework conventions (Zustand, TanStack Query, Zod), component/styling preferences (shadcn from @/components/ui, Phosphor icons, sonner toasts, loading states), a test-driven workflow, error-handling practices, performance guidance (minimize 'use client'/useEffect, favor RSC/SSR, dynamic imports, optimized images), and an Explore→Plan→Code→Commit process. It includes standard, safe guidance to keep API keys in .env files and to store them in Vercel/Netlify environment variables.

Target users are Bence himself and any assistant or collaborator generating code on his behalf, plus teams who want an example of codifying personal or house conventions. It is documentation only, with no executable components, and its security-relevant content (using .env for secrets) is ordinary best-practice advice, so it carries no operational risk.