菜单
Analyze Volatio debug logs from /tmp/volatio-debug/. Use when the user asks to check debug logs, analyze problems, or diagnose simulation issues.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Market data integrity rules — gap filling, look-forward bias prevention, and stock split handling. Use when writing or reviewing code that loads prices, fills missing data, computes returns, backtests strategies, or makes trading decisions. Applies across Python, TypeScript, SQL, and TimescaleDB.
Apply bottom-up systematic testing to a multi-layer system. Use when asked to test, debug, or verify a pipeline that spans multiple layers (e.g., Python worker → bridge → processor → API → UI).
Drizzle Kit workflow for Volatio using idempotent migrations (generate + edit + migrate), never use push. Idempotent patterns prevent partial failure issues, enable safe re-runs, and work cleanly in CI. Use when schema changes, migration errors, or database sync issues occur.
Template for creating Volatio research experiments with Optuna optimization and portfolio backtesting. Includes proper train/test splits, lookahead bias prevention, results saving, and validated patterns from Exp 051-053.
Financial research look-ahead bias verification for Volatio ML pipelines, mandatory baseline comparisons, timezone handling, feature leakage detection. Use when model accuracy seems too good or validating prediction experiments.
Creating PROGRESSION.md documents for research experiment series in Volatio. Captures the evolution of ideas, learnings, and breakthroughs across numbered experiments (001, 002, ...). Use when documenting experiment series or reviewing research evolution.
基于 SOC 职业分类
| name | debug-logs |
| description | Analyze Volatio debug logs from /tmp/volatio-debug/. Use when the user asks to check debug logs, analyze problems, or diagnose simulation issues. |
Read and analyze debug logs to diagnose problems in the simulation pipeline, Python worker, or API.
All in /tmp/volatio-debug/:
| File | Source | What it captures |
|---|---|---|
debug-YYYY-MM-DD.log | TypeScript DEBUG() | Processor, simulate endpoint, bridge calls |
bridge-YYYY-MM-DD.log | FlowRegimeBridge | IPC requests/responses sent to Python worker |
worker-YYYY-MM-DD.log | Python DEBUG() | Signal generation, cache lookups, price fetches |
rm -f /tmp/volatio-debug/*.log
tail -f /tmp/volatio-debug/*.log
DEBUG is on by default in development. To disable:
DEBUG_LOGGING=false bun run dev
bun run scripts/remove-debug-logs.ts # remove all
bun run scripts/remove-debug-logs.ts --dry-run # preview only
| Pattern in logs | Meaning | Fix |
|---|---|---|
0 signals generated | No symbols matched or cache empty | Check symbols list and cache data |
'dict' object is not callable | Python DEBUG() missing lambda: wrapper | Wrap 3rd arg: DEBUG("loc", "msg", lambda: {...}) |
No cached data found | Z-score cache not seeded for date range | Run Phase A first, or seed with seed_zscore_cache.py |
no price for SYMBOL | Minute bars missing for that symbol/date | Check Polygon data availability |
Phase A failed or Phase A timed out | REST API fetch failed | Check Massive API connectivity |
BLOCKED in trade decisions | Signals filtered by entry rules | Check max_positions, no_existing_position in decisions |
symbols: [] or symbols: null | Session has no flowRegimeConfig.symbols | This is OK — empty means "use all clusters" |
TypeScript:
DEBUG('message')
DEBUG('location', 'message')
DEBUG('location', () => ({ data: value }))
DEBUG('location', 'message', () => ({ data: value }))
Python:
DEBUG('message')
DEBUG('location', 'message')
DEBUG('location', lambda: {'data': value})
DEBUG('location', 'message', lambda: {'data': value})
The 3rd argument in Python MUST be a lambda:, never a raw dict.