env-management
使用分隔的.env.client和.env.api结构管理环境变量。在添加新的环境变量、调试配置问题或设置环境时使用。
📖 中文导读:使用分隔的.env.client和.env.api结构管理环境变量。在添加新的环境变量、调试配置问题或设置环境时使用。 以下正文为该技能的原始 SKILL.md 内容(英文),上方安装命令可直接使用。
name: env-management description: Manage environment variables with split .env.client and .env.api structure. Use when adding new env vars, debugging config issues, or setting up environments.
Environment Variables
Split Structure
This project uses split env files (see docs/PRDs/env-system-refactor.md):
| File | Purpose | Prefix |
|---|---|---|
.env.client |
Public browser vars | NEXT_PUBLIC_* |
.env.api |
Server secrets | No prefix |
Adding New Variables
Client-side (Public)
- Add to
.env.client:NEXT_PUBLIC_API_URL=https://api.example.com - Access in code:
const url = process.env.NEXT_PUBLIC_API_URL;
Server-side (Secret)
- Add to
.env.api:STRIPE_SECRET_KEY=sk_live_xxx - Access only in server code:
// Only in app/api/*, server/*, or Server Components const key = process.env.STRIPE_SECRET_KEY;
Security Rules
- Never put secrets in
.env.client - Never prefix secrets with
NEXT_PUBLIC_ - Supabase anon key is public (safe for client)
- Supabase service role key is secret (API only)
Local Development
Copy example files:
cp .env.client.example .env.client
cp .env.api.example .env.api
Cloudflare Deployment
Set vars in Cloudflare Pages dashboard under Settings > Environment Variables.