c54c569f30
Completed clean root directory structure: - Root now contains only: .git, .env, docs/, orig/ - Moved all remaining files and directories to orig/: - Config files (.claude, .dockerignore, .drone.yml, etc.) - All .env variants (except active .env) - Git config (.gitconfig, .github, .gitignore, etc.) - Tool configs (.golangci.yml, .revive.toml, etc.) - Documentation (*.md files, @prompts) - Build files (Dockerfiles, Makefile, go.mod, go.sum) - Docker compose files - All source directories (scripts, tests, tools, etc.) - Runtime directories (logs, monitoring, reports) - Dependency files (node_modules, lib, cache) - Special files (--delete) - Removed empty runtime directories (bin/, data/) V2 structure is now clean: - docs/planning/ - V2 planning documents - orig/ - Complete V1 codebase preserved - .env - Active environment config (not in git) 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
16 lines
586 B
Markdown
16 lines
586 B
Markdown
# MEV Bot Development Prompts
|
|
|
|
This directory contains prompts that can be used with AI coding assistants to help with the development of the MEV bot.
|
|
|
|
## Purpose
|
|
|
|
These prompts are designed to help developers:
|
|
1. Understand complex Uniswap V3 pricing mathematics
|
|
2. Implement efficient market scanning algorithms
|
|
3. Optimize arbitrage detection logic
|
|
4. Handle Ethereum transaction monitoring
|
|
5. Implement gas optimization strategies
|
|
|
|
## Usage
|
|
|
|
When working on specific parts of the MEV bot, you can use these prompts with your AI coding assistant to get targeted help and suggestions. |