Guide for setting up a new Brite dev environment
Guides a developer through a structured, multi-step process to set up and verify a complete local development environment for Brite projects.
When to use
Use this when onboarding a new developer to a Brite project to ensure their local setup is correct and functional.
How to invoke
both
/plugin marketplace add brite-nites/brite-claude-plugins/plugin install workflows@brite-claude-pluginsWalk the user through setting up their development environment for Brite projects. Verify each step succeeds before moving to the next. If a step fails, help troubleshoot before continuing.
Check for and help install required system tools:
| Tool | Check Command | Install (macOS) |
|---|---|---|
| Git | git --version | xcode-select --install |
| Node.js 18+ | node --version | brew install node or nvm |
| pnpm | pnpm --version | npm install -g pnpm |
| Python 3.11+ | python3 --version | brew install python@3.11 |
| Poetry | poetry --version | pipx install poetry |
| Docker | docker --version | Docker Desktop |
Run the check commands and report which tools are already installed and which need setup.
Help the user clone the project repository:
gh auth statusgh auth loginIf the user doesn't specify a repo, ask which Brite project they're joining.
Guide environment variable setup:
.env.example or .env.template exists in the repo.env: cp .env.example .envInstall project dependencies based on what's in the repo:
If package.json exists:
pnpm install
If pyproject.toml exists:
poetry install
If docker-compose.yml exists:
docker compose up -d
Verify each installation completes without errors.
If the project uses a database:
alembic upgrade headpackage.jsonRecommend VS Code extensions based on the project's tech stack:
Always recommend:
For TypeScript/React projects:
For Python projects:
Check if .vscode/settings.json or .vscode/extensions.json exists in the repo and point the user to it.
Install the Brite Claude Code plugins:
claude plugins add https://github.com/Brite-Nites/brite-claude-plugins
Verify the plugin is loaded by checking that /workflows:tech-stack is available.
Run a final check to confirm everything works:
Report results as a checklist:
[x] System tools installed
[x] Repository cloned
[x] Environment configured
[x] Dependencies installed
[x] Database running
[x] IDE configured
[x] Claude Code plugins loaded
[x] Build passes
[x] Tests pass
[x] Dev server starts
If any step failed, summarize what still needs attention.
Once everything passes, suggest:
/workflows:tech-stack to review the technology stack