environment-variables
Add environment variable
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Menu
Add environment variable
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Monitor an existing GitHub pull request for automated code-review bots, address only their feedback, push fixes, and keep waiting until the selected bots finish reviewing the latest commit with no new comments. Use when the user asks to wait for review bots, loop on automated review, babysit a reviewer such as Cubic or Baz, or address bot comments without performing an independent review.
End-to-end feature testing — browser QA, API verification, eval tests, or any combination. Covers browser interactions (via agent-browser CLI), Google Workspace operations (gws CLI), API calls, and LLM eval tests. Can also persist tests as reusable QA flows or eval files.
Guidelines for testing the application with Vitest, including unit tests, integration tests (emulator), AI tests, and eval suites for LLM features
Cursor Cloud VM setup and service startup instructions for local development
Guidelines for implementing LLM (Language Model) functionality in the application
Simplify and refine recently modified code for clarity, consistency, and maintainability while preserving exact behavior. Use when asked to simplify, polish, refactor lightly, or clean up current-session changes before review or PR.
| name | environment-variables |
| description | Add environment variable |
This is how we add environment variables to the project:
Add to .env.example:
NEW_VARIABLE=value_example
Add to apps/web/env.ts:
// For server-only variables
server: {
NEW_VARIABLE: z.string(),
}
// For client-side variables
client: {
NEXT_PUBLIC_NEW_VARIABLE: z.string(),
}
experimental__runtimeEnv: {
NEXT_PUBLIC_NEW_VARIABLE: process.env.NEXT_PUBLIC_NEW_VARIABLE,
}
For client-side variables:
NEXT_PUBLIC_client and experimental__runtimeEnv sectionsAdd to turbo.json under globalDependencies:
{
"tasks": {
"build": {
"env": [
"NEW_VARIABLE"
]
}
}
}
examples:
input: |
API_KEY=your_api_key_here
server: { API_KEY: z.string(), }
"build": { "env": ["API_KEY"] } output: "Server-side environment variable properly added"
input: |
NEXT_PUBLIC_FEATURE_ENABLED=false
client: { NEXT_PUBLIC_FEATURE_ENABLED: z.coerce.boolean().default(false), }, experimental__runtimeEnv: { NEXT_PUBLIC_FEATURE_ENABLED: process.env.NEXT_PUBLIC_FEATURE_ENABLED, }
"build": { "env": ["NEXT_PUBLIC_FEATURE_ENABLED"] } output: "Client-side environment variable properly added"
references: