role-trading-architect

Design trading system architectures with order state machines and risk gateways.

Updated Jan 30, 2026
One-click install
npx skills add https://github.com/ChoiHyunjin/ai_skills --skill role-trading-architect
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: role-trading-architect
Source: https://github.com/ChoiHyunjin/ai_skills/tree/main/skills/role-trading-architect
Command: npx skills add https://github.com/ChoiHyunjin/ai_skills --skill role-trading-architect

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enables the design of robust and reliable trading system architectures, addressing the critical need for accuracy and reliability in financial systems.

Core Features & Use Cases

  • Trading System Design: Architectures for order state machines, risk gateways, event sourcing, and strategy-execution separation.
  • Domain-Specific Principles: Incorporates principles crucial for trading systems like fixed-point arithmetic for money, robust dependency management, and explicit order state transitions.
  • Use Case: Design the architecture for a new high-frequency trading platform, ensuring all components adhere to strict reliability and performance requirements.

Quick Start

Design the architecture for a trading system focusing on the order state machine and risk gateway.

Frequently Asked Questions about role-trading-architect

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

FAQPage Schema
How do I design a trading system architecture with an order state machine and risk gateway?

Designing a trading system architecture involves defining explicit order state transitions, implementing a risk gateway for validation, and separating strategy execution from order management to ensure high reliability and correctness.

What is event sourcing in financial trading systems?

Event sourcing in financial trading systems is an architectural pattern that logs explicit state transitions as a sequence of events, enabling robust order lifecycle management and separate read/write paths for accurate processing.

Why use fixed-point arithmetic in trading system design?

Fixed-point arithmetic is used in trading system design to prevent rounding errors and ensure strict accuracy in financial calculations, which is a critical domain-specific principle for high-reliability order management.

How do you separate strategy execution from order management in a trading platform?

You separate strategy execution from order management by isolating decision logic in a strategy layer and routing orders through a dedicated state machine and risk gateway, ensuring correctness and high reliability.

Can this trading system architecture handle high-frequency trading platforms?

Yes, this trading system architecture applies to high-frequency trading platforms, ensuring all components adhere to strict reliability, event-driven processing, and performance requirements for financial trading domains.

What are the limitations of using event sourcing for order lifecycle management?

Event sourcing for order lifecycle management requires explicit state logging and separate read/write paths, adding architectural complexity to the trading system design while ensuring high reliability and correctness.