Ryusmay

CryptoEdge — Development skill for Claude Code

Development community

Paper-first Python desk for crypto USDT-M perps: daytrading engine, risk gates, purged walk-forward, modular architecture.

How to install CryptoEdge

This entry records only its repository, not the path inside it, so there is no exact command to give. Open Ryusmay/CryptoEdge and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What CryptoEdge does

Paper-first Python desk for crypto USDT-M perps: daytrading engine, risk gates, purged walk-forward, modular architecture. Live execution off by default.

Alternatives in Development

Om Meeting — Prep for any meeting by topic — subject-forward briefing with open tasks, blockers, and brainstormed considera 4.6k ★
Crypto Research Command — Think hard and execute comprehensive cryptocurrency research by calling all crypto analysis agents in parallel 3.4k ★
Crypto Market Rank — Query crypto market rankings including trending tokens, smart money inflows, meme rankings, and top trader PnL 483 ★

README

CryptoEdge

[![tests](https://github.com/Ryusmay/CryptoEdge/actions/workflows/tests.yml/badge.svg)](https://github.com/Ryusmay/CryptoEdge/actions/workflows/tests.yml) [![license: MIT](https://img.shields.io/badge/license-MIT-blue.svg)](LICENSE) [![python](https://img.shields.io/badge/python-3.10%20%7C%203.12-blue.svg)](https://www.python.org/)

**Paper-first research desk for crypto USDT-M perpetuals.** Python engine + native PySide6 UI. Live order placement stays **off** unless you explicitly enable it.

CryptoEdge is a personal quantitative trading workstation: multi-timeframe daytrading (V2), hard risk gates, purged walk-forward, and a modular monolith so strategy, risk, and execution stay testable in isolation.

Ready for **ChatGPT Codex**, **GitHub Copilot**, and **Claude Code** via [`AGENTS.md`](AGENTS.md).

![CryptoEdge paper desk (v20.45, DEMO)](docs/images/desk-v20.45.png)

Native DESK: open positions, candidates, BloFin watchlist, session PnL and risk. Screenshot is **PAPER/DEMO** with an empty book — filled positions wait on modular migration ([ROADMAP](ROADMAP.md) M0).

Not financial advice. Defaults to **PAPER**. API keys never belong in git (`.env` is gitignored).

Why this repo exists

Most crypto “bots” mix signals, sizing, and exchange I/O in one loop. This project is the opposite:

Strategy sees a market snapshot, not your wallet or LIVE flag
Risk owns size, cluster caps, and vetoes
Execution owns fills, SL/TP, reduce-only (paper adapter today)
Replay / walk-forward reuse the same decision path as the desk

Architecture notes live in [`docs/architecture/`](docs/architecture/) (ADR-001 modular monolith, migration stages 0–7).

How this codebase defends itself

The gates in `tools/` are the load-bearing part of the workflow, more than any single strategy parameter. They exist because a trading codebase fails quietly: a refactor that changes one number produces plausible output forever.