Fusion Research
When to use
Use this skill when a user needs a source-backed answer about the Fusion ecosystem.
Typical triggers:
- "Research this Fusion Framework hook and show me the supporting source."
- "What props does this EDS component accept?"
- "Which skill handles X in a Fusion workflow?"
- "Find a source-backed example for…"
- "Which Fusion package or module owns this API?"
- "Is there an EDS design token for this value?"
- "How can I persist user preferences in a Fusion app?"
- "What's the recommended pattern for X in Fusion?"
- "Show me a Fusion Framework example for building X."
- "What are the design tokens for color and spacing in EDS?"
- "How does Fusion handle X at the platform level?"
- "What is the Fusion platform guidance on Y?"
- "How do I onboard to Fusion?"
- "What are the guidelines for Z in the Fusion platform?"
When not to use
Do not use this skill for:
- implementing code changes — use
fusion-app-react-dev or the relevant dev skill; if the research is for a specific app you are actively building, use fusion-app-react-dev first — it will call this skill when needed
- finding, installing, updating, or removing skills — use
fusion-discover-skills; use this skill only to understand a skill's scope, relationships, or catalog fit — not to discover what to install
- creating or editing skill files — use
fusion-skill-authoring for authoring-time research
- Fusion MCP installation or troubleshooting — use
fusion-mcp; once MCP is running, return here for research
- pure conceptual Fusion questions with no specific artifact name (hook, component, package, token, or platform topic) — ask the user for a concrete artifact reference or platform topic first
Instructions
Step 0 — Sharpen scope (optional)
Before classifying, you may use the domain-specific follow-up questions to narrow the user's exact need:
- Framework scope: assets/framework.follow-up.md
- EDS scope: assets/eds.follow-up.md
- Skills catalog scope: assets/skills.follow-up.md
- Docs scope: assets/docs.follow-up.md
Skip this step if the question already names a specific artifact (hook, component, package, token, or skill).
Step 1 — Classify the research question
Determine which domain the question belongs to:
| Domain |
Indicators |
Agent |
| Framework |
Fusion Framework hooks, packages, modules, TypeScript APIs, cookbook examples |
agents/framework.agent.md |
| EDS |
EDS component props, usage examples, accessibility, design tokens |
agents/eds.agent.md |
| Skills |
Skill catalog lookup, scope boundaries, companion/orchestrator relationships |
agents/skills.agent.md |
| Docs |
Fusion platform concepts, onboarding, platform operations, governance, non-implementation guidance |
agents/docs.agent.md |
| Backend Code |
C# service implementations, interfaces, CQRS patterns, authorization, validation, cross-service APIs |
agents/backend-code.agent.md |
If the question spans multiple domains, answer each domain separately using the appropriate agent in sequence.
Step 2 — Dispatch to the correct agent
- Framework questions → follow
agents/framework.agent.md.
- EDS questions → follow
agents/eds.agent.md.
- Skills questions → follow
agents/skills.agent.md.
- Docs questions → follow
agents/docs.agent.md.
- Backend code questions → follow
agents/backend-code.agent.md.
If the runtime supports skill-local agents, invoke the agent directly. Otherwise, apply the agent's instructions inline.
Step 3 — Return the source-backed answer
Use the structure in assets/source-backed-answer-template.md:
- State which domain and agent was used.
- Include one to three source-backed evidence bullets.
- End with any remaining assumptions, uncertainty, or the next verification step.
Research agents
This skill includes five research agents in agents/. Each covers one Fusion research domain with its own query patterns and evidence checklist.
agents/framework.agent.md — source-backed answers about Fusion Framework hooks, packages, modules, and cookbook examples. Uses mcp_fusion_search_framework.
agents/eds.agent.md — source-backed answers about EDS component props, usage, accessibility, and design tokens. Uses mcp_fusion_search_eds.
agents/skills.agent.md — source-backed answers about the Fusion skill catalog: what skills exist, their scope, and how they relate. Uses mcp_fusion_search_skills.
agents/docs.agent.md — source-backed answers about Fusion platform concepts, onboarding, operations, and governance. Uses mcp_fusion_search_docs.
agents/backend-code.agent.md — source-backed answers about Fusion backend service implementations: C# services, interfaces, CQRS patterns, authorization, and cross-service integrations. Uses mcp_fusion_search_backend_code.
Assets
- assets/source-backed-answer-template.md
- assets/framework.follow-up.md — pre-dispatch scope questions for Framework research
- assets/eds.follow-up.md — pre-dispatch scope questions for EDS research
- assets/skills.follow-up.md — pre-dispatch scope questions for skills catalog research
- assets/docs.follow-up.md — pre-dispatch scope questions for Docs platform research
Safety & constraints
Never:
- invent Fusion Framework hooks, EDS props, or skill catalog entries
- claim evidence exists when MCP is unavailable or results are weak
- keep refining indefinitely — state uncertainty after one refinement pass per agent
- implement code changes or mutate repositories during a research flow
Always:
- classify the question before choosing an agent
- capture the source path and supporting excerpt before finalizing any claim
- state explicitly which agent and source backed each part of the answer
1---2name: fusion-research3description: 'Source-backed research orchestrator for the Fusion ecosystem. Routes to the correct research agent based on question type. Returns source-backed evidence only; will not invent Framework behavior, component APIs, skill catalog relationships, platform guidance, or backend implementation details. USE FOR: any research question needing source-backed evidence about Fusion Framework APIs, EDS components, the Fusion skill catalog, Fusion platform documentation, or backend service implementation. DO NOT USE FOR: implementing code changes, installing or editing skills, MCP setup or troubleshooting, or inventing Fusion behavior without evidence.'4license: MIT5compatibility: Works best with Fusion MCP. Dispatches to `agents/framework.agent.md` for `mcp_fusion_search_framework`, `agents/eds.agent.md` for `mcp_fusion_search_eds`, `agents/skills.agent.md` for `mcp_fusion_search_skills`, `agents/docs.agent.md` for `mcp_fusion_search_docs`, and `agents/backend-code.agent.md` for `mcp_fusion_search_backend_code`. If MCP is unavailable, state that clearly rather than guessing.6metadata:7 source: https://skillmd.com/skills/equinor/fusion-research8 version: "0.4.1"9 status: experimental10 owner: "@equinor/fusion-core"11 tags:12 - fusion13 - research14 - mcp15 - evidence16 - framework17 - eds18 - skills19 - docs20 - backend21 - csharp22 - services23 - platform-guidance24 mcp:25 suggested:26 - mcp_fusion_search_framework27 - mcp_fusion_search_eds28 - mcp_fusion_search_docs29 - mcp_fusion_search_skills30 - mcp_fusion_search_backend_code31 - mcp_fusion_skills32---3334# Fusion Research3536## When to use3738Use this skill when a user needs a source-backed answer about the Fusion ecosystem.3940Typical triggers:41- "Research this Fusion Framework hook and show me the supporting source."42- "What props does this EDS component accept?"43- "Which skill handles X in a Fusion workflow?"44- "Find a source-backed example for…"45- "Which Fusion package or module owns this API?"46- "Is there an EDS design token for this value?"47- "How can I persist user preferences in a Fusion app?"48- "What's the recommended pattern for X in Fusion?"49- "Show me a Fusion Framework example for building X."50- "What are the design tokens for color and spacing in EDS?"51- "How does Fusion handle X at the platform level?"52- "What is the Fusion platform guidance on Y?"53- "How do I onboard to Fusion?"54- "What are the guidelines for Z in the Fusion platform?"5556## When not to use5758Do not use this skill for:59- implementing code changes — use `fusion-app-react-dev` or the relevant dev skill; if the research is for a specific app you are actively building, use `fusion-app-react-dev` first — it will call this skill when needed60- finding, installing, updating, or removing skills — use `fusion-discover-skills`; use this skill only to understand a skill's scope, relationships, or catalog fit — not to discover what to install61- creating or editing skill files — use `fusion-skill-authoring` for authoring-time research62- Fusion MCP installation or troubleshooting — use `fusion-mcp`; once MCP is running, return here for research63- pure conceptual Fusion questions with no specific artifact name (hook, component, package, token, or platform topic) — ask the user for a concrete artifact reference or platform topic first6465## Instructions6667### Step 0 — Sharpen scope (optional)6869Before classifying, you may use the domain-specific follow-up questions to narrow the user's exact need:70- Framework scope: [assets/framework.follow-up.md](assets/framework.follow-up.md)71- EDS scope: [assets/eds.follow-up.md](assets/eds.follow-up.md)72- Skills catalog scope: [assets/skills.follow-up.md](assets/skills.follow-up.md)73- Docs scope: [assets/docs.follow-up.md](assets/docs.follow-up.md)7475Skip this step if the question already names a specific artifact (hook, component, package, token, or skill).7677### Step 1 — Classify the research question7879Determine which domain the question belongs to:8081| Domain | Indicators | Agent |82| --- | --- | --- |83| **Framework** | Fusion Framework hooks, packages, modules, TypeScript APIs, cookbook examples | [`agents/framework.agent.md`](agents/framework.agent.md) |84| **EDS** | EDS component props, usage examples, accessibility, design tokens | [`agents/eds.agent.md`](agents/eds.agent.md) |85| **Skills** | Skill catalog lookup, scope boundaries, companion/orchestrator relationships | [`agents/skills.agent.md`](agents/skills.agent.md) |86| **Docs** | Fusion platform concepts, onboarding, platform operations, governance, non-implementation guidance | [`agents/docs.agent.md`](agents/docs.agent.md) |87| **Backend Code** | C# service implementations, interfaces, CQRS patterns, authorization, validation, cross-service APIs | [`agents/backend-code.agent.md`](agents/backend-code.agent.md) |8889If the question spans multiple domains, answer each domain separately using the appropriate agent in sequence.9091### Step 2 — Dispatch to the correct agent9293- Framework questions → follow [`agents/framework.agent.md`](agents/framework.agent.md).94- EDS questions → follow [`agents/eds.agent.md`](agents/eds.agent.md).95- Skills questions → follow [`agents/skills.agent.md`](agents/skills.agent.md).96- Docs questions → follow [`agents/docs.agent.md`](agents/docs.agent.md).97- Backend code questions → follow [`agents/backend-code.agent.md`](agents/backend-code.agent.md).9899If the runtime supports skill-local agents, invoke the agent directly. Otherwise, apply the agent's instructions inline.100101### Step 3 — Return the source-backed answer102103Use the structure in [assets/source-backed-answer-template.md](assets/source-backed-answer-template.md):104- State which domain and agent was used.105- Include one to three source-backed evidence bullets.106- End with any remaining assumptions, uncertainty, or the next verification step.107108## Research agents109110This skill includes five research agents in `agents/`. Each covers one Fusion research domain with its own query patterns and evidence checklist.111112- **[`agents/framework.agent.md`](agents/framework.agent.md)** — source-backed answers about Fusion Framework hooks, packages, modules, and cookbook examples. Uses `mcp_fusion_search_framework`.113- **[`agents/eds.agent.md`](agents/eds.agent.md)** — source-backed answers about EDS component props, usage, accessibility, and design tokens. Uses `mcp_fusion_search_eds`.114- **[`agents/skills.agent.md`](agents/skills.agent.md)** — source-backed answers about the Fusion skill catalog: what skills exist, their scope, and how they relate. Uses `mcp_fusion_search_skills`.115- **[`agents/docs.agent.md`](agents/docs.agent.md)** — source-backed answers about Fusion platform concepts, onboarding, operations, and governance. Uses `mcp_fusion_search_docs`.116- **[`agents/backend-code.agent.md`](agents/backend-code.agent.md)** — source-backed answers about Fusion backend service implementations: C# services, interfaces, CQRS patterns, authorization, and cross-service integrations. Uses `mcp_fusion_search_backend_code`.117118## Assets119120- [assets/source-backed-answer-template.md](assets/source-backed-answer-template.md)121- [assets/framework.follow-up.md](assets/framework.follow-up.md) — pre-dispatch scope questions for Framework research122- [assets/eds.follow-up.md](assets/eds.follow-up.md) — pre-dispatch scope questions for EDS research123- [assets/skills.follow-up.md](assets/skills.follow-up.md) — pre-dispatch scope questions for skills catalog research124- [assets/docs.follow-up.md](assets/docs.follow-up.md) — pre-dispatch scope questions for Docs platform research125126## Safety & constraints127128Never:129- invent Fusion Framework hooks, EDS props, or skill catalog entries130- claim evidence exists when MCP is unavailable or results are weak131- keep refining indefinitely — state uncertainty after one refinement pass per agent132- implement code changes or mutate repositories during a research flow133134Always:135- classify the question before choosing an agent136- capture the source path and supporting excerpt before finalizing any claim137- state explicitly which agent and source backed each part of the answer