Amazon Auto-Buyer Tool Development
Development agent for amazonBuyer - an Amazon automated purchasing tool. This skill enforces strict technical debt prevention, proper file organization, and systematic task execution patterns.
Core Development Principles
Critical Rules (MUST Acknowledge Before Any Task)
Before starting ANY task, you MUST respond with:
"✅ CRITICAL RULES ACKNOWLEDGED - I will follow all prohibitions and requirements listed in CLAUDE.md"
Absolute Prohibitions
NEVER create new files in root directory - use proper module structureNEVER write output files directly to root - use designated output foldersNEVER create documentation files (.md) unless explicitly requestedNEVER use git commands with -i flag (interactive mode not supported)NEVER use `find`, `grep`, `cat`, `head`, `tail`, `ls` commands - use Read, Grep, Glob tools insteadNEVER create duplicate files (manager_v2.py, enhanced_xyz.py, utils_new.js)NEVER create multiple implementations of same conceptNEVER copy-paste code blocks - extract into shared utilitiesNEVER hardcode values - use config files/environment variablesNEVER use naming like enhanced_, improved_, new_, v2_ - extend original filesMandatory Requirements
COMMIT after every completed task/phaseUSE TASK AGENTS for all operations >30 secondsUSE TODOWRITE for complex tasks (3+ steps)READ FILES FIRST before editingPREVENT TECHNICAL DEBT - search for existing functionality before creating newMAINTAIN SINGLE SOURCE OF TRUTH - one authoritative implementation per featurePre-Task Compliance Check
Before starting any task, explicitly verify ALL points:
**Step 1: Rule Acknowledgment**
Acknowledge all critical rules and commit to following them**Step 2: Task Analysis**
Check if task will create files in root → use proper module structureCheck if task takes >30 seconds → use Task agents not BashCheck if task is 3+ steps → use TodoWrite breakdown firstVerify not using grep/find/cat → use proper tools instead**Step 3: Technical Debt Prevention (MANDATORY)**
SEARCH FIRST using Grep to find existing implementationsREAD any found files to understand current functionalityCheck if similar functionality exists → extend existing codeVerify not creating duplicate class/manager → consolidate insteadEnsure not creating multiple sources of truthConfirm searched for existing implementations using Grep/GlobCheck if can extend existing code instead of creating newVerify not about to copy-paste code → extract to shared utility**Step 4: Session Management**
Check if long/complex task → plan context checkpointsCheck if working >1 hour → consider /compact or session breakDO NOT PROCEED until all checkboxes are explicitly verified.
Technical Debt Prevention Workflow
Before Creating ANY New File:
1. **Search First** - Use Grep/Glob to find existing implementations
```
Grep(pattern="feature.*implementation", include="*.py")
```
2. **Analyze Existing** - Read and understand current patterns
```
Read(file_path="existing_feature.py")
```
3. **Decision Tree**:
- Can extend existing? → DO IT
- Must create new? → Document why
4. **Follow Patterns** - Use established project patterns
5. **Validate** - Ensure no duplication or technical debt
Correct Approach Example:
```bash
WRONG: Creating new file without searching
Write(file_path="new_feature.py", content="...")
CORRECT: Search, read, extend
Grep(pattern="feature.*implementation", include="*.py")
Read(file_path="existing_feature.py")
Edit(file_path="existing_feature.py", old_string="...", new_string="...")
```
Project Structure
```
amazonBuyer/
├── src/main/python/ # Main application code
├── requirements.txt # Python dependencies
└── venv/ # Virtual environment
```
Common Commands
Environment Setup
```bash
Create virtual environment
python -m venv venv
Activate (Linux/Mac)
source venv/bin/activate
Activate (Windows)
venv\Scripts\activate
Install dependencies
pip install -r requirements.txt
```
Run Application
```bash
python src/main/python/main.py
```
Execution Patterns
**PARALLEL TASK AGENTS** - Launch multiple Task agents simultaneously for maximum efficiency**SYSTEMATIC WORKFLOW** - TodoWrite → Parallel agents → Git checkpoints → Test validation**BACKGROUND PROCESSING** - ONLY Task agents can run true background operationsDevelopment Status
**Setup**: ✅ Complete**Core Features**: 🚧 Pending**Testing**: 🚧 Pending**Documentation**: 🚧 PendingImportant Notes
Prevention is better than consolidation - build clean from the startFocus on single source of truth and extending existing functionalityEach task should maintain clean architecture and prevent technical debtAlways commit after completing tasks or phasesUse Task agents for long-running operations to prevent context loss