slopgate / rules
Cursor rule1 starsChanged 51 days agoMITView on GitHub
Design system, typography, color, accessibility (WCAG 2.2), responsive-first layout, and motion design standards
We split this design.mdc into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
If the service supports CJK languages: prioritize CJK-ready fonts (Pretendard Variable > Noto Sans CJK > system-ui fallback).
- Distinctive: line 17
ALL output must be responsive-first (mobile layout as default, enhance upward).
- Distinctive: line 23
Typography: Don't default to custom Google Fonts.
- Distinctive: line 24
Color: Avoid purple-to-blue gradient backgrounds.
- Distinctive: line 27
Components: Use shadcn/ui for base; all interactive elements must have visible focus states
≈ “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: "Design system, typography, color, accessibility (WCAG 2.2), responsive-first layout, and motion design standards" globs: alwaysApply: false --- <!-- Generated by oh-my-agent. Source: .agents/rules/design.md --> # Design Standards ## Core Rules 1. System font stack as default (`system-ui, -apple-system, BlinkMacSystemFont, 'Segoe UI', Roboto, sans-serif`). Add custom fonts only with project justification. 2. If the service supports CJK languages: prioritize CJK-ready fonts (Pretendard Variable > Noto Sans CJK > system-ui fallback). 3. Name colors semantically with hex values: "Deep Ocean Navy (#1a2332)" not "dark blue". 4. Recommend components with install commands (shadcn CLI). 5. ALL output must be responsive-first (mobile layout as default, enhance upward). 6. WCAG AA minimum for all designs. Respect `prefers-reduced-motion`. 7. Present 2-3 design directions and get user confirmation before generating. ## Anti-Patterns to Avoid - **Typography**: Don't default to custom Google Fonts; body text minimum 16px on mobile; test CJK at every size - **Color**: Avoid purple-to-blue gradient backgrounds; avoid gradient orbs/blobs; use solid colors or subtle single-hue gradients - **Layout**: 8px grid; works at 375px minimum; avoid nested cards inside nested cards - **Motion**: transform + opacity only for 60fps; 150ms micro-interactions, 200-500ms transitions; respect prefers-reduced-motion - **Components**: Use shadcn/ui for base; all interactive elements must have visible focus states
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 repository115 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/backend.mdcCursor rule
- .cursor/rules/commit.mdcCursor rule
- .cursor/rules/database.mdcCursor rule
- .cursor/rules/debug.mdcCursor rule
- .cursor/rules/dev-workflow.mdcCursor rule
- .cursor/rules/frontend.mdcCursor rule
- .cursor/rules/i18n-arb.mdcCursor rule
- .cursor/rules/i18n-guide.mdcCursor rule
- .cursor/rules/infrastructure.mdcCursor rule
- .cursor/rules/market.mdcCursor rule
- .cursor/rules/mobile.mdcCursor rule
- .cursor/rules/quality.mdcCursor rule
- beadsSkill
- gitnexus-area-adaptersSkill
- gitnexus-area-cliSkill
- gitnexus-area-contextSkill
- gitnexus-area-dashboardSkill
- gitnexus-area-detectorsSkill
- gitnexus-area-engineSkill
- gitnexus-area-enrichmentSkill
- gitnexus-area-hooksSkill
- gitnexus-area-installerSkill
- gitnexus-area-integrationSkill
- gitnexus-area-lintSkill
- gitnexus-area-payloadsSkill
- gitnexus-area-project-indexSkill
- gitnexus-area-resourcesSkill
- gitnexus-area-rules-2Skill
- gitnexus-area-rulesSkill
- gitnexus-area-scriptsSkill
- gitnexus-area-test-smellsSkill
- gitnexus-area-testsSkill
- gitnexus-area-uiSkill
- gitnexus-cliSkill
- gitnexus-debuggingSkill
- gitnexus-exploringSkill
- gitnexus-guideSkill
- gitnexus-impact-analysisSkill
- gitnexus-refactoringSkill
- impeccableSkill
- oma-academic-writingSkill
- oma-architectureSkill
- oma-backendSkill
- oma-brainstormSkill
- oma-coordinationSkill
- oma-dbSkill
- oma-debugSkill
- oma-deepsecSkill
- oma-designSkill
- oma-dev-workflowSkill
- oma-docsSkill
- oma-explanationSkill
- oma-frontendSkill
- oma-hwpSkill
- oma-imageSkill
- oma-marketSkill
- oma-mobileSkill
- oma-observabilitySkill
- The first 60 shown.
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.

