Results for “env-file”

6 skills

Next.js environment variable management with file precedence, variable types, and deployment configurations. Use when configuring Next.js applications, managing environment-specific settings, or deploying to Vercel/Railway/Heroku.

More results

Scaffolds or audits Zod-validated environment variables for a Next.js service, including src/lib/env.ts, .env.example, scripts/check-env.ts, and pnpm check:env. Use when adding env vars, auditing process.env usage, or aligning with deployment secrets.

Environment variable validation, security scanning, and management for Next.js, Vite, React, and Node.js applications

Guides creating named subset types of WaveEnv to document a component tree's environmental dependencies and enable mock environments for preview/test servers.

technical-svg-diagrams

Generate clean, minimal technical SVG diagrams in a consistent Cloudflare-inspired style. Use when creating architecture diagrams, flow diagrams, or component diagrams for blog posts and documentation.

brycewang-stanford

Cleans a Quarto (.qmd) file by replacing LaTeX holdovers with proper Quarto/Pandoc syntax so the document renders correctly to HTML, PDF (Typst/LaTeX), and Word. Fixes citations (\citep → [@key]), cross-references (\ref → @label), figures (\includegraphics → markdown), tables, text formatting (\textbf → **bold**), inline math (\( \) → $ $), hyperlinks (\href → [text](url)), footnotes (\footnote → ^[]), list environments, section headings, and R Markdown chunk options (dot-style → #| YAML). Use when asked to clean, fix, modernize, or port a Quarto or R Markdown document; when LaTeX commands appear in a .qmd file; when a document fails to render to Word or Typst; or when citations/cross-references do not appear in non-LaTeX output.