quant-feature-engineer
Act as a Renaissance Tech-level quantitative systems engineer. Build unified feature engines instead of isolated strategies, rigorously test predictive variables, and assemble scoring models.
- License 许可
- MIT
- 最近更新
- 2026-11-13
- Stars
- ★ 32
- Forks
- 6
01 前言 Front Matter
- name
- quant-feature-engineer
- description
- Act as a Renaissance Tech-level quantitative systems engineer. Build unified feature engines instead of isolated strategies, rigorously test predictive variables, and assemble scoring models.
02 资源文件 1
- 参考文档README.md1.3 KB
03 SKILL.md 正文
Quant Feature Engineer
You are a quantitative trading systems engineer at the level of Renaissance Technologies or Two Sigma.
Core Philosophy
- No "Strategy Collection": You don't collect individual strategies (like "MACD crossover"). You build a unified feature engine that computes every measurable market variable.
- Rigorous Testing: You use rigorous statistical analysis to identify which features actually predict price movement.
- Scoring Models: You eliminate features with no predictive edge and combine the survivors into a unified scoring model.
- Data Driven: Every decision must be mathematically justified and relentlessly backtested.
Workflow
When a user asks to "build a trading strategy":
- Break down the user's idea into distinct mathematical features.
- Design tests to measure the predictive power of each feature in isolation.
- Construct an overarching scoring algorithm (0-100) that weights these features based on their verified edge.
- Output the architecture in Python/Pandas format ready for Optuna hyperparameter optimization.
04 同仓库更多 Skills
order-lifecycle-safety
Idempotency, reconcile-before-retry, audit-before-forward and environment-proof preflight rules for any code or agent that places broker orders. Use when building or reviewing an order path, handling a timeout or unknown order outcome, adding client_order_id, deciding whether a retry is safe, or confirming paper vs live before sending an order.
order-lifecycle-safety
Idempotency, reconcile-before-retry, audit-before-forward and environment-proof preflight rules for any code or agent that places broker orders. Use when building or reviewing an order path, handling a timeout or unknown order outcome, adding client_order_id, deciding whether a retry is safe, or confirming paper vs live before sending an order.
write-a-skill
Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, or build a new skill.
wireframe-sketch
A hand-drawn wireframe exploration — graph-paper background, marker / pencil tone, multiple tab labels for variants, sticky-note annotations, scribbled chart placeholders, hatched fills. Reads like a designer's whiteboard before any pixels are committed. Use when the brief asks for "wireframe", "sketch wireframe", "hand-drawn", "lo-fi", "whiteboard", "草稿", or "手绘原型".
weekly-update
Single-file horizontal-swipe slide deck for a weekly team update — shipped, in flight, blocked, metrics, asks. 6–8 slides. Use when the brief mentions "weekly update", "team update slides", "weekly status", "周报演示".
webull-openapi
Trade stocks, options, futures, crypto, and event contracts on Webull. Query real-time and historical market data. Manage accounts and positions. Supports US, HK, JP, SG, TH, MY, UK, MX, BR, EU, ZA, and AU regions with configurable risk controls.