ct-quaq

Use this skill when the user wants to configure, debug, or work with the quaq MCP (Model Context Protocol) server. Triggers include: setting up quaq as an MCP server, configuring Claude Code or other AI agents to use quaq tools, debugging MCP JSON-RPC communication, understanding quaq MCP tools/resources/prompts, testing the MCP server, or integrating quaq into an agentic workflow. Also use when the user asks about "mcp", "agentic backend", "stdio JSON-RPC", or "tool integration".

Use this skill when the user wants to run backtests, interpret backtest results, perform parameter sweeps, analyze quantitative metrics, or iterate on strategy performance in the quaq engine. Triggers include: running a backtest, reading backtest output, understanding Sharpe ratio or drawdown or win rate, diagnosing zero-trade or negative-return results, sweeping parameters, validating before running, explaining strategy structure, reading exported files (trades.csv, metrics.json, chart.json, report_stats.json), interpreting quant analysis output (P0/P1/P2 tiers), or iterating on a strategy to improve performance. Also use when the user asks about execution modes (bar, tick, microstructure), run configuration, fill modes, fees, slippage, or warmup bars.

Use this skill when the user wants to fetch, download, or manage market data for quaq backtesting. Triggers include: fetching OHLCV klines from Binance, creating or converting Parquet files, preparing CSV data files, configuring the [data] section of strategy TOML files, debugging data loading errors, understanding supported data formats (Parquet, CSV, QBF, Binance ZIP), checking timestamp conventions, or troubleshooting Parquet compatibility issues. Also use when the user asks how to get data into quaq, wire up live Binance fetch, or manage files in core/data/.

Use this skill when the user wants to add custom indicators, create new node types, write custom formulas, extend the quaq engine with new blocks, or add custom logic that doesn't exist in the built-in node catalog. Triggers include: "add custom indicator", "create new node", "custom formula", "extend engine", "add block", "custom logic", "new indicator", "write a block", or any request to add functionality not covered by existing 150+ built-in nodes.

Use this skill when the user wants to import, convert, or prepare data from any source for use with quaq backtesting. Triggers include: downloading data from Yahoo Finance, converting TradingView exports, getting data from a custom API, preparing OHLCV data, importing CSV files, converting data formats, "how do I get data into quaq", custom data source integration, or any data preparation task for the quaq engine.

Use when composing, editing, validating, debugging, or running quaq trading strategies. Triggers: creating strategy TOML files, wiring node graphs, configuring backtests, adding indicators/signals/operators/trade blocks, fixing validation errors (E001-E025), choosing data sources (CSV, Parquet, Binance API), setting up outputs/exports, adding quant analysis nodes, running backtest/validate/explain/sweep commands, or any task involving the quaq strategy engine pipeline.

Use this skill when the user wants to work on the quaq visualization dashboard, the interactive web UI for inspecting strategy node graphs, OHLCV charts, and backtest metrics. Triggers include: launching the viz server, modifying the dashboard frontend (React/TypeScript), changing chart rendering (uPlot plugins, candlestick/volume/markers), editing the node graph view (React Flow, ELK layout), updating the metrics bar, adjusting the pure black theme, modifying the Zig HTTP backend (viz_server.zig), changing API endpoint payloads (/api/graph, /api/chart, /api/metrics), rebuilding frontend assets, embedding assets into the Zig binary, adding new chart panels or series types, customizing node styling or colors, debugging viz server issues, or configuring strategy outputs (series/markers) for chart display.