Agent skill

Awesome Cursorrules: Cursor Rules for Frontend and CSS

Awesome Cursorrules is a curated list of Cursor project rule files, including many for Tailwind, shadcn/ui, Next.js, accessibility testing and design systems.

Install
mkdir -p .cursor/rules
View on GitHub

Stars, license and last push from GitHub. Install count as reported by the open skills directory.

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.
  • 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.