design
01Cursor rule Cursor
Design system, visual standards, component behavior, and interaction patterns. Apply whenever creating or editing UI — components, pages, styles, forms, tables, dropdowns, modals, or anything a user sees.
A starter template for .cursor/rules — five ready-to-fill markdown files that give AI full context on your product, tech stack, design system, project structure, and behavioral guardrails. Copy into any project, replace the [brackets], and every Cursor conversation is immediately better.
This repository also configures its own agents. See what cursor-rules tells them →
Cursor rule Cursor
Design system, visual standards, component behavior, and interaction patterns. Apply whenever creating or editing UI — components, pages, styles, forms, tables, dropdowns, modals, or anything a user sees.
Cursor rule Cursor
Documentation and cursor-rules maintenance — where docs live, how they're named, and what must stay current. The step-by-step "update docs" workflow lives in the update-docs skill.
Cursor rule Cursor
Universal AI behavior, communication, and guardrails. Applies to every interaction.
Cursor rule Cursor
Model selection guidance — which Cursor model fits the task at hand, and when to tell the user to switch. Applies to every interaction.
Cursor rule Cursor
Product context — what this is, who it's for, and where it's going. Applies to every interaction.
Cursor rule Cursor
Security checklist and guardrails. Applies to all code that handles user input, authentication, authorization, or external data.
Cursor rule Cursor
Project folder structure and file placement conventions. Applies to all file creation and organization.
Cursor rule Cursor
Tech stack, coding conventions, and engineering standards. Applies to all code files.
Cursor rule Cursor
This repository publishes the cursor-rules template. It is not an application. Never fill shipped placeholders or run /setup-rules here unless the user is converting a clone into a new app.
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: