agentleFS
davision0102davision0102/fabrik/.agents/skills/design-system/SKILL.md

design-system

Skill3 starsChanged 3 days agoMITView on GitHub

Règles visuelles du projet — couleurs, polices, espacements, mode sombre. À lire avant de créer ou modifier une interface, ou pour changer le thème (couleur principale, police, arrondis).

193 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

Files
SKILL.md

Design system

Tout le thème vit dans src/index.css (Tailwind CSS 4, sans fichier de config).

Couleurs

Toujours utiliser les tokens, jamais de couleurs brutes : c'est ce qui fait marcher le mode sombre.

TokenUsage
background / foregroundfond de page / texte principal
cardsurfaces surélevées (cartes, panneaux)
muted-foregroundtexte secondaire
secondaryfonds discrets, survols
borderbordures et séparateurs
primarybouton principal (encre)
brandcouleur signature : accents, liens, détails
destructiveerreurs, suppressions

Utiliser brand avec parcimonie : un accent par zone, pas de grands aplats. Les opacités (bg-brand/10, text-brand/50) servent pour les nuances.

Changer la couleur signature : modifier --brand dans :root et dans .dark (format oklch). Garder la même teinte (3ᵉ valeur) dans les deux, un peu plus claire en sombre.

Typographie

  • Titres (h1–h3) : Bricolage Grotesque, appliquée automatiquement (font-heading).
  • Texte : Inter (font-sans).
  • Code et commandes : font-mono.
  • Grands titres : font-semibold tracking-tight, jamais font-bold + uppercase ensemble.

Pour changer de police : installer le paquet @fontsource-variable/<police>, l'importer en haut de src/index.css et modifier --font-heading ou --font-sans.

Mise en page

  • Conteneur : mx-auto max-w-6xl px-4 sm:px-6.
  • Sections : py-16 à py-24.
  • Arrondis généreux : rounded-3xl pour les blocs, rounded-full pour boutons et pastilles.
  • Toujours vérifier à 375 px de large : aucun défilement horizontal.

Mode sombre

La classe dark est posée sur <html> (script dans index.html + hook useTheme). Si une interface a été construite avec les tokens, elle fonctionne en sombre sans rien ajouter. Éviter dark: sauf cas particulier.

Mouvement

Animations courtes et utiles seulement (tw-animate-css : animate-in fade-in slide-in-from-bottom-3). Pas d'animation sur ce qui est utilisé en boucle.

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.