unparalleled-skillset / rules
Cursor rule41 starsChanged 10 days agoMITView on GitHub
Application screens, dashboards, forms, and components
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 4,181 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 repository6 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/unparalleled-website.mdcCursor rule
- unparalleled-uiSkill
- unparalleled-websiteSkill
The file
We split this unparalleled-ui.mdc into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are 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.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 9
Read .agents/skills/unparalleled-ui/SKILL.md for application interfaces and .agents/skills/unparalleled-website/SKILL.md for public …
- Very specific: line 15
Run npm run validate-all and npm run check-contrast for repository fixtures/structure, and the applicable product checks.
≈ “Common” is an estimate: at least 1 in 5 of the 6,668 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: Application screens, dashboards, forms, and components
globs: **/*.{tsx,jsx,vue,svelte,html,css}
alwaysApply: false
---
# Unparalleled design routing
Read `.agents/skills/unparalleled-ui/SKILL.md` for application interfaces and `.agents/skills/unparalleled-website/SKILL.md` for public websites. The complete applicable skill and the current human brief govern the work; load supporting references when needed.
For a new task invoke the prompt architect, then create the vocabulary-led Design/Brand Kit. Use inner Playwright inspection/repair and outer human reviews for the kit, consequential design choices, specimen and progressive working milestones. Preserve explicit choices, approved revisions and scoped waivers. Local fixes inherit the established kit and task.
Choose component geometry dynamically from product, task and brand: pills, rounding, square edges and other forms are valid. Keep facts truthful, controls accessible, and design decisions grounded in the product. Do not substitute a fixed genre or component recipe for discovery.
Run `npm run validate-all` and `npm run check-contrast` for repository fixtures/structure, and the applicable product checks. Actual rendered review and measured foreground/background pairs remain necessary; scripts and scores cannot supply human approval or certify design quality.
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.