mit einem Klick
architecture-standards
This skill enforces the strict directory structure and file naming conventions of the project. Use this whenever an agent is creating new files or folders to ensure consistency across the client and server.
Menü
This skill enforces the strict directory structure and file naming conventions of the project. Use this whenever an agent is creating new files or folders to ensure consistency across the client and server.
Authoritative guide for the monorepo architecture of the react-supabase-boilerplate. Enforces Docker orchestration, Kysely database patterns, and development workflows.
Opinionated backend development standards for Node.js + Express + TypeScript microservices. Covers layered architecture, BaseController pattern, dependency injection, Prisma repositories, Zod validation, unifiedConfig, Sentry error tracking, async safety, and testing discipline.
This skill focuses on backend architecture (Controller/Service/Repository), Prisma interaction, and standardized error/response middleware. Use it when building or modifying backend routes, controllers, or services.
This skill enforces robust, scalable testing methodologies for both the frontend and backend. Use it when writing unit or integration tests, setting up testing frameworks like Vitest, or verifying that features conform to the "Gold Standard".
Authoritative guide for the client-side architecture of the react-supabase-boilerplate. Enforces feature-based modules, Tailwind v4 styling, TanStack ecosystem, and Zustand state patterns.
Authoritative guide for the server-side architecture of the react-supabase-boilerplate. Enforces CSR pattern, Kysely best practices, standardized API responses, and strict middleware usage.
| name | architecture-standards |
| description | This skill enforces the strict directory structure and file naming conventions of the project. Use this whenever an agent is creating new files or folders to ensure consistency across the client and server. |
This skill ensures that the codebase remains clean, predictable, and scalable by strictly enforcing a feature-based folder structure and uniform, lowercase file naming conventions.
lowercase-with-hyphens.purpose.extension format for all files across the
stack to prevent casing issues across different operating systems.client and server strictly follow a Feature-Based architecture.
src/features/[feature-name]/.src/components/, src/utils/, or src/controllers/ folders.src/shared/ for code that is truly agnostic and used across multiple features
(e.g., global error handlers, UI primitives, generic API configuration).tests/ directory of the client or server, following the
tests/[feature]/[unit|integration] pattern.userComponent.tsx is
forbidden; use user-component.tsx).- separator (e.g.,
user-profile).[feature/domain].[purpose].ts.auth.controller.tsauth.service.tsauth.repository.tsauth.route.tserror.middleware.ts[domain].[purpose].ts (e.g., auth.store.ts,
use-debounce.hook.ts, data-table.util.ts)..tsx or .ts files, generally ending with the element type if ambiguous. The
purpose notation is optional here if the feature folder implies the component type.login-form.tsxprofile-card.tsxdashboard.page.tsx (if representing a full route layout)T followed by an uppercase first letter.
TJWTPayload, TAuthResponseJWTPayload, AuthResponseany: The use of any is strictly forbidden.px). Use rem.container for page layouts.tracking-* or font-black.