visual-color
Skill2 starsChanged 22 days agoMITView on GitHub
Use when any visual needs a professional palette: md-deck theme selection, article cover images, inline diagrams, or generated images (Zenn, LinkedIn, Dev.to, and slide decks). Canonical palette is dark-blue. Eyebrows use the secondary accent. Ordinary dashes use the arrow colour. Gap emphasis (style=gap) uses the accent. Dashed card outlines use color_dashed_outline. Plain white and black is for eval and regression only. Do not put customer names or subject claims here.
In this repository14 other files it gives its agents.
- AGENTS.mdAGENTS.md
- confluence-operationsSkill
- devto-articleSkill
- download-website-to-markdownSkill
- english-tech-blog-structureSkill
- linkedin-articleSkill
- llm-evaluationSkill
- md-deckSkill
- pdf-to-markdownSkill
- repo-security-auditSkill
- sales-agentSkill
- threat-model-attack-reviewSkill
- visual-diagramSkill
- zenn-articleSkill
The file
Files
Visual color
Shared palette for professional visuals. The same tokens apply to slide decks and to article covers, diagrams, and generated images. This skill names the colours and when to use them. It does not ship CSS. It is independent of any one deck, article, or subject.
Process and structure rules for those figures: visual-diagram. Slide markup: md-deck.
When to use
Load this skill for any visual that needs a professional palette:
- An md-deck theme, or a
deck_styletheme selection - An article cover (Zenn, LinkedIn, Dev.to)
- An inline diagram
- A generated image
Palette dark-blue
Canonical tokens. Background is off-white, not pure white.
| Role | HEX | Use |
| Background / off-white | #EDE8E4 | Page and image ground |
| Text | #333333 | Body text |
| Main / navy | #073365 | Titles, structure, diagram strokes, and ordinary dashed edges (--color-flow-arrow) |
| Accent | #F7581D | Highlights, calls to action, caution, and gap emphasis ([style=gap], --color-edge-gap) |
| Secondary accent | #1A6B7A | Eyebrows and other quiet labels (--color-accent-2). On this theme, also the {.dashed} card outline (--color-dashed-outline) |
Area split: about 60% background, about 30% text and structure, about 10% accent. The secondary accent colours eyebrows and, on dark-blue, the dashed card outline. The accent share stays the highlights, including gap emphasis.
Ops rules
- Customer-facing decks, and public article covers and diagrams, use
dark-blue. - Plain white and black is for evaluation and visual regression only. Do not use it for a customer-facing or public visual.
- An eyebrow uses the secondary accent (
--color-accent-2,#1A6B7Aondark-blue). - An ordinary dashed edge (
..>,-.[label].->) uses the arrow colour (--color-flow-arrow, navy#073365ondark-blue). - Gap emphasis uses the accent (
--color-edge-gap,#F7581Dondark-blue) only when that dashed edge has[style=gap]. The shaft is0.5pxthicker than the arrow shaft, and the dash is tighter. Markup: md-deck. - A
{.dashed}card outline uses--color-dashed-outlineand--dashed-outline-width. Ondark-bluethe colour is the secondary accent#1A6B7Aand the width is2.5pxwhen the token is omitted. Plain is#333333at2px. Those defaults are darker and thicker than the earlier card-border dash. A deck overridescolor_dashed_outlineanddashed_outline_width. Markup: md-deck.
How consumers apply
- md-deck. Select theme
dark-blueindeck_style. The theme CSS lives in md-deck. This skill does not ship that CSS. Authoring rules: md-deck. - Articles and image generation. Pass these HEX values and roles into the image prompt for a cover or a diagram. Keep the ground off-white, the structure navy (including an ordinary dash), the accent for a gap emphasis or a highlight, and the secondary accent for a section label and for a dashed card outline.
Sources
- Theme color samples — dark-blue HEX roles. The site is closed; use the Wayback snapshot.
- PowerPoint color schemes — navy, gray, and one accent (60-30-10).
- Slide accessibility guidance — avoid a pure white background; prefer navy on off-white.
- Digital Agency design system: color — token roles.
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.

