fusion-design
Skill2 starsChanged 2 months agoMITView on GitHub
Looks up Fusion Design Guidelines and applies them to any frontend code in the Fusion ecosystem. USE FOR: layout, spacing, component usage, interaction patterns, any UI implementation decision. DO NOT USE FOR: backend changes, CI/CD, skill authoring, data layer logic.
In this repository31 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .github/copilot-instructions.mdCopilot instructions
- caveman-compressSkill
- fusion-core-servicesSkill
- fusion-dependency-reviewSkill
- fusion-framework-mockingSkill
- fusion-framework-testingSkill
- fusion-github-review-resolutionSkill
- fusion-issue-solvingSkill
- fusion-issue-task-planningSkill
- fusion-mcpSkill
- fusion-package-scribeSkill
- fusion-pm-mcpSkill
- fusion-backend-devSkill
- fusion-developer-appSkill
- fusion-developer-portalSkill
- fusion-devtoolsSkill
- fusion-help-apiSkill
- fusion-help-docsSkill
- fusion-help-integrationSkill
- fusion-infra-cliSkill
- fusion-issue-authoringSkill
- fusion-roles-cliSkill
- fusion-rulesSkill
- fusion-skill-authoringSkill
- fusionSkill
- fusion-skillsSkill
- equinor-design-systemSkill
- fusion-code-conventionsSkill
- fusion-researchSkill
- fusion-rule-authorSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 25
All text uses EDS
<Typography>: Never write a bare <h1>–<h6>, <p>, or <span> for text — not even a temporary title or stub. - Very specific: line 26
All spacing uses EDS spacing variables: Never hardcode px in padding/margin/gap.
- Very specific: line 49
If the app has a DESIGN.md at its root, read it first.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Fusion Design
When to use
Any time you are writing or reviewing frontend code in the Fusion ecosystem and need to know how it should look, behave, or be structured.
Non-negotiable invariants
These apply to every file you write, regardless of the task — do not wait until you have read the references to honour them, and never emit a "placeholder" that violates them:
- All text uses EDS
<Typography>. Never write a bare<h1>–<h6>,<p>, or<span>for text — not even a temporary title or stub. A page title is<Typography variant="h1">, body text is<Typography variant="body_short">. Seereferences/eds-typography.md. - All spacing uses EDS spacing variables. Never hardcode
pxinpadding/margin/gap. Seereferences/spacing.md.
Instructions
This skill is a lookup. Read all reference files before writing any code — they define mandatory requirements, not optional styling.
1. Read the references
| Topic | File |
| EDS Typography | references/eds-typography.md |
| Navigation — Sidemenu | references/navigation-sidemenu.md |
| Navigation — Tabs | references/navigation-tabs.md |
| Layout — Content area patterns | references/layout.md |
| Layout — Centered content | references/layout-centered-content.md |
| Spacing | references/spacing.md |
| Actions — Action bar, destructive actions, button placement | references/actions.md |
| Empty states | references/empty-states.md |
| Error messages | references/error-messages.md |
| Contextual help (ℹ / ? icons, density) | references/contextual-help.md |
2. Check for a local DESIGN.md
If the app has a DESIGN.md at its root, read it first. It is the authoritative source for that app's design decisions and overrides or supplements the reference rules.
3. Apply
Implement the UI to match the rules. If no DESIGN.md exists and the task requires a layout decision, document it there.
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.

