- [ ] **Export your IDE settings.**
→ *Each member exports their settings (keymaps, themes, formatting, code style) using the IDE’s built-in tools (e.g. “Settings Sync” in VS Code or “Export Settings” in JetBrains). Store exports in `/config/ide/`.*
- [ ] **Question:** Which settings are worth sharing?
→ *Decide which configurations should be common (e.g. formatting, indentation, file encodings, color scheme for code review consistency) and which can remain personal (themes, fonts). Document this in `/docs/ide_settings.md`.*
- [ ] **Create a shared configuration file or folder.**
→ *Maintain one shared export per IDE (`vscode-settings.json`, `pycharm-settings.zip`, etc.) committed under `/config/ide/`. Include version and export date in the filename or header.*
- [ ] **Question:** How will updates to shared settings be handled?
→ *Agree on a policy — e.g. “Only one person updates shared settings at a time,” or “All changes discussed and approved in an issue labeled `ide-settings`.” Describe it in `/docs/ide_settings.md`.*
- [ ] **Verify import workflow.**
→ *Each team member tests importing the shared settings into their IDE and confirms nothing breaks personal configs. Record feedback in the same `ide-settings` issue.*
- [ ] **Keep IDE versions compatible with shared settings.**
→ *Note in `/docs/ide_settings.md` which IDE versions were used when exporting; re-export after version upgrades if incompatibilities arise.*
- [ ] **Question:** How will you track settings changes over time?
→ *Use commit messages like `update: vscode settings (indent=4)` and link to a changelog entry in `/docs/ide_settings.md` summarizing the modification.*
- [ ] **Provide recovery instructions.**
→ *Document how to restore the default IDE configuration if an import fails (e.g. “Reset settings” menu or deleting config folder).*