agentleFS
jeremy-colard-devjeremy-colard-dev/agent-communication-claude/.claude/skills/design-system/SKILL.md

design-system

Skill1 starsChanged 21 days agoMITView on GitHub

Charte graphique, éditoriale et accessibilité de l'organisation (Les Ateliers du Parc par défaut, personnalisable dans config/organization.json). À consulter systématiquement avant de générer une newsletter, une affiche A4 ou un e-mail HTML.

194 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

Charte Graphique & Éditoriale

1. Philosophie visuelle

Le style visuel privilégie une esthétique éditoriale chaleureuse, lisible et accessible :

  • Pas de fond blanc clinique (#ffffff) en plein écran : utiliser le fond Papier (#f4f2eb) à l'extérieur et Crème (#fbf8f0) pour les cartes de contenu.
  • Contraste maximal pour la lecture : texte principal en Noir Encre (#111111) et texte secondaire en Gris Ardoise (#4a4842).
  • Deux couleurs d'accentuation complémentaires définies dans config/organization.json :
    • Vert Forêt (#1f5c4b) : surtitres, badges de dates, étiquettes de rubriques.
    • Terracotta (#c84b31) : boutons d'action principaux (CTA) et un seul mot-clé mis en valeur dans le grand titre (<em> en italique souligné).

2. Typographies

  • Titres (h1, h2, h3) : Playfair Display, Georgia, serif.
  • Corps de texte & boutons : Manrope, Arial, sans-serif (taille minimale 15px sur e-mail, interlignage généreux 1.6 à 1.7).

3. Règles éditoriales strictes

  1. Zéro émoji dans les e-mails et newsletters : Ne jamais insérer d'émojis dans les objets ou le corps des e-mails. Les scripts brevo_tool.py et appscript_email.py nettoient d'ailleurs automatiquement tout émoji résiduel si allow_emojis_in_emails vaut false.
  2. Utilisation obligatoire des gabarits :
    • Pour une newsletter : toujours partir de templates/template_newsletter.html.
    • Pour une affiche imprimable ou sociale : toujours partir de templates/template_affiche_a4.html.
  3. Pied de page complet : Toujours conserver le bloc de pied de page sombre (#111111) contenant l'adresse postale, le téléphone et l'adresse e-mail cliquable de l'organisation.

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.