switching-projectslisted

# Switching Projects ## Overview Every project has its own conventions, stack quirks, and gotchas; applying the previous project's conventions is a common source of avoidable review comments. This skill is lighter than onboarding — it assumes you can already write code and focuses on one thing: the delta between the project you were on and the new one. The output is a delta report — a table that puts old and new side by side, with explicit "watch out for" notes for the gaps most likely to trip you up. ## Process ### Step 1: Load the new project's CLAUDE.md and config Read the new project's `CLAUDE.md` (Stack, Conventions, Overrides, Test Approach, Build/Run commands) and `README.md` (purpose, local setup, known caveats). If `CLAUDE.md` is missing, suggest running `exloom:authoring-claude-md` first — working without one means Claude invents conventions, a real risk on a shared codebase. If the developer proceeds anyway, fall back to the README and the config files below, and note the gap in the report. Also scan the project root for the ground-truth config — these are what the tools actually read, where `CLAUDE.md` only summarizes: - **Linter/formatter:** `.eslintrc*`, `.prettierrc*`, `checkstyle.xml`, `.editorconfig`, `biome.json` - **Build:** `package.json`, `build.gradle`, `pom.xml`, `Makefile`, `Cargo.toml` - **Types:** `tsconfig.json`, `mypy.ini` - **Environment:** `.env.example`, `docker-compose.yml`, `.tool-versions`, `.nvmrc`, `.java-version` - **Git hooks:** `