- [ ] **Select your primary IDE/editor as a team.**
→ *Discuss options like VS Code, PyCharm (Community/Professional), IntelliJ IDEA, or Sublime Text. Choose one or two main environments that everyone can support. Record the decision and reasoning in `README` → “Development Environment.”*
- [ ] **Question:** Does your IDE support all team languages and frameworks?
→ *Verify syntax highlighting, debugging, and version control integration work for your stack. Note any missing features or workarounds in `/docs/environment.md`.*
- [ ] **Decide on OS compatibility strategy.**
→ *List all operating systems in use (Windows, macOS, Linux). Ensure your chosen IDE and tools behave consistently across them or note OS-specific instructions.*
- [ ] **Document installation steps.**
→ *Write short install guides or links for each platform (e.g. VS Code download + recommended Python or Java extensions). Store them in `/docs/setup.md`.*
- [ ] **Question:** What IDE versions will you standardize on?
→ *Agree on major/minor versions (e.g. VS Code 1.95+, PyCharm 2024.2) and verify all members use compatible ones. Record this in `README`.*
- [ ] **Check interoperability with Git and environment tools.**
→ *Confirm that Git integration, terminal, and environment detection (e.g. Python interpreter, SDK, or Java version) work out of the box. Note fixes if needed.*
- [ ] **Create a verification issue.**
→ *Open one issue titled “IDE Environment Verified” where each team member posts their IDE, version, and OS details to ensure consistency.*
- [ ] **Question:** Can you easily reinstall or migrate your IDE setup?
→ *Locate export/import or sync options (e.g. VS Code Settings Sync, JetBrains IDE Settings Repository). Note how to use them for disaster recovery.*
- [ ] **Keep one lightweight fallback editor.**
→ *Nominate a simple backup tool (e.g. Sublime Text, nano, or VS Code portable) in case the main IDE fails. Add the recommendation to `/docs/environment.md`.*