fusion-backend-dev

Provides backendless API integration guidance from parsed Rust source files and standardized comments.

9|5|Updated Jan 11, 2021
One-click install
npx skills add https://github.com/equinor/fusion-react-components --skill fusion-backend-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fusion-backend-dev
Source: https://github.com/equinor/fusion-react-components/tree/main/.agents/skills/fusion-backend-dev
Command: npx skills add https://github.com/equinor/fusion-react-components --skill fusion-backend-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

It helps you understand how Fusion backend services expose contracts and how their architectural patterns work (authorization, validation, async/eventing) so you can integrate confidently without guessing.

Core Features & Use Cases

  • Reference-driven API understanding: Guides consumption and explains endpoint behavior and expected contracts using evidence from backend source discovery.
  • Pattern explanations with constraints: Covers authorization, validation, error handling, CQRS flow, and async/event patterns with what to verify and what not to assume.
  • Integration guidance for frontend/client and integrators: Helps you choose the correct integration point and apply resilient consumption practices (including event subscription and polling concepts).

Use case example: You need to call the People API and wire it into a frontend; you ask for the right endpoint contract, required authorization scope, and a reference implementation you can mirror in your client.

Quick Start

Use the fusion-backend-dev skill to explain how to consume the People API "get person by id" endpoint, including the authorization scope and a reference code snippet from the Fusion backend repositories.

Frequently Asked Questions about fusion-backend-dev

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I consume Fusion backend APIs and find the correct authorization scope?

To consume Fusion backend APIs, use backend code search to extract endpoint contracts, verify required authorization patterns, and mirror reference implementations from repository source files for your client.

What is the CQRS handler flow in Fusion backend services?

The CQRS handler flow in Fusion backend services separates command and query execution paths. You can understand this pattern by retrieving source code details that show how handlers process commands and return query results.

How do I interpret validation errors returned by Fusion backend APIs?

Interpreting validation errors from Fusion backend APIs requires checking the source code for error handling patterns. The skill guides you to the exact contract definitions and validation logic to ensure accurate client-side error processing.

How do I integrate async events and event subscriptions with Fusion backends?

Integrating async events with Fusion backends involves examining event subscription and polling concepts within the source. The skill helps you choose the correct integration point for resilient async consumption based on backend behavior.

Can I get a reference implementation for structuring a Fusion API client?

You can obtain reference implementations for structuring a Fusion API client by searching backend repositories. The skill extracts code snippets and contract details, providing evidence-based guidance for your frontend integration.

When should I not assume behavior when integrating with Fusion backend services?

You should not assume behavior when integrating with Fusion backend services if the source code lacks explicit evidence. The skill requires citing repository, service, and file paths to verify actual behavior and avoid unsupported claims.