Files
mev-beta/orig/.claude/commands/implement-feature.md
Administrator c54c569f30 refactor: move all remaining files to orig/ directory
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>
2025-11-10 10:53:05 +01:00

1.6 KiB

Implement Feature

Implement the following feature for the MEV bot: $ARGUMENTS

Implementation Framework:

  1. Requirements Analysis: Break down the feature requirements and acceptance criteria
  2. Architecture Design: Design the solution following existing patterns
  3. Interface Design: Define clean interfaces between components
  4. Implementation: Write the code following Go best practices
  5. Testing: Create comprehensive unit and integration tests
  6. Documentation: Update relevant documentation and examples

Implementation Standards:

  • Code Quality: Follow Go conventions and project coding standards
  • Error Handling: Implement robust error handling with context
  • Logging: Add appropriate logging with structured fields
  • Testing: Achieve >90% test coverage
  • Performance: Consider performance implications and add metrics
  • Security: Validate all inputs and handle edge cases

File Organization:

  • Core Logic: Place in appropriate pkg/ subdirectory
  • Configuration: Add to internal/config/ if needed
  • Tests: Co-locate with source files (*_test.go)
  • Documentation: Update docs/ and inline comments

Integration Points:

  • Event System: Integrate with pkg/events/ for transaction processing
  • Market Pipeline: Connect to pkg/market/pipeline.go for processing
  • Monitoring: Add metrics and health checks
  • Configuration: Add necessary environment variables

Deliverables:

  • Working implementation with tests
  • Updated documentation
  • Configuration updates
  • Performance benchmarks if applicable
  • Migration guide for existing deployments