bencium-code-conventions

Enforce TypeScript, ES modules, and app router conventions in React projects.

Updated Mar 23, 2026
One-click install
npx skills add https://github.com/ProLeadAppt/doggroomerdemo --skill bencium-code-conventions-proleadappt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bencium-code-conventions
Source: https://github.com/ProLeadAppt/doggroomerdemo/tree/main/.agents/skills/bencium-bencium-code-conventions
Command: npx skills add https://github.com/ProLeadAppt/doggroomerdemo --skill bencium-code-conventions-proleadappt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

To standardize how projects are built and remain maintainable across teams by codifying Bence's code style, tech stack, and workflow conventions.

Core Features & Use Cases

  • Establishes a standardized tech stack and project structure for frontend and backend work.
  • Enforces TypeScript usage, ES modules, and app router conventions to improve consistency.
  • Guides naming, architecture, and tooling choices (e.g., Next.js, TailwindCSS, Zustand, TanStack) for scalable projects.

Quick Start

Create a new project scaffold following Bence's conventions and set up the configured tooling.

Frequently Asked Questions about bencium-code-conventions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce code conventions and project structure for a React and Next.js App Router codebase?

Enforcing code conventions for React and Next.js App Router projects involves codifying standards for TypeScript usage, ES modules, and directory structure into a repeatable project setup blueprint. This ensures consistent tooling and reproducible builds across teams.

What is the best way to standardize TypeScript and TailwindCSS coding style across a development team?

Standardizing TypeScript and TailwindCSS coding style is achieved by applying a predefined convention blueprint that dictates naming, architecture choices, and tooling guidance. This approach keeps frontend and full-stack projects maintainable and aligned.

Can I use this convention blueprint to scaffold a new frontend project from scratch?

Yes, you can use this convention blueprint to scaffold a new frontend project from scratch. It establishes a standardized tech stack and project structure, applying tooling guidance for Next.js, TailwindCSS, Zustand, and TanStack to ensure scalable architecture.

Does the code style guidance include state management and data fetching tooling for Next.js?

Yes, the code style guidance includes state management and data fetching tooling for Next.js. It directs architecture choices for scalable projects by recommending specific tools like Zustand for state management and TanStack for data fetching.

Why should I codify workflow conventions instead of relying on manual code reviews?

Codifying workflow conventions instead of relying on manual code reviews ensures reproducible builds and standardizes how projects remain maintainable across teams. It automates the enforcement of TypeScript, ES modules, and App Router conventions.