skills.rest
luifertorres
luifertorresCOMMUNITY
Explore all skills by this author →
𝕏@luifertorresGitHub

binance-net

Enforces Binance.Net types and clients for USD-M Futures REST and WebSocket integrations.

1|Updated Nov 3, 2023
Search Tags:#integration#infrastructure#dotnet#exchange-api#binance#binance-net#usd-futures
One-click install
npx skills add https://github.com/luifertorres/trading-assistant --skill binance-net
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: binance-net
Source: https://github.com/luifertorres/trading-assistant/tree/main/.cursor/skills/binance-net
Command: npx skills add https://github.com/luifertorres/trading-assistant --skill binance-net

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures consistent and correct use of the Binance.Net framework across the trading-assistant codebase to avoid duplicated DTOs, mismatched client usage, and fragmented exchange integrations.

Core Features & Use Cases

  • Framework stance: Directs implementers to use IBinanceRestClient, IBinanceSocketClient, UsdFuturesApi and API-shaped types such as BinanceFuturesUsdtSymbol rather than inventing parallel exchange DTOs.
  • Architecture guidance: Specifies where mapping into Domain or through Application interfaces is appropriate and mandates preferring IExchangeService for host/strategy interactions.
  • Use Case: When adding or updating USD‑M Futures REST or WebSocket code, follow these patterns to align package versions, reuse BinanceService patterns (GetExchangeInfoAsync, GetResultOrError), and keep Backtesting MVP usage consistent.

Quick Start

Use the binance-net guidance to implement Binance.Net types and clients in Infrastructure adapters and map exchange DTOs only into Domain or Application interfaces for USD-M Futures.

Frequently Asked Questions about binance-net

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

FAQPage Schema
How do I standardize Binance .NET integration for USD-M Futures REST and WebSocket clients?▼

To standardize Binance .NET integration, enforce the use of IBinanceRestClient, IBinanceSocketClient, and UsdFuturesApi types across your codebase. This ensures consistent USD-M Futures REST and WebSocket implementations by reusing BinanceService patterns like GetExchangeInfoAsync.

What is the correct architecture for mapping Binance.Net exchange DTOs in a .NET trading application?▼

The correct architecture for mapping Binance.Net exchange DTOs is to map them exclusively into Domain or Application boundaries. You should prefer IExchangeService for host and strategy interactions, preventing fragmented exchange integrations and duplicated DTOs.

Do I need to use specific Binance.Net types like BinanceFuturesUsdtSymbol when adding exchange information code?▼

Yes, when adding exchange information code, you must use API-shaped types such as BinanceFuturesUsdtSymbol rather than inventing parallel exchange DTOs. This aligns package versions and ensures correct handling of klines and filters.

How do I implement Binance .NET adapters for a Backtesting MVP scenario?▼

To implement Binance .NET adapters for a Backtesting MVP, use Binance.Net types and clients within Infrastructure adapters. You must apply GetResultOrError patterns and map the exchange DTOs only into Domain or Application interfaces to keep usage consistent.

Why does my Binance .NET integration have mismatched client usage and fragmented exchange connections?▼

Binance .NET integration becomes mismatched and fragmented when developers invent parallel exchange DTOs instead of using Binance.Net types. Enforcing IBinanceRestClient and IBinanceSocketClient via an IExchangeService interface eliminates these inconsistencies.

Related Skills

Explore More Software Engineering Skills→
pohlai88pohlai88

pnpm-workspace

Define pnpm-workspace.yaml and link local packages with the workspace protocol.

Community
Intermediate
nirholasnirholas
71

binance-futures

Automate Binance Futures trading with local database tracking for positions and trades.

Community
Advanced
baphledbaphled
1

service-layer

Design application services for business logic orchestration and transaction management.

Community
Intermediate
HouseGarofaloHouseGarofalo
3

browserless

Automate headless Chrome browser tasks via REST API and WebSocket.

Official
Intermediate