Results for “backtesting”

Escribe tests de frontend centrados en el usuario con Vitest, Testing Library y Playwright, cubriendo unit, integración y E2E, y configura el runner de tests.

Verifies that tests for already-implemented behavior are meaningful by temporarily breaking the production code and confirming the test fails for the expected reason.

Prevents AI-introduced regressions with sandbox-mode API testing, automated bug-check workflows, and patterns that catch blind spots where the same model writes and reviews code.

Implements comprehensive backtesting capabilities for Pine Script indicators and strategies. Use when adding performance metrics, trade analysis, equity curves, win rates, drawdown tracking, or statistical validation. Triggers on "backtest", "performance", "metrics", "win rate", "drawdown", or testing requests.

Provides structured reverse engineering techniques for analyzing compiled, obfuscated, packed, or virtualized targets including binaries, APKs, WASM, firmware, and custom VMs using static and dynamic analysis workflows.

Guides backend development across API design, authentication, security, performance, architecture, and testing, with decision guides and defaults for production-ready systems.

Detect when backtest iteration has stalled and generate structurally different strategy pivot proposals to break out of local optima.

Screen S&P 500 stocks for Mark Minervini's Volatility Contraction Pattern (VCP) and detect historical VCPs in a single ticker's price path.

Diagnose failures from runtime evidence before editing code.

Test Fleet

Diagnose and eliminate performance bottlenecks across web, API, database, and code with load testing, profiling, and optimization techniques.

Weekly engineering retrospective. (gstack)

Resume a paused experiment. Checkout the experiment branch, read results history, continue iterating. Use when the user runs /ar:resume or asks to pick up a previously started autoresearch experiment.

Guides backend development across API design, authentication, databases, performance, security, scalability, and testing, with quick decision guides and defaults for production-ready systems.

Rehearse

Retro

Design and evaluate A/B tests with power, sample size, and robust metric interpretation. Use when: (1) planning controlled experiments, (2) reading p-values/effects, (3) sequential testing safeguards. NOT for: dark-pattern optimization.

Validate ransomware recovery plans by testing backup restore operations, measuring RTO/RPO targets, verifying data integrity, and documenting recovery gaps in an isolated lab environment.

Runs a side-by-side walk-forward backtest of a Bull Put Spread strategy with and without a FearScore entry signal, comparing performance metrics over ~8 years of daily data.

Performance regression detection using the browse daemon. Establishes baselines for page load times, Core Web Vitals, and resource sizes. Compares before/after on every PR. Tracks performance trends over time. Use when: "performance", "benchmark", "page speed", "lighthouse", "web vitals", "bundle size", "load time". (gstack) Voice triggers (speech-to-text aliases): "speed test", "check performance".

Post-epic review to extract lessons and assess success. Use when the user says "run a retrospective" or "lets retro the epic [epic]"

Runs and writes tests, verifies behavior, and orchestrates two-pass TDD across scoped modes, blocking on quality gates and never editing production code.

Resume a paused experiment. Checkout the experiment branch, read results history, continue iterating.

Use when investigating a bug, runtime error, unexpected behavior, test failure, or crash. For systematic root cause analysis, error message interpretation, stack trace reading, reproduction steps, and targeted fixes. Activate when the user says "it's broken", "this doesn't work", "I'm getting an error", or "help me debug".

Runs and writes tests for a project, supporting unit, integration, and end-to-end scopes, plus two-pass TDD orchestration with quality-gate checks and regression sweeps.

Weekly engineering retrospective. (gstack)

Weekly engineering retrospective. (gstack)

Use for server-side development including APIs, database schemas, and business logic.

Imported skill backend from langchain

Fix 8-action space bug in backtest engines and rewrite backtest notebook for Colab v4.0.0

Analyzes evaluation patterns across completed plans and evolves the superpowers checklists accordingly.

Analyze sprint retrospectives for patterns and action item tracking. Usage: /retro analyze <retro_data.json>

Runs a full retrospective and dev cycle analysis, chaining /recall and /new-features to reconstruct what went wrong, extract lessons learned, identify rework patterns, and synthesize feature ideas from the findings.