IDE/editor setup documented

Severity: Optional

Shared IDE configuration ensures consistent developer experience (formatting, linting, extensions).

Check automatically:

# Look for IDE config files in repo
ls -la .vscode/ .idea/ .editorconfig 2>/dev/null

# Check for recommended extensions
cat .vscode/extensions.json 2>/dev/null

# Look for IDE setup docs
grep -riE "vscode|vs code|intellij|ide|editor|extension|plugin" docs/ README.md --include="*.md" 2>/dev/null | head -10

# Check for workspace settings
ls -la *.code-workspace 2>/dev/null

Ask user:

• "Is there a recommended IDE/editor?"
• "Are settings/extensions shared in the repo?"
• "Would a new dev get the same linting/formatting experience as the team?"

Pass criteria:

• Recommended IDE documented OR shared config exists
• Extensions/plugins listed (for linting, formatting, language support)
• Settings ensure consistent experience (format on save, lint rules)

Fail criteria:

• No IDE guidance
• Team uses shared config but it's not in repo/docs
• Inconsistent formatting across team due to different setups

Note: Some teams intentionally stay editor-agnostic. This is acceptable if linting/formatting is enforced at CI level regardless of editor.

Cross-reference with:

• GIT-019 (no local engineer settings committed - but shared settings are OK)

Evidence to capture:

• IDE config files present (.vscode/, .editorconfig)
• Extensions documented or in extensions.json
• Whether settings are shared or individual

---