Common Pitfalls.md 18 KB

🕳️ Common Pitfalls Summary

Common issues and solutions during the Vibe Coding process


🤖 AI Chat Related | Issue | Reason | Solution | |:---|:---|:---| | AI generated code doesn't run | Insufficient context | Provide full error messages, describe the runtime environment | | AI repeatedly modifies the same issue | Stuck in a loop | Describe with a different approach, or start a new conversation | | AI hallucinating, fabricating non-existent APIs | Outdated model knowledge | Provide official documentation links for AI reference | | Code becomes messy with changes | Lack of planning | Let AI propose a plan first, then write code after confirmation | | AI doesn't understand my requirements | Vague description | Explain with concrete examples, provide input and output samples | | AI forgets previous conversations | Context loss | Re-provide key information, or use a memory bank | | AI modifies unintended code | Unclear instructions | Explicitly state "only modify xxx, do not touch other files" | | AI generated code style is inconsistent | No style guide | Provide a code style guide or sample code |

🐍 Python Virtual Environment Related ### Why use a virtual environment? - Avoid dependency conflicts between different projects - Keep the system Python clean - Easy to reproduce and deploy ### Creating and using .venv ```bash # Create virtual environment python -m venv .venv # Activate virtual environment # Windows .venv\Scripts\activate # macOS/Linux source .venv/bin/activate # Install dependencies pip install -r requirements.txt # Deactivate virtual environment deactivate ``` ### Common Issues | Issue | Reason | Solution | |:---|:---|:---| | Cannot configure environment at all | Global pollution | Delete and restart, use `.venv` for virtual environment isolation | | `python` command not found | Virtual environment not activated | Run `source .venv/bin/activate` first | | Package installed but import error | Installed globally | Confirm virtual environment is activated before `pip install` | | Dependency conflicts in different projects | Sharing global environment | Create a separate `.venv` for each project | | VS Code uses wrong Python | Interpreter not selected correctly | Ctrl+Shift+P → "Python: Select Interpreter" → Select .venv | | pip version too old | Virtual environment defaults to old version | `pip install --upgrade pip` | | requirements.txt missing dependencies | Not exported | `pip freeze > requirements.txt` | ### One-click environment reset Environment completely messed up? Delete and restart: ```bash # Delete old environment rm -rf .venv # Recreate python -m venv .venv source .venv/bin/activate pip install -r requirements.txt ```

📦 Node.js Environment Related ### Common Issues | Issue | Reason | Solution | |:---|:---|:---| | Node version mismatch | Project requires specific version | Use nvm to manage multiple versions: `nvm install 18` | | `npm install` error | Network/Permission issues | Change registry, clear cache, delete `node_modules` and reinstall | | Global package not found | PATH not configured | Add `npm config get prefix` to PATH | | package-lock conflict | Collaborative work | Use `npm ci` instead of `npm install` consistently | | `node_modules` too large | Normal phenomenon | Add to `.gitignore`, do not commit | ### Common Commands ```bash # Change to Taobao registry npm config set registry https://registry.npmmirror.com # Clear cache npm cache clean --force # Delete and reinstall rm -rf node_modules package-lock.json npm install # Use nvm to switch Node version nvm use 18 ```

🔧 Environment Configuration Related | Issue | Reason | Solution | |:---|:---|:---| | Command not found | Environment variables not configured | Check PATH, restart terminal | | Port occupied | Not properly shut down last time | `lsof -i :port_number` or `netstat -ano \| findstr :port_number` | | Insufficient permissions | Linux/Mac permissions | `chmod +x` or `sudo` | | Environment variables not taking effect | Not sourced | `source ~/.bashrc` or restart terminal | | .env file not taking effect | Not loaded | Use `python-dotenv` or `dotenv` package | | Windows path issues | Backslashes | Use `/` or `\\` or `Path` library |

🌐 Network Related | Issue | Reason | Solution | |:---|:---|:---| | GitHub access slow/timeout | Network restrictions | Configure proxy, refer to [Network Environment Configuration](../从零开始vibecoding/01-网络环境配置.md) | | API call failed | Network/Key issue | Check proxy, API Key validity | | Terminal not using proxy | Incomplete proxy configuration | Set environment variables (see below) | | SSL certificate error | Proxy/Time issue | Check system time, or temporarily disable SSL verification | | pip/npm download slow | Source is abroad | Change to domestic mirror source | | git clone timeout | Network restrictions | Configure git proxy or use SSH | ### Terminal Proxy Configuration ```bash # Temporary setting (effective in current terminal) export http_proxy=http://127.0.0.1:7890 export https_proxy=http://127.0.0.1:7890 # Permanent setting (add to ~/.bashrc or ~/.zshrc) echo 'export http_proxy=http://127.0.0.1:7890' >> ~/.bashrc echo 'export https_proxy=http://127.0.0.1:7890' >> ~/.bashrc source ~/.bashrc # Git Proxy git config --global http.proxy http://127.0.0.1:7890 git config --global https.proxy http://127.0.0.1:7890 ```

📝 Code Related | Issue | Reason | Solution | |:---|:---|:---| | Code file too large, AI cannot process | Exceeds context | Split files, only provide relevant parts to AI | | Code changes not taking effect | Cache/Not saved | Clear cache, confirm save, restart service | | Merge conflicts | Git conflicts | Let AI help resolve: paste conflict content | | Dependency version conflicts | Incompatible versions | Specify version numbers, or isolate with virtual environments | | Chinese garbled characters | Encoding issue | Consistently use UTF-8, add `# -*- coding: utf-8 -*-` at file beginning | | Hot update not taking effect | Watch issue | Check if file is within watch scope |

🎯 Claude Code / Cursor Related | Issue | Reason | Solution | |:---|:---|:---| | Claude Code cannot connect | Network/Authentication | Check proxy, re-run `claude login` | | Cursor completion is slow | Network latency | Check proxy configuration | | Quota exhausted | Limited free quota | Change account or upgrade to paid | | Rules file not taking effect | Path/Format error | Check `.cursorrules` or `CLAUDE.md` location | | AI cannot read project files | Workspace issue | Confirm opened in correct directory, check .gitignore | | Generated code in wrong location | Cursor position | Place cursor at correct position before generating |

🚀 Deployment Related | Issue | Reason | Solution | |:---|:---|:---| | Runs locally, fails on deployment | Environment differences | Check Node/Python versions, environment variables | | Build timeout | Project too large | Optimize dependencies, increase build time limit | | Environment variables not taking effect | Not configured | Set environment variables on the deployment platform | | CORS cross-origin error | Backend not configured | Add CORS middleware | | Static files 404 | Path issue | Check build output directory configuration | | Insufficient memory | Free tier limitations | Optimize code or upgrade plan |

🗄️ Database Related | Issue | Reason | Solution | |:---|:---|:---| | Connection refused | Service not started | Start database service | | Authentication failed | Incorrect password | Check username/password, reset password | | Table does not exist | Not migrated | Run migration | | Data loss | Not persistent | Docker add volume, or use cloud database | | Too many connections | Connections not closed | Use connection pool, close connections promptly |

🐳 Docker Related | Issue | Reason | Solution | |:---|:---|:---| | Image pull failed | Network issue | Configure image accelerator | | Container failed to start | Port conflict/Configuration error | Check logs `docker logs container_name` | | File changes not taking effect | Volume not mounted | Add `-v` parameter to mount directory | | Insufficient disk space | Too many images | `docker system prune` to clean up |

🧠 Large Model Usage Related | Issue | Reason | Solution | |:---|:---|:---| | Token limit exceeded | Input too long | Simplify context, only provide essential information | | Response truncated | Output token limit | Ask AI to output in segments, or say "continue" | | Large differences in model results | Different model characteristics | Select model based on task: Claude for code, GPT for general use | | Temperature parameter effect | Temperature setting | Use low temperature (0-0.3) for code generation, high for creativity | | System prompt ignored | Prompt too long/conflicting | Simplify system prompt, put important parts first | | JSON output format error | Model instability | Use JSON mode, or ask AI to only output code blocks | | Multi-turn conversation quality degrades | Context pollution | Periodically start new conversations, keep context clean | | API call error 429 | Rate limit | Add delay and retry, or upgrade API plan | | Streaming output garbled | Encoding/Parsing issue | Check SSE parsing, ensure UTF-8 |

🏗️ Software Architecture Related | Issue | Reason | Solution | |:---|:---|:---| | Code becomes messy with changes | No architectural design | Draw architecture diagram first, then write code | | Changing one place breaks many others | Tight coupling | Split modules, define clear interfaces | | Don't know where to put code | Confused directory structure | Refer to [General Project Architecture Template](../模板与资源/通用项目架构模板.md) | | Too much duplicate code | Lack of abstraction | Extract common functions/components | | State management chaotic | Global state abuse | Use state management library, unidirectional data flow | | Configuration scattered | No unified management | Centralize into config files or environment variables | | Difficult to test | Too many dependencies | Dependency injection, mock external services |

🔄 Git Version Control Related | Issue | Reason | Solution | |:---|:---|:---| | Committed unintended files | .gitignore not configured | Add to .gitignore, `git rm --cached` | | Committed sensitive information | Not checked | Use git-filter-branch to clean history, change key | | Cannot resolve merge conflicts | Unfamiliar with Git | Use VS Code conflict resolution tool, or ask AI for help | | Commit message written incorrectly | Accidental | `git commit --amend` to modify | | Want to undo last commit | Committed wrongly | `git reset --soft HEAD~1` | | Too many messy branches | No standardization | Use Git Flow or trunk-based | | Push rejected | New commits on remote | `pull --rebase` first, then push | ### Common Git Commands ```bash # Undo changes in working directory git checkout -- filename # Undo changes in staging area git reset HEAD filename # Undo last commit (keep changes) git reset --soft HEAD~1 # View commit history git log --oneline -10 # Stash current changes git stash git stash pop ```

