agentleFS
xsovad06xsovad06/sova/.agents/skills/design-system/SKILL.md

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

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

    setup-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

  • CoralGameSkill

    team-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

  • lilangMaxSkill

    create-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

  • lilangMaxSkill

    story-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

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
  1. Distinctive:

    When creating or modifying frontend templates, CSS, or UI components, follow these conventions.

    line 8
  2. Distinctive:

    Use whitespace to separate logical sections: generous padding over cramped layouts

    line 13
  3. Distinctive:

    Do not use font weights below 400 for body text

    line 21
  4. Distinctive:

    Use a consistent spacing scale (4px base: 4, 8, 12, 16, 24, 32, 48)

    line 26
  5. Very specific:

    Use semantic color names in CSS (--color-primary, --color-danger) not raw values

    line 34
  6. Distinctive:

    No centered-everything layouts: use left-aligned text with intentional centering

    line 40
  7. Distinctive:

    No generic card grids without hierarchy: vary card sizes to show importance

    line 41
  8. Distinctive:

    No walls of same-sized buttons: establish visual priority

    line 42
  9. Distinctive:

    No unstyled form elements: every input needs focus states and consistent borders

    line 43
  10. Distinctive:

    Do not hide critical information behind hover states on touch devices

    line 50

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

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.