design-system
Skill3 starsChanged 6 days agoApache-2.0View on GitHub
Frontend design conventions for SOVA: layout hierarchy, spacing, typography, anti-slop rules. Auto-activates when creating or modifying templates, CSS, or frontend components.
192 other projects use a version of this.
Adopted by
Most recently taken up by
- Rojios/everything-claude-codetheir own version, first seen Nov 8, 2026
- caidanw/skillstheir own version, first seen Nov 8, 2026
- Adelie-Squad/solosquadtheir own version, first seen Nov 8, 2026
- darkweb19/skillstheir own version, first seen Nov 8, 2026
- dmoreq/agent-grimoiretheir own version, first seen Nov 8, 2026
- ahmadvahidi/skill-atlastheir own version, first seen Nov 8, 2026
Used with
Projects with it also use setup-engine, team-level and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
CoralGameSkillsetup-engine
Configure the project's game engine and version. Pins the engine in CLAUDE.md, detects knowledge gaps, and populates engine reference docs via WebSearch when the version is beyond the LLM's training data.
Also in 13 projects that use this
CoralGameSkillteam-level
Orchestrate level design team: level-designer + narrative-director + world-builder + art-director + systems-designer + qa-tester for complete area/level creation.
Also in 12 projects that use this
lilangMaxSkillcreate-stories
Break a single epic into implementable story files. Reads the epic, its GDD, governing ADRs, and control manifest. Each story embeds its GDD requirement TR-ID, ADR guidance, acceptance criteria, story type, and test evidence path. Run after /create-epics for each epic.
Also in 11 projects that use this
lilangMaxSkillstory-done
End-of-story completion review. Reads the story file, verifies each acceptance criterion against the implementation, checks for GDD/ADR deviations, prompts code review, updates story status to Complete, and surfaces the next ready story from the sprint.
Also in 11 projects that use this
- +2 more from CoralGame
- +6 more from lilangMax
Other versions192 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 192
- nextlevelbuilder/ui-ux-pro-max-skill★ 147ksame name
- getsentry/sentry★ 46ksame name
- anthropics/knowledge-work-plugins★ 35ksame name
- Donchitos/Claude-Code-Game-Studios★ 27ksame name
- ethereum/ethereum-org-website★ 6ksame name
- langwatch/langwatch★ 5ksame name
- joye61/pic-smaller★ 2.9ksame name
- daveebbelaar/bama★ 1.7ksame name
- reatom/reatom★ 1.4ksame name
- microsoft/power-platform-skills★ 1.1ksame name
182 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository44 other files it gives its agents.
- AGENTS.mdAGENTS.md
- templates/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- templates/CLAUDE.mdCLAUDE.md
- dashboard-designSkill
- database-patternsSkill
- design-tasteSkill
- issue-templateSkill
- sova-address-prSkill
- sova-after-mergeSkill
- sova-agent-readinessSkill
- sova-audit-instructionsSkill
- sova-debugSkill
- sova-develop-explainSkill
- sova-develop-fullSkill
- sova-developSkill
- sova-extract-knowledgeSkill
- sova-find-taskSkill
- sova-health-auditSkill
- sova-ingest-reviewSkill
- sova-integrate-prSkill
- sova-issueSkill
- sova-new-featureSkill
- sova-optimize-knowledgeSkill
- sova-prSkill
- sova-rearrange-commitsSkill
- sova-researchSkill
- sova-review-fullSkill
- sova-review-prSkill
- sova-reviewSkill
- sova-simplifySkill
- sova-specSkill
- sova-standupSkill
- sova-statusSkill
- sova-testSkill
- sova-update-docsSkill
- testing-patternsSkill
- visual-auditSkill
- dashboard-designSkill
- database-patternsSkill
- design-tasteSkill
- issue-templateSkill
- testing-patternsSkill
- visual-auditSkill
The file
We split this skill into the rules it gives an agent
10 rules. 0 are common, 9 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 175 edited versions we read keep these.
9
Distinctive
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
- Distinctive: line 8
When creating or modifying frontend templates, CSS, or UI components, follow these conventions.
- Distinctive: line 13
Use whitespace to separate logical sections: generous padding over cramped layouts
- Distinctive: line 21
Do not use font weights below 400 for body text
- Distinctive: line 26
Use a consistent spacing scale (4px base: 4, 8, 12, 16, 24, 32, 48)
- Very specific: line 34
Use semantic color names in CSS (--color-primary, --color-danger) not raw values
- Distinctive: line 40
No centered-everything layouts: use left-aligned text with intentional centering
- Distinctive: line 41
No generic card grids without hierarchy: vary card sizes to show importance
- Distinctive: line 42
No walls of same-sized buttons: establish visual priority
- Distinctive: line 43
No unstyled form elements: every input needs focus states and consistent borders
- Distinctive: line 50
Do not hide critical information behind hover states on touch devices
“Common” is measured: kept by at least 6 in 10 of the 175 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Design System Conventions
When creating or modifying frontend templates, CSS, or UI components, follow these conventions.
Visual Hierarchy
- Establish clear heading hierarchy (h1 > h2 > h3) with distinct sizes
- Use whitespace to separate logical sections: generous padding over cramped layouts
- Primary actions must be visually distinct from secondary actions (size, color, weight)
- Data tables: header row visually distinct, alternating row backgrounds for readability
Typography
- Limit to 2 font families maximum (one for headings, one for body)
- Body text: 14-16px minimum, 1.5-1.6 line height
- Do not use font weights below 400 for body text
- Headings: use weight contrast (600-700) rather than excessive size
Spacing
- Use a consistent spacing scale (4px base: 4, 8, 12, 16, 24, 32, 48)
- Containers: minimum 16px padding on all sides
- Between sections: minimum 24px gap
- Between related items: 8-12px gap
Color
- Maintain WCAG AA contrast ratios (4.5:1 for text, 3:1 for large text)
- Use semantic color names in CSS (--color-primary, --color-danger) not raw values
- Status indicators: green=success, yellow=warning, red=error, blue=info
- Dark mode: never use pure black (#000) backgrounds, use dark grays
Anti-Slop Rules
- No centered-everything layouts: use left-aligned text with intentional centering
- No generic card grids without hierarchy: vary card sizes to show importance
- No walls of same-sized buttons: establish visual priority
- No unstyled form elements: every input needs focus states and consistent borders
- Animations: subtle and purposeful (150-300ms transitions), never decorative
Responsive
- Mobile-first: design for smallest viewport, enhance for larger
- Touch targets: minimum 44x44px on mobile
- Do not hide critical information behind hover states on touch devices
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.