🧪 Testing Related | Issue | Reason | Solution | |:---|:---|:---| | Don't know what to test | Lack of testing mindset | Test edge cases, exceptions, core logic | | Tests are too slow | Test granularity too large | Write more unit tests, fewer E2E | | Tests are unstable | Depends on external services | Mock external dependencies | | Tests pass but bugs appear in production | Incomplete coverage | Add edge case tests, check with coverage | | Changing code requires changing tests | Tests coupled to implementation | Test behavior, not implementation | | AI generated tests are useless | Only tests happy path | Ask AI to supplement edge case and exception tests |

⚡ Performance Related | Issue | Reason | Solution | |:---|:---|:---| | Page loads slowly | Resources too large | Compression, lazy loading, CDN | | API response slow | Queries not optimized | Add indexes, caching, pagination | | Memory leak | Resources not cleaned up | Check event listeners, timers, closures | | High CPU usage | Infinite loop/Redundant computation | Use profiler to locate hotspots | | Database queries slow | N+1 issue | Use JOIN or batch queries | | Frontend lagging | Too many re-renders | React.memo, useMemo, virtualized lists |

🔐 Security Related | Issue | Reason | Solution | |:---|:---|:---| | API Key leaked | Committed to Git | Use environment variables, add to .gitignore | | SQL Injection | SQL concatenation | Use parameterized queries/ORM | | XSS Attack | User input not escaped | Escape HTML, use CSP | | CSRF Attack | No token verification | Add CSRF token | | Password stored in plaintext | Lack of security awareness | Use bcrypt or other hashing algorithms | | Sensitive information in logs | Printed unintended data | Anonymize, disable debug in production |

📱 Frontend Development Related | Issue | Reason | Solution | |:---|:---|:---| | Styles not taking effect | Priority/Cache | Check selector priority, clear cache | | Mobile adaptation issues | Not responsive | Use rem/vw, media queries | | White screen | JS error | Check console, add error boundaries | | State not synchronized | Asynchronous issues | Use useEffect dependencies, or state management library | | Component not updating | Reference not changed | Return new object/array, do not modify directly | | Build size too large | Not optimized | On-demand import, code splitting, tree shaking | | Cross-origin issues | Browser security policy | Backend configure CORS, or use proxy |

🖥️ Backend Development Related | Issue | Reason | Solution | |:---|:---|:---| | API returns slowly | Synchronous blocking | Use async, put time-consuming tasks in queue | | Concurrency issues | Race conditions | Add locks, use transactions, optimistic locking | | Service crashed undetected | No monitoring | Add health checks, alerts | | Logs cannot find issues | Incomplete logs | Add request_id, structured logging | | Configure different environments | Hardcoding | Use environment variables to distinguish dev/prod | | OOM crash | Memory leak/Too much data | Pagination, streaming, check for leaks |

🔌 API Design Related | Issue | Reason | Solution | |:---|:---|:---| | API naming chaotic | No standardization | Follow RESTful, use HTTP verbs for actions | | Return format inconsistent | No agreement | Unify response structure `{code, data, message}` | | Version upgrade difficult | No version control | Add version number to URL `/api/v1/` | | Documentation and implementation inconsistent | Manual maintenance | Use Swagger/OpenAPI for auto-generation | | Error messages unclear | Only returns 500 | Refine error codes, return useful information | | Pagination parameters inconsistent | Each written differently | Unify `page/size` or `offset/limit` |

📊 Data Processing Related | Issue | Reason | Solution | |:---|:---|:---| | Data format incorrect | Type conversion issues | Perform type validation and conversion | | Timezone issues | Timezones not unified | Store UTC, convert to local time for display | | Precision loss | Floating point issues | Use integers (cents) for monetary values, or Decimal | | Large file processing OOM | Loaded all at once | Stream processing, chunked reading | | Encoding issues | Not UTF-8 | Consistently use UTF-8, specify encoding when reading files | | Null value handling | null/undefined | Perform null checks, provide default values |

🤝 Collaboration Related | Issue | Reason | Solution | |:---|:---|:---| | Code style inconsistent | No standardization | Use ESLint/Prettier/Black, unify configuration | | PR too large, difficult to review | Too many changes | Commit in small steps, one PR per feature | | Documentation outdated | No one maintains | Update code and documentation together, CI checks | | Don't know who is responsible | No owner | Use CODEOWNERS file | | Reinventing the wheel | Unaware of existing solutions | Establish internal component library/documentation |
  1. Check error messages - Copy the full error to AI
  2. Minimum reproduction - Find the simplest code that reproduces the issue
  3. Bisection method - Comment out half the code to narrow down the problem scope
  4. Change environment - Try different browsers/terminals/devices
  5. Restart magic - Restart service/editor/computer
  6. Delete and restart - If the environment is messed up, delete and recreate the virtual environment

🔥 Ultimate Solution

Still can't figure it out? Try this prompt:

I've encountered an issue and have tried many methods without success.

Error message:
[Paste full error]

My environment:
- Operating system:
- Python/Node version:
- Relevant dependency versions:

I have tried:
1. xxx
2. xxx

Please help me analyze the possible causes and provide solutions.

📝 Contribution

Found a new pitfall? Welcome PR contributions!