What is Awesome Cursorrules?
Awesome Cursorrules is a community list by PatrickJS of Cursor project rules, written as .mdc files you copy into .cursor/rules/. It covers many stacks. For UI work it includes rules for Tailwind, shadcn/ui, Next.js, CSS and styling, accessibility testing and a Toss-style design system.
Awesome Cursorrules is an awesome-list repository of Cursor Project Rules. The README describes these as Markdown based .mdc files in .cursor/rules/ that tell Cursor how to behave for specific projects, file types, frameworks and workflows.
It is a general collection, not a design skill. Sections run from frontend frameworks and backend to testing and security, so the useful move is to pick the few rules that match your stack and UI needs.
What changes in your agent's output
- Generated components follow the conventions in the rule you add, such as Tailwind with shadcn/ui or a Next.js and React layout.
- Rule frontmatter holds a description and file globs, so a rule can attach automatically to matching files such as .tsx.
- Accessibility test rules steer Cypress or Playwright tests toward accessibility checks.
- A design system rule such as the Toss-style one pushes toward restrained color and a grayscale hierarchy.
UI related rules in the list
- CSS and Styling section: landing page image quality, several Tailwind combinations, HTML with Tailwind and JavaScript, and Styled Components.
- Frontend entries for shadcn/ui, Chakra UI, Material UI with Tailwind, Qwik, Solid.js and SvelteKit with Tailwind.
- Cypress and Playwright accessibility testing rules, and an RTL rule for right-to-left layouts.
Who it is for
Best for
- Cursor users who want a starting rule file for a known stack, then edit it to match their project.
- Teams that want shared .cursor/rules files committed to the repo so contributors get the same guidance.
- Developers pairing stack rules with a design-quality skill like frontend-design.
Not for
- People who want a deep design or accessibility audit workflow. Rules here are short stack guidance, so look at ui-ux-pro-max for design knowledge.
- Users of other editors, since the README frames everything around Cursor and the .mdc format.
- Anyone who copies without reading. Rules are community contributions, so review each file first.
Use it with UiChemy
If your Cursor rules produce HTML, CSS and JS for a page, UiChemy Composer can carry that kind of code into an editable WordPress site. Click Get Started on uichemy.com.
How to install Awesome Cursorrules: Cursor Rules for Frontend and CSS
mkdir -p .cursor/rulesThe README gives no install command. It is a copy-the-file flow.Find a rule
Browse the README categories, such as Frontend Frameworks and Libraries or CSS and Styling, and open the .mdc file that matches your stack.
Create the folder
Make a .cursor/rules directory in your project if it does not exist.
Copy the file
Copy the chosen .mdc file from the rules folder into .cursor/rules.
Customize it
The README says to adjust the rule to your project, for example by editing the globs and the description.
Check that it loaded
Open a matching file in Cursor and check that the rule shows as active in the project rules for that file.
Key features
- Modern .mdc formatThe repo uses Cursor Project Rules as .mdc files, with a description, globs and an alwaysApply flag in the frontmatter.
- Frontend frameworks sectionEntries for Angular, Astro, Next.js in several variants, Qwik, Solid.js, SvelteKit and a React and shadcn/ui rule.
- CSS and styling sectionA dedicated group with landing page image quality, Tailwind with Next.js, shadcn/ui, React and Firebase, plus HTML, Astro and Styled Components rules.
- Component library rulesSeparate rules for Chakra UI, Material UI with Tailwind, shadcn/ui with TypeScript and NextUI with Supabase.
- Accessibility testing rulesCypress and Playwright rules that focus on accessibility checks in end-to-end tests.
- Design system ruleA Toss-style design system entry describing disciplined product UI with restrained color and grayscale hierarchy.
- RTL and i18n ruleA right-to-left rule covering logical properties for Tailwind and React Native layouts.
- Landing page image qualityA rule against placeholder or broken image URLs, covering alt text, dimensions, licensing and responsive behavior.
- Scoped by globsEach rule lists file patterns, and alwaysApply false keeps a rule limited to matching or requested context.
- Public domain licenseThe repository is CC0-1.0, so rules can be copied and edited freely, and contributions are welcome.
Frequently asked questions
What is Awesome Cursorrules?
It is a GitHub list by PatrickJS of Cursor Project Rules, stored as .mdc files in a rules folder. Each entry sets project guidance for Cursor on a framework, language or workflow, and the README groups them by category.
How do I use Cursor rules from this repo?
Create a .cursor/rules folder in your project, copy the .mdc file you want into it, and customize it. The README lists exactly these steps. There is no package or command to run.
Does it include rules for Tailwind and shadcn/ui?
Yes. The CSS and Styling section lists several Tailwind rules, including Next.js, React with Firebase and shadcn/ui integration, and the frontend section has a React, TypeScript and shadcn/ui rule and a Next.js, React 19 and Tailwind rule.
Is it only for design and UI?
No. It is a general Cursor rules list covering backend, mobile, testing, databases, security and more. Only part of it concerns UI, so pick rules by section instead of copying the whole set.
What is the .mdc rule format?
It is a Markdown file with frontmatter. The README example uses a description, globs for the file patterns that auto-attach the rule, and alwaysApply, which should be false unless the guidance applies to every request.
Does it cover accessibility?
Partly. It has Cypress and Playwright accessibility testing rules and an RTL rule. For deeper audits use a dedicated skill such as web-accessibility-skill, since a short rule file cannot replace a full review.
Is it free and can I copy the rules?
The repository is licensed CC0-1.0, which is a public domain dedication, and the README welcomes contributions. Rules come from the community, so read each file and check it fits your project before you commit it.
Is there a rules list for other editors?
This repo is written around Cursor and the .mdc format. Other agents read SKILL.md files from a skills folder instead, so for a rule set in that shape compare design-taste-frontend or a larger kit like ui-craft. Those are separate projects with their own install steps.


