saas-starter / rules
Cursor rule9 starsChanged 42 days agoMITView on GitHub
Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.
We split this impeccable.mdc into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Read .agents/skills/impeccable/SKILL.md before answering.
≈ “Common” is an estimate: at least 1 in 5 of the 6,350 Cursor rule files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
--- description: Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks. alwaysApply: false --- # impeccable Read `.agents/skills/impeccable/SKILL.md` before answering. It is the source; this file exists only so Cursor knows the skill is there. Generated by `bun run agents` from `.agents/skills`. Do not edit.
Where files are headingNew Cursor rule files have more rules about planning and tracking tasks, and fewer about code style.
Of the Cursor rule files we read, the 3,978 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository33 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/better-auth.mdcCursor rule
- .cursor/rules/brand-review.mdcCursor rule
- .cursor/rules/campaign-plan.mdcCursor rule
- .cursor/rules/competitive-brief.mdcCursor rule
- .cursor/rules/content-creation.mdcCursor rule
- .cursor/rules/draft-content.mdcCursor rule
- .cursor/rules/effect-form-e2e.mdcCursor rule
- .cursor/rules/effect-sql-rls.mdcCursor rule
- .cursor/rules/email-sequence.mdcCursor rule
- .cursor/rules/grilling.mdcCursor rule
- .cursor/rules/grill-me.mdcCursor rule
- .cursor/rules/performance-report.mdcCursor rule
- .cursor/rules/product-development.mdcCursor rule
- .cursor/rules/seo-audit.mdcCursor rule
- .cursor/rules/tanstack-start-ssr.mdcCursor rule
- better-authSkill
- brand-reviewSkill
- campaign-planSkill
- competitive-briefSkill
- content-creationSkill
- draft-contentSkill
- effect-form-e2eSkill
- effect-sql-rlsSkill
- email-sequenceSkill
- grillingSkill
- grill-meSkill
- impeccableSkill
- performance-reportSkill
- product-developmentSkill
- seo-auditSkill
- tanstack-start-ssrSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

