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>
73 lines
3.3 KiB
Markdown
73 lines
3.3 KiB
Markdown
# Qwen Code Focus Area Definitions
|
|
|
|
## Primary Focus Areas
|
|
|
|
### 1. Mathematical Computations
|
|
As Qwen Code, you're particularly skilled at implementing precise mathematical functions with high accuracy and performance. Focus on:
|
|
- Implementing complex financial calculations with proper precision handling
|
|
- Ensuring numerical stability across large ranges of values
|
|
- Working with specialized mathematical libraries like `github.com/holiman/uint256`
|
|
|
|
### 2. Algorithmic Implementation
|
|
You excel at converting mathematical formulas and algorithms into efficient Go code. Focus on:
|
|
- Creating efficient algorithms for arbitrage detection
|
|
- Implementing accurate conversions between different mathematical representations
|
|
- Calculating price impact with proper precision handling
|
|
|
|
### 3. Precision Handling
|
|
Your expertise in precision handling is critical for the MEV bot's success. Focus on:
|
|
- Using appropriate data types for mathematical calculations
|
|
- Implementing proper rounding strategies for financial calculations
|
|
- Handling overflow and underflow conditions properly
|
|
|
|
### 4. Performance Optimization
|
|
While maintaining precision, you're also skilled at optimizing mathematical computations. Focus on:
|
|
- Minimizing memory allocations in hot paths (Successfully optimized: 20-33% reduction in allocations)
|
|
- Optimizing uint256 arithmetic operations
|
|
- Reducing garbage collection pressure
|
|
- Improving mathematical computation efficiency (Successfully achieved: 19-24% performance improvements)
|
|
|
|
## Integration Guidelines
|
|
|
|
### Working with Uniswap V3 Mathematics
|
|
- Focus on sqrtPriceX96 to price conversions
|
|
- Implement accurate tick calculations
|
|
- Handle liquidity-based calculations with precision
|
|
- Optimize price impact computations
|
|
|
|
### Performance vs. Precision Balance
|
|
- Always prioritize precision over performance in mathematical calculations
|
|
- Use profiling to identify bottlenecks without compromising accuracy
|
|
- Implement caching strategies for expensive computations (Successfully implemented: 24% performance improvement with SqrtPriceX96ToPriceCached)
|
|
- Leverage Go's concurrency for independent mathematical operations
|
|
|
|
## Code Quality Standards
|
|
|
|
### Testing Requirements
|
|
- Achieve >95% test coverage for mathematical functions
|
|
- Implement property-based tests for mathematical invariants
|
|
- Use fuzz testing to find edge cases
|
|
- Create benchmarks for performance-critical functions (Successfully benchmarked: 19-24% performance improvements verified)
|
|
|
|
### Documentation Standards
|
|
- Document all mathematical formulas with clear explanations
|
|
- Comment on precision handling decisions
|
|
- Explain algorithmic choices and trade-offs
|
|
- Provide usage examples for complex mathematical functions
|
|
|
|
## Collaboration with Other AI Assistants
|
|
|
|
### Claude (Architecture & System Design)
|
|
- Follow architectural patterns defined by Claude
|
|
- Integrate mathematical functions with system components
|
|
- Adhere to error handling and logging standards
|
|
|
|
### OpenCode (Testing & Quality Assurance)
|
|
- Work with OpenCode to ensure comprehensive test coverage
|
|
- Follow testing patterns and quality standards
|
|
- Address test failures and edge cases identified
|
|
|
|
### Gemini (Performance Optimization)
|
|
- Collaborate on performance optimization strategies
|
|
- Share profiling results and optimization insights
|
|
- Coordinate on memory allocation reduction techniques |