AI SummaryHeuristic scoring (no AI key configured).
Install
Copy this and paste it into Claude Code, Cursor, or any AI assistant:
I want to add the "Crypto-Backtest-NautilusTrader-vs-Btdotpy — Copilot Instructions" prompt rules to my project. Repository: https://github.com/ezemriv/Crypto-Backtest-NautilusTrader-vs-Btdotpy Please read the repo to find the rules/prompt file, then: 1. Download it to the correct location (.cursorrules, .windsurfrules, .github/prompts/, or project root — based on the file type) 2. If there's an existing rules file, merge the new rules in rather than overwriting 3. Confirm what was added
Description
Under development...
Scope and Goals of this codebase/project
• Python project to compare two backtesting frameworks: • backtesting.py • nautilustrader • Run identical simple strategies on both. • Measure performance, output parity, and runtime. • If results diverge, document root causes and justify differences. • Data: BTCUSDT 1h bars. Primary source via Binance (CCXT was tested but slower). • Workflow final target (invoked from main.py): • Load or download data • Run backtests on both frameworks • Produce comparisons: strategy metrics, runtime, cpu use, etc. Dependencies are managed with uv. See pyproject.toml for versions.
Language and typing
• Python ≥ version in .python-version. • Full type hints. No Any unless unavoidable. • Strict mypy/pyright settings recommended. Treat warnings as errors.
Docstrings and comments
• Google style docstrings for all public modules, classes, functions: Include Args, Returns, Raises, and Examples when relevant. • Document non-obvious complexity with brief inline comments, not prose.
Structure and imports
• Keep framework-specific code isolated under src/strategies/. • Shared utilities in src/utils/. No framework imports inside utils. • Absolute imports within src. Avoid circular deps.
Discussion
Health Signals
My Fox Den
Community Rating
Sign in to rate this booster
Works With
Any AI assistant that accepts custom rules or system prompts