Fusion Backend Consumption
When to use
Use when needing to understand Fusion backend services, available APIs, integration patterns, or architectural decisions.
Typical triggers:
- "How do I call the People API?"
- "Show an example of how the authorization pattern works"
- "What's the contract for the Org service?"
- "How do services handle validation errors?"
- "What async/messaging patterns does Fusion use?"
- "Can I see a reference implementation of a CQRS handler?"
- "How do services integrate with external APIs?"
- "What authentication/authorization requirements do I need?"
- "Show how events flow through the system"
- "What's the pattern for cross-service calls?"
- "How should I structure my API client?"
- "Where should I call the Context API?"
- "What's the difference between a command and a query in Fusion?"
Implicit triggers:
- Building frontend/client app needing to understand backend contracts
- Integrating with Fusion APIs and need patterns
- Designing architecture needing backend best practices
- Learning from existing Fusion service implementations
When not to use
- Creating or modifying backend services — use service-specific repo skill
- Adding new endpoints or API operations — backend development
- Database schema changes or migrations — backend development
- Authorization requirement definitions — backend development (this skill shows what exists, not new requirements)
- Pure architecture discussions without code references — use
fusion-research or ADR-focused skills
- Selecting between Fusion Framework alternatives — use
fusion-research or fusion-app-react-dev
Required inputs
Mandatory
- What you're trying to do: clear description of integration point, use case, or pattern
- Your role/context: building a frontend app? Integrating externally? Designing architecture?
Conditional
- When comparing patterns: which two options you're deciding between
- When consuming an API: what operation/scenario (CRUD, async, real-time, etc.)
- When integrating: external system name and direction of flow (calling out vs being called)
Instructions
Step 1 — Clarify consumption context
Before searching for code, understand what you need:
- Integration point: Calling a backend API? Reading event messages? Implementing a webhook? Integrating with external system?
- Your boundaries: Frontend developer? Backend developer in another service? External integrator? Architect?
- Scope: Single API contract? Full pattern? Reference implementation? Architectural tradeoffs?
Use assets/follow-up-questions.md if user intent is unclear.
Step 2 — Search for reference implementation
Use mcp_fusion_search_backend_code to locate existing patterns:
- Call with high-level intent: "How People service exposes authorization" or "Cross-service API integration patterns"
- Start with
top: 3-5 results
- Capture
metadata.repository, metadata.service, metadata.filePath
- Extract minimal code snippets showing the pattern (method signature, type contract, authorization check)
- If results are unclear, refine once:
- Add specific service name or interface
- Narrow to specific layer (controller, handler, client interface)
- Try a different phrase focusing on outcome rather than implementation details
Step 3 — Explain the pattern
Use evidence from Step 2:
- State the pattern clearly: What does the service do? What contract does it expose?
- Show the reference code: Quote relevant snippet with file path and line range
- Explain the constraints: Preconditions? Authorization? Error handling? Async behavior?
- Relate to your use case: How to apply this pattern?
- Surface tradeoffs or alternatives if they exist
Step 4 — Verify completeness
Before ending, check:
If uncertainty remains, flag it explicitly.
Reference guides
See references/ for deeper pattern documentation:
api-contracts.md — Fusion service API contracts and versioning
authorization-patterns.md — Authentication, authorization requirements, role-based access
validation-patterns.md — Input validation, error responses, business rules
async-patterns.md — Events, service bus, domain notifications, eventual consistency
integration-patterns.md — Cross-service calls, external APIs, webhook handling
cqrs-reference.md — CQRS handlers, commands, queries, notifications structure
Assets
assets/follow-up-questions.md — Clarifying questions for ambiguous requests
references/integration-patterns.md — Common integration scenarios and which patterns apply
Safety & constraints
Never:
- Describe real backend API behavior as fact unless verifiable in retrieved source code or cited repo docs
- Claim a pattern exists when search returns no evidence
- Present illustrative pseudo-code as retrieved source code
- Suggest modifying a backend service — that's out of scope
Always:
- Label illustrative examples as examples/pseudo-code when explanatory rather than retrieved
- Capture and cite repository, file path, and line references for real code
- State which repository the pattern comes from
- Note when a pattern exists in one service but not others
- Offer to escalate to the
fusion-services-developer agent if user wants to implement changes
- For setting up or deploying a new standalone backend API (app registration, Roles V2, database, Radix/Kubernetes deployment, observability), point to the New Backend Service Checklist on fusion-docs rather than improvising the sequence
1---2name: fusion-backend-dev3description: 'Guides consumption and understanding of Fusion backend services, APIs, and patterns for frontend/client developers, integrators, and architects. Shows reference implementations, explains architectural decisions, and clarifies contracts. USE FOR: understanding Fusion backend APIs, learning implementation patterns, exploring reference code, choosing the right integration point, and understanding authorization/validation/async patterns. DO NOT USE FOR: modifying backend services, creating new endpoints, database changes, or backend-specific development (use the fusion-services-developer agent or the target backend service repo instead).'4license: MIT5compatibility: Works best with Fusion MCP. Works best with mcp_fusion_search_backend_code for reference code discovery. Frontend/client developers should also install fusion-research for deeper architectural context.6metadata:7 source: https://skillmd.com/skills/equinor/fusion-backend-dev8 version: "0.1.3"9 status: active10 owner: "@equinor/fusion-core"11 skills:12 - fusion-research13 - fusion-code-conventions14 - fusion-devtools15 tags:16 - fusion-backend17 - api-consumption18 - patterns19 - architecture20 - reference-implementation21 - csharp22 mcp:23 suggested:24 - mcp_fusion_search_backend_code25---2627# Fusion Backend Consumption2829## When to use3031Use when needing to understand Fusion backend services, available APIs, integration patterns, or architectural decisions.3233Typical triggers:34- "How do I call the People API?"35- "Show an example of how the authorization pattern works"36- "What's the contract for the Org service?"37- "How do services handle validation errors?"38- "What async/messaging patterns does Fusion use?"39- "Can I see a reference implementation of a CQRS handler?"40- "How do services integrate with external APIs?"41- "What authentication/authorization requirements do I need?"42- "Show how events flow through the system"43- "What's the pattern for cross-service calls?"44- "How should I structure my API client?"45- "Where should I call the Context API?"46- "What's the difference between a command and a query in Fusion?"4748Implicit triggers:49- Building frontend/client app needing to understand backend contracts50- Integrating with Fusion APIs and need patterns51- Designing architecture needing backend best practices52- Learning from existing Fusion service implementations5354## When not to use5556- **Creating or modifying backend services** — use service-specific repo skill57- **Adding new endpoints or API operations** — backend development58- **Database schema changes or migrations** — backend development59- **Authorization requirement definitions** — backend development (this skill shows what exists, not new requirements)60- **Pure architecture discussions without code references** — use `fusion-research` or ADR-focused skills61- **Selecting between Fusion Framework alternatives** — use `fusion-research` or `fusion-app-react-dev`6263## Required inputs6465### Mandatory6667- **What you're trying to do**: clear description of integration point, use case, or pattern68- **Your role/context**: building a frontend app? Integrating externally? Designing architecture?6970### Conditional7172- When comparing patterns: which two options you're deciding between73- When consuming an API: what operation/scenario (CRUD, async, real-time, etc.)74- When integrating: external system name and direction of flow (calling out vs being called)7576## Instructions7778### Step 1 — Clarify consumption context7980Before searching for code, understand what you need:81821. **Integration point**: Calling a backend API? Reading event messages? Implementing a webhook? Integrating with external system?832. **Your boundaries**: Frontend developer? Backend developer in another service? External integrator? Architect?843. **Scope**: Single API contract? Full pattern? Reference implementation? Architectural tradeoffs?8586Use `assets/follow-up-questions.md` if user intent is unclear.8788### Step 2 — Search for reference implementation8990Use `mcp_fusion_search_backend_code` to locate existing patterns:91921. Call with high-level intent: "How People service exposes authorization" or "Cross-service API integration patterns"932. Start with `top: 3-5` results943. Capture `metadata.repository`, `metadata.service`, `metadata.filePath`954. Extract minimal code snippets showing the pattern (method signature, type contract, authorization check)965. If results are unclear, refine once:97 - Add specific service name or interface98 - Narrow to specific layer (controller, handler, client interface)99 - Try a different phrase focusing on outcome rather than implementation details100101### Step 3 — Explain the pattern102103Use evidence from Step 2:1041051. **State the pattern clearly**: What does the service do? What contract does it expose?1062. **Show the reference code**: Quote relevant snippet with file path and line range1073. **Explain the constraints**: Preconditions? Authorization? Error handling? Async behavior?1084. **Relate to your use case**: How to apply this pattern?1095. **Surface tradeoffs or alternatives** if they exist110111### Step 4 — Verify completeness112113Before ending, check:114115- [ ] User understands the contract (inputs, outputs, errors)116- [ ] User sees a real code reference (not invented)117- [ ] User knows where the code lives (repository, service, file path)118- [ ] User knows prerequisites (authentication, configuration, dependencies)119- [ ] User has enough context to implement or integrate120121If uncertainty remains, flag it explicitly.122123## Reference guides124125See `references/` for deeper pattern documentation:126127- `api-contracts.md` — Fusion service API contracts and versioning128- `authorization-patterns.md` — Authentication, authorization requirements, role-based access129- `validation-patterns.md` — Input validation, error responses, business rules130- `async-patterns.md` — Events, service bus, domain notifications, eventual consistency131- `integration-patterns.md` — Cross-service calls, external APIs, webhook handling132- `cqrs-reference.md` — CQRS handlers, commands, queries, notifications structure133134## Assets135136- `assets/follow-up-questions.md` — Clarifying questions for ambiguous requests137- `references/integration-patterns.md` — Common integration scenarios and which patterns apply138139## Safety & constraints140141Never:142- Describe real backend API behavior as fact unless verifiable in retrieved source code or cited repo docs143- Claim a pattern exists when search returns no evidence144- Present illustrative pseudo-code as retrieved source code145- Suggest modifying a backend service — that's out of scope146147Always:148- Label illustrative examples as examples/pseudo-code when explanatory rather than retrieved149- Capture and cite repository, file path, and line references for real code150- State which repository the pattern comes from151- Note when a pattern exists in one service but not others152- Offer to escalate to the `fusion-services-developer` agent if user wants to implement changes153- For setting up or deploying a new standalone backend API (app registration, Roles V2, database, Radix/Kubernetes deployment, observability), point to the [New Backend Service Checklist](https://docs.fusion.equinor.com/docs/developer/api/new-service-checklist) on fusion-docs rather than improvising the sequence