Coding

CLAUDE.md - amazonBuyer

> **Documentation Version**: 1.0

promptBeginner5 min to valuemarkdown

0 views

Feb 8, 2026

CLAUDE.md - amazonBuyer

Documentation Version: 1.0
Last Updated: 2025-07-13
Project: amazonBuyer
Description: amazon 商品自動購買工具
Features: Task agents, technical debt prevention

This file provides essential guidance to Claude Code (claude.ai/code) when working with code in this repository.

🚨 CRITICAL RULES - READ FIRST

⚠️ RULE ADHERENCE SYSTEM ACTIVE ⚠️
Claude Code must explicitly acknowledge these rules at task start
These rules override all other instructions and must ALWAYS be followed:

🔄 RULE ACKNOWLEDGMENT REQUIRED

Before starting ANY task, Claude Code 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 structure
NEVER write output files directly to root directory → use designated output folders
NEVER create documentation files (.md) unless explicitly requested by user
NEVER use git commands with -i flag (interactive mode not supported)
NEVER use
```
find
```
,
```
grep
```
,
```
cat
```
,
```
head
```
,
```
tail
```
,
```
ls
```
commands → use Read, LS, Grep, Glob tools instead
NEVER create duplicate files (manager_v2.py, enhanced_xyz.py, utils_new.js) → ALWAYS extend existing files
NEVER create multiple implementations of same concept → single source of truth
NEVER copy-paste code blocks → extract into shared utilities/functions
NEVER hardcode values that should be configurable → use config files/environment variables
NEVER use naming like enhanced_, improved_, new_, v2_ → extend original files instead

📝 MANDATORY REQUIREMENTS

COMMIT after every completed task/phase - no exceptions
USE TASK AGENTS for all long-running operations (>30 seconds) - Bash commands stop when context switches
TODOWRITE for complex tasks (3+ steps) → parallel agents → git checkpoints → test validation
READ FILES FIRST before editing - Edit/Write tools will fail if you didn't read the file first
DEBT PREVENTION - Before creating new files, check for existing similar functionality to extend
SINGLE SOURCE OF TRUTH - One authoritative implementation per feature/concept

⚡ 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 operations

🔍 MANDATORY PRE-TASK COMPLIANCE CHECK

STOP: Before starting any task, Claude Code must explicitly verify ALL points:

Step 1: Rule Acknowledgment

✅ I acknowledge all critical rules in CLAUDE.md and will follow them

Step 2: Task Analysis

Will this create files in root? → If YES, use proper module structure instead
Will this take >30 seconds? → If YES, use Task agents not Bash
Is this 3+ steps? → If YES, use TodoWrite breakdown first
Am I about to use grep/find/cat? → If YES, use proper tools instead

Step 3: Technical Debt Prevention (MANDATORY SEARCH FIRST)

SEARCH FIRST: Use Grep pattern=".*" to find existing implementations
CHECK EXISTING: Read any found files to understand current functionality
Does similar functionality already exist? → If YES, extend existing code
Am I creating a duplicate class/manager? → If YES, consolidate instead
Will this create multiple sources of truth? → If YES, redesign approach
Have I searched for existing implementations? → Use Grep/Glob tools first
Can I extend existing code instead of creating new? → Prefer extension over creation
Am I about to copy-paste code? → Extract to shared utility instead

Step 4: Session Management

Is this a long/complex task? → If YES, plan context checkpoints
Have I been working >1 hour? → If YES, consider /compact or session break

⚠️ DO NOT PROCEED until all checkboxes are explicitly verified

🏗️ PROJECT OVERVIEW

Amazon商品自動購買工具 - 提供自動化Amazon商品購買功能

🎯 DEVELOPMENT STATUS

Setup: ✅ Complete
Core Features: 🚧 Pending
Testing: 🚧 Pending
Documentation: 🚧 Pending

🎯 RULE COMPLIANCE CHECK

Before starting ANY task, verify:

✅ I acknowledge all critical rules above
Files go in proper module structure (not root)
Use Task agents for >30 second operations
TodoWrite for 3+ step tasks
Commit after each completed task

🚀 COMMON COMMANDS

# Python virtual environment
python -m venv venv
source venv/bin/activate  # Linux/Mac
venv\Scripts\activate     # Windows

# Install dependencies
pip install -r requirements.txt

# Run main application
python src/main/python/main.py

🚨 TECHNICAL DEBT PREVENTION

❌ WRONG APPROACH (Creates Technical Debt):

# Creating new file without searching first
Write(file_path="new_feature.py", content="...")

✅ CORRECT APPROACH (Prevents Technical Debt):

# 1. SEARCH FIRST
Grep(pattern="feature.*implementation", include="*.py")
# 2. READ EXISTING FILES  
Read(file_path="existing_feature.py")
# 3. EXTEND EXISTING FUNCTIONALITY
Edit(file_path="existing_feature.py", old_string="...", new_string="...")

🧹 DEBT PREVENTION WORKFLOW

Before Creating ANY New File:

🔍 Search First - Use Grep/Glob to find existing implementations
📋 Analyze Existing - Read and understand current patterns
🤔 Decision Tree: Can extend existing? → DO IT | Must create new? → Document why
✅ Follow Patterns - Use established project patterns
📈 Validate - Ensure no duplication or technical debt

⚠️ Prevention is better than consolidation - build clean from the start.
🎯 Focus on single source of truth and extending existing functionality.
📈 Each task should maintain clean architecture and prevent technical debt.

View Original Source