Cursor rule Cursor
Accessibility requirements for UI — semantic HTML, keyboard, names.
This repository also configures its own agents. See what frontend-template tells them →
Cursor rule Cursor
Accessibility requirements for UI — semantic HTML, keyboard, names.
Cursor rule Cursor
Fetchers, Tanstack Query hooks, and Zod validation for API layers.
Cursor rule Cursor
Biome, Fallow, and CI quality expectations for app code and tool config.
Cursor rule Cursor
Encapsulate component and feature folders; keep the UI file free of types and constants.
Cursor rule Cursor
Engineering practices — SRP, named exports, useEffect, errors.
Cursor rule Cursor
No inline display strings — use locales or constants; i18n stack wiring.
Cursor rule Cursor
Naming conventions for files, folders, and symbols.
Cursor rule Cursor
Folder layout for Next.js App Router and Vite + React variants.
Cursor rule Cursor
React runtime rules for Next.js App Router and Vite screens.
Cursor rule Cursor
Core frontend stack and quality gates for this template.
Cursor rule Cursor
When to use Context versus Zustand in app code.
Cursor rule Cursor
Tailwind class composition via cn (clsx + twMerge), not string ternaries.
Cursor rule Cursor
Vitest and Playwright BDD testing conventions.
Cursor rule Cursor
Spec-first gate for non-trivial changes. Procedures live in skills.
Cursor rule Cursor
Template identity, locked default stack, and the finish bar.
Cursor rule Cursor
Enforce specification-first delivery and independent quality gates for non-trivial changes.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: