JoinQuant Skill

Generate quantitative strategy code that runs on the JoinQuant platform without modification.

When to Use This Skill

Yes:

• Stock backtest / paper trading / live trading on JoinQuant (聚宽)
• ETF rotation, multi-factor stock selection, momentum, mean reversion strategies
• Futures (期货) strategies on JoinQuant
• Margin trading (融资融券) strategies
• Strategy code review / lint to catch hallucinated APIs and future-function violations
• Translating a strategy idea into JoinQuant API calls

No:

• Local data analysis without JoinQuant (use jqdatasdk directly, or pandas/numpy)
• Strategy backtesting on other platforms (vectorbt, backtrader, vn.py — use those skills instead)
• Pure machine learning model training (no JoinQuant-specific API needed)
• Live trading on broker APIs other than JoinQuant simulated trading (CTP, Interactive Brokers, etc. need different skills)

Default Mode

Most user requests fall into one of three patterns. Detect the pattern first, then route:

Progressive Disclosure: 14 API Categories

DO NOT load all references at once (294KB total, would burn context). Pattern-match the user request and load only the relevant category file:

If the user mentions a function name not in any keyword list, use scripts/api_search.py <keyword> to find it across all references.

Templates

5 production-ready templates in templates/:

When generating code, start from a template, modify, do not write from scratch. Reasons:

1. Templates already include the boilerplate (set_benchmark, set_option, set_order_cost, set_slippage)
2. Templates have correct timing (run_daily / run_weekly with proper time arg)
3. Templates avoid future-function pitfalls (count-based instead of date-based slicing)

Lint Tool

Before returning generated code to user, mentally (or actually) run strategy_lint.py:

python scripts/strategy_lint.py <user_strategy.py>

Critical checks:

• ❌ Hallucinated API calls (e.g., jqdata.get_stock_data() doesn't exist)
• ❌ Future function: using non-count get_price or attribute_history with hardcoded future dates
• ❌ Missing set_option('use_real_price', True) (mandatory for accurate backtest)
• ❌ Missing set_order_cost(...) and set_slippage(...)
• ❌ Order placed in before_trading_start / after_trading_end (forbidden, will be rejected)
• ❌ Use of deprecated APIs (update_universe etc.)
• ⚠️ Recommend g. global vars for state across bars instead of module globals
• ⚠️ Recommend cluster-aware sizing for high-correlation assets

Things That Must Survive Generation

When advising on a strategy, never lose:

• Always set use_real_price=True. Traditional pre-adjusted price has future-function bias. This is non-negotiable.
• set_order_cost and set_slippage are mandatory. Without them, backtest is unrealistic and will mislead the user.
• run_daily time argument matters. 'open' runs at 09:30, 'every_bar' runs every bar (minute or daily). Wrong choice causes wrong execution timing.
• g. is the only safe global state. Module-level globals can leak across runs in some JoinQuant environments.
• order_value > order for capital management. Computing share count manually is error-prone with stock splits.
• order_target_value for rebalancing, never compute "current value - target value" yourself.
• Don't pip install anything inside JoinQuant. The platform is sandboxed; only its preinstalled libraries work.

Workflow

A typical end-to-end strategy session:

1. User describes idea in natural language
2. AI: pick matching template (e.g., 03-etf-rotation.py)
3. AI: ask 2-3 clarifying questions:
   - 标的池范围（指数成分 / 自定义列表）
   - 调仓频率（日 / 周 / 月）
   - 风险控制（止损 / 仓位上限 / 行业中性）
4. AI: generate strategy code modifying template
5. AI: run mental lint (or actual) — fix issues
6. User: paste into JoinQuant online editor, click 编译运行
7. If errors: re-load relevant references/XX-*.md, fix
8. User: review backtest curve, iterate

For high-stakes (live trading) strategies, additionally:

• Reference references/14-strategy-engine.md for slippage, commission, risk metrics
• Reference references/11-margin-trading.md if leverage involved
• Discuss model risk explicitly (overfitting, regime change, transaction cost realism)

Files