setup-env

/architect:setup-env

Trigger

/architect:setup-env

Purpose

After generating a blueprint and scaffolding projects, this command walks through setting up every third-party service account (from deliverable 4m — Required Accounts), validates API keys with live checks, and writes a working .env file for each project. Turns 60-90 minutes of manual setup into a guided, validated process.

Workflow

Step 1: Read Context

First, check for architecture-output/_state.json. If it exists, read it in full and extract:

• project.name → product name for display
• tech_stack → list of integrations (Stripe, SendGrid, etc.) to cross-reference against the accounts list
• components → component directory names + ports for .env.example discovery

Then, read the SDL and extract architecture.services[].dependsOn[] for each service — this lists the external providers and sibling services each service calls, which maps directly to which third-party credentials and service URLs each service needs in its .env.example. Check solution.sdl.yaml first; if absent, read sdl/README.md then the relevant module (typically sdl/architecture.yaml or sdl/services.yaml).

Then, check if a blueprint with a Required Accounts list (deliverable 4m) or scaffolded projects with .env.example files exist.

If neither exists, respond:

"I need a list of services to set up. Run /architect:blueprint first to identify required accounts, or /architect:scaffold to create projects with .env.example files, then come back here."

Step 2: Show Setup Plan

Present the services in dependency order:

Here are the accounts you need to set up:

| # | Service | Category | Free Tier | Est. Time |
|---|---------|----------|-----------|-----------|
| 1 | Clerk | Auth | 10K MAU | 10 min |
| 2 | Neon | Database | 0.5 GB | 5 min |
| 3 | Upstash | Redis | 10K cmds/day | 5 min |
| 4 | Stripe | Payments | Test mode | 15 min |
| 5 | SendGrid | Email | 100/day | 10 min |
| 6 | Sentry | Monitoring | 5K errors/mo | 5 min |

Total estimated setup time: 50-60 minutes

I'll walk you through each one, validate your keys, and write the .env file.
Ready to start? (yes / skip to specific service)