
Fusion
- 601 installs
- 1 repo stars
- Updated August 4, 2026
- equinor/fusion-skills
fusion is an agent skill that applies Equinor Fusion design system tokens, components, and patterns so developers build interfaces consistent with enterprise Fusion UI standards.
About
fusion is an equinor/fusion-skills agent skill for developers building web interfaces on the Equinor Fusion design system. It guides use of Fusion design tokens, prebuilt components, and documented layout patterns so new screens match enterprise visual and interaction standards. Developers reach for fusion when scaffolding dashboards, forms, or data views that must align with Fusion typography, color tokens, spacing scales, and component APIs rather than ad-hoc CSS. The skill reduces design drift in large codebases where multiple teams ship UI concurrently. Use it during frontend build when Fusion compliance is required for internal or customer-facing Equinor applications.
- Fusion design system
- Component consistency
- Design tokens
- Enterprise UI standards
- Branded interfaces
Fusion by the numbers
- 601 all-time installs (skills.sh)
- Ranked #532 of 1,880 Design & UI/UX skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/equinor/fusion-skills --skill fusionAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 601 |
|---|---|
| repo stars | ★ 1 |
| Last updated | August 4, 2026 |
| Repository | equinor/fusion-skills ↗ |
How do you use Equinor Fusion design system components?
Apply Equinor Fusion design system tokens, components, and patterns when building interfaces so new screens stay visually consistent with enterprise Fusion standards.
Who is it for?
Developers building Equinor Fusion-based enterprise web apps who need token and component consistency.
Skip if: Projects outside the Equinor Fusion ecosystem or greenfield apps using unrelated design systems like Material UI.
When should I use this skill?
Building or refactoring UI that must follow Equinor Fusion tokens, components, and patterns.
What you get
Fusion-compliant screens using design tokens, standard components, and documented layout patterns.
Files
Fusion
Main gate. Identify intent, route to the right Fusion skill.
Requires `fusion-skills` for skill lifecycle operations. If fusion-skills is not installed, suggest: npx -y skills add equinor/fusion-skills fusion-skills
First-contact response
If the user asks "what can you do?" or is clearly exploring for the first time, respond with a brief overview before asking clarifying questions:
"I route you to the right Fusion skill. Currently available:
- Find, install, or manage skills → fusion-skills- Create GitHub issues → fusion-issue-authoring- Solve issues, review PRs, plan tasks → experimental skills (ask me to check availability)
>
Try: 'find me a skill for...' or 'create an issue for...'"
Routing
| Intent | Skill | Status |
|---|---|---|
| Find, install, update, remove, sync, or greenkeep skills | fusion-skills | active |
| Create, author, or improve a skill | fusion-skills | active |
| Inspect a skill for quality issues or report a skill failure | fusion-skills | active |
| Create or update a GitHub issue | fusion-issue-authoring | active |
| Solve / implement a GitHub issue | fusion-issue-solving | experimental |
| Plan or break down an issue into sub-tasks | fusion-issue-task-planning | experimental |
| Address PR review comments | fusion-github-review-resolution | experimental |
| Review a dependency update PR | fusion-dependency-review | experimental |
Loop prevention
This skill is a top-level router. It must never re-route back to itself. If you arrived here from another Fusion skill, do not redirect back to that skill — answer directly or state that the intent is out of scope.
Workflow
1. Identify intent from the user's request. 2. Call mcp_fusion_skills to confirm which skill handles it and whether it is installed.
- If MCP is unavailable: use the routing table above as the sole source of truth. Do not guess or hallucinate skill names.
3. If installed: redirect the user to invoke that skill directly. 4. If not installed but available (active or experimental): name the skill, state what it does in one sentence, note if experimental, and give the install command:
npx -y skills add equinor/fusion-skills <skill-name>5. If the skill is experimental: add a note: "This skill is experimental and may change. Install at your own risk." 6. If intent doesn't match any routing entry: say so and suggest the user describe their goal differently, or use fusion-skills discovery to search for a matching skill. 7. If intent is still unclear after reading the request, ask one conversational question:
"Are you looking to manage skills, create an issue, work on an issue, or review a PR?"
Safety
- No secrets or credentials.
- No GitHub mutations without confirmation.
- No remote script execution.
- No invented skill names.
Changelog
0.1.0 - 2026-03-21
minor
Introduces skills/fusion as the universal cross-domain router. Routes any Fusion-related request to the right installed skill: fusion-skills (skill lifecycle), fusion-issue-authoring, fusion-issue-solving, fusion-issue-task-planning, fusion-github-review-resolution, fusion-dependency-review. Includes status column (active/experimental), loop prevention, first-contact response, and MCP fallback guidance.
Related to: equinor/fusion-core-tasks#470
Related skills
FAQ
What does the fusion skill enforce?
The fusion skill enforces Equinor Fusion design system tokens, components, and patterns when building interfaces. equinor/fusion-skills keeps new screens visually aligned with enterprise Fusion standards instead of custom one-off styling.
When should developers use the fusion skill?
Developers should use the fusion skill when implementing Equinor Fusion-based web UI that must match official tokens and components. The skill fits frontend build work requiring design system compliance.