config

Configuration

Critical

• NEVER hardcode URLs, tokens, emails, or passwords anywhere in the scaffold. The only source of truth for env-driven values is process.env.*, backed by env/.env.${environment}.
• NEVER hardcode endpoint paths or route strings in config/. Paths belong in enums/{area}/* (see the enums skill).
• ALWAYS add every new env variable to env/.env.example with a safe placeholder — no real secrets, no production URLs.
• ALWAYS add a JSDoc comment on every config property describing the value and the backing env var.
• ALWAYS keep app-facing URLs/settings in config/app.ts and utility/third-party services in config/util/util.ts. Do not create ad-hoc config files elsewhere.
• NEVER commit env/.env.dev, env/.env.staging, or any other real env file containing credentials. Only env/.env.example is tracked.

File Locations

Type	Directory	Purpose
App config	config/app.ts	URLs and settings for the main application
Utility config	config/util/util.ts	Utility / third-party service configuration
Env template	env/.env.example	Tracked template — safe placeholders only
Env (active)	env/.env.${ENVIRONMENT}	Real values, selected at runtime (.env.dev etc.) — untracked

Instructions

Phase 1: Understand how env files are loaded

playwright.config.ts loads env values via dotenv at startup:

const environment = process.env.ENVIRONMENT ?? 'dev';
const environmentPath = `./env/.env.${environment}`;
dotenv.config({ path: environmentPath });

Consequences:

• Default environment is dev (file env/.env.dev).
• Override with a shell variable: ENVIRONMENT=staging npx playwright test.
• The selected file must exist — missing files silently load nothing and every process.env.* becomes undefined.
• ENVIRONMENT itself is set at the shell level; it is not declared in any .env file.