apex-rithmic-trading_skill

Overview

This skill enforces Apex Trader Funding account compliance and optimizes Rithmic data feed handling for NinjaTrader 8 automated systems. It implements real-time daily loss limits, trailing drawdown protection, order rate-limiting, disconnect detection, and execution quality monitoring. The goal is to keep funded accounts within strict rules while preserving execution reliability for MES/MGC strategies.

How this skill works

The skill monitors executions, account equity, and market ticks to enforce hard limits (daily loss, trailing drawdown) and to pause or flatten positions when rules are breached. It rate-limits order modifications, tracks order lifecycle timing for latency and slippage metrics, and watches Rithmic tick frequency and last-tick timestamps to detect disconnects and trigger recovery procedures. Per-account tracking supports safe scaling across multiple funded accounts.

When to use it

• Running automated NinjaTrader 8 strategies on Apex Trader Funding accounts.
• You need continuous enforcement of daily loss and trailing drawdown rules.
• When using Rithmic for real-time data and needing disconnect or low-tick detection.
• Implementing strict order modification limits or per-order rate control.
• Scaling from one funded account to multiple accounts with independent limits.

Best practices

• Reset daily P&L at 00:00 ET and stop trading if losses approach 80% of the limit as a safety buffer.
• Track account peak equity for trailing drawdown and lock trading immediately if the drawdown threshold is reached.
• Enforce a minimum 1000 ms gap between order modifications and track rate-limits per order.
• Pause new entries and flatten risky positions on Rithmic disconnects; only resume when tick flow is stable (e.g., >= 10 ticks/min immediately after reconnect).
• Monitor fill latency and slippage thresholds; flag fills >500 ms or slippage >3 ticks for investigation.

Example use cases

• Auto-closing positions and disabling strategy when daily loss limit is hit during the session.
• Detecting Rithmic disconnects and executing a safe recovery: close positions, disable entries, wait for stable tick flow before resuming.
• Rate-limiting stop/limit updates in a high-frequency entry logic to comply with modification rules.
• Measuring fill latency and slippage to identify execution regressions after infrastructure changes.
• Managing multiple Apex accounts with per-account limits and a combined risk dashboard before scaling.