Files
BrainBytesandClaude Opus 4.6 9a8fcfcaac feat: Everything Claude Trading v1.0.0
The complete trading and quantitative finance system for Claude Code.

- 18 specialized agents (quant-researcher, algo-strategist, risk-manager, derivatives-analyst, etc.)
- 82 domain skills across 10 categories (quant methods, strategies, risk, derivatives, portfolio, execution, data, crypto, macro, backtesting)
- 20 slash commands for trading workflows
- 5 always-active rules (risk limits, data integrity, model governance, regulatory compliance, ethical trading)
- 4 hook scripts (risk check, backtest validation, data quality, session start)
- 3 context modes (research, live-trading, backtesting)
- 3 example configs (quant fund, crypto trader, retail algo)
- 8 MCP server configurations
- The Complete Guide (setup + advanced patterns)
- Viral-ready README, CONTRIBUTING, CI, PR template

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-03-15 00:26:54 +01:00

3.3 KiB

description
description
Design a systematic trading strategy from concept to implementation

/strategy

What This Command Does

Designs a complete systematic trading strategy including signal generation, entry/exit rules, position sizing, and risk management. The algo-strategist agent leads, pulling in quant-researcher for signal validation and risk-manager for risk assessment when needed.

When to Use

  • You have a trading idea or market hypothesis and want to formalize it into a systematic strategy
  • You need to define entry signals, exit rules, and position sizing for an existing concept
  • You want to evaluate whether a discretionary approach can be systematized
  • You are building a new strategy for a specific asset class, timeframe, or market regime

How It Works

  1. Idea capture — Parses your strategy description, target asset class, timeframe, and objectives.
  2. Signal design — Defines the alpha signal(s) driving the strategy, including data inputs, calculation logic, and expected decay profile.
  3. Rule specification — Produces concrete entry conditions, exit conditions (take-profit, stop-loss, time-based), and position sizing rules.
  4. Risk framework — Specifies maximum drawdown tolerance, position limits, correlation constraints, and portfolio-level risk budget.
  5. Implementation plan — Outputs pseudocode or structured logic suitable for backtesting.

The algo-strategist agent orchestrates the process. If the signal requires statistical validation, it delegates to quant-researcher. If risk constraints need formal modeling, it consults risk-manager.

Example Usage

Input:

/strategy momentum breakout on US large-cap equities, daily timeframe,
long-only, targeting Sharpe > 1.5 after costs

Output:

## Momentum Breakout Strategy — US Large-Cap Equities

### Signal
- 12-month price momentum (skip last month) ranked across S&P 500
- Entry: Top decile momentum score, confirmed by 20-day volume breakout (> 1.5x average)
- Lookback: 252 trading days for momentum, 20 days for volume confirmation

### Entry Rules
- Buy on next open after signal triggers
- Require ADV > $10M for liquidity filter
- Maximum 30 positions at any time

### Exit Rules
- Stop-loss: 8% trailing from peak price
- Time exit: Rebalance monthly, drop stocks falling below top quartile
- Take-profit: None (let winners run within momentum regime)

### Position Sizing
- Equal risk contribution: size inversely proportional to 20-day realized vol
- Target 15bps portfolio risk per position
- Maximum single position: 5% of NAV

### Risk Framework
- Maximum portfolio drawdown: 15%
- Sector concentration limit: 30% in any single GICS sector
- Beta cap: gross portfolio beta < 1.3
- Correlation to benchmark: monitor, target information ratio > 0.8

### Implementation Notes
- Universe: S&P 500 constituents (point-in-time to avoid survivorship bias)
- Data: Adjusted close prices, volume, GICS sector codes
- Rebalance: Monthly, first trading day
- Estimated turnover: ~150% annually
- Transaction cost assumption: 5bps per side
  • algo-strategist — Primary agent, designs the strategy architecture
  • quant-researcher — Validates signal significance and decay characteristics
  • risk-manager — Reviews risk framework and position limits
  • backtesting-engineer — Next step after strategy design (use /backtest)