Varlock prompt builder

 ██▒   █▓ ▄▄▄       ██▀███   ██▓     ▒█████   ▄████▄   ██ ▄█▀
 ▓██░   █▒▒████▄    ▓██ ▒ ██▒▓██▒    ▒██▒  ██▒▒██▀ ▀█   ██▄█▒ 
  ▓██  █▒░▒██  ▀█▄  ▓██ ░▄█ ▒▒██░    ▒██░  ██▒▒██    ▄ ▓███▄░ 
   ▒██ █░░░██▄▄▄▄██ ▒██▀▀█▄  ▒██░    ▒██   ██░▒██▄ ▄██▒▓██ █▄ 
    ▒▀█░   ▓█   ▓██▒░██▓ ▒██▒░██████▒░ █████▒░▒ ████▀ ░▒██▒ █▄
    ░ ▐░   ▒▒   ▓▒█░░ ▒▓ ░▒▓░░ ▒░▓  ░░ ▒░▒░▒░ ░ ░▒ ▒  ░▒ ▒▒ ▓▒
    ░ ░░    ▒   ▒▒ ░  ░▒ ░ ▒░░ ░ ▒  ░  ░ ▒ ▒░   ░  ▒   ░ ░▒ ▒░
      ░░    ░   ▒     ░░   ░   ░ ░   ░ ░ ░ ▒  ░        ░ ░░ ░ 
       ░        ░  ░   ░         ░  ░    ░ ░  ░ ░      ░  ░

Prompt builder

Choose languages, monorepo layout, frameworks, secret stores, and deployment targets. The generated prompt and the page URL stay in sync. Bookmark or share the URL to save your selections.

I. AI tools

Editors and agents where Varlock should pair with your workflow.

II. Monorepo

Monorepos often share schema and config across packages; single projects usually use one primary config.

Single projectOne app or service: one primary Varlock config.MonorepoMultiple packages or apps, with shared .env.schema patterns where needed.

III. Languages

Languages and runtimes for this repo. Choose Node.js for the JavaScript / Node.js integration guide.

IV. Frameworks

App frameworks and bundlers (including Vite-ecosystem routes).

V. Secret stores & plugins

Secret stores and Varlock plugins you plan to use with .env.schema and resolvers.

VI. Deployment platforms and other tools

CI, containers, edge, and per-environment loading.

VII. Generated prompt

Copy into your editor or assistant. Links point to pages on this site.

Help me set up **Varlock** (AI-safe `.env` workflow: `.env.schema`, validation, plugins) for this project.

## Repository layout
- **Single project:** one primary Varlock setup at the repo root (adjust if multiple env files are needed).

Please run `varlock init --agent`, author a sensible of `.env.schema` files (as many as needed), and install any required Varlock plugins and framework/language integrations for the stack above. Always prefer the linked Varlock docs. You can validate your `.env.schema` with `varlock load --agent`.

Add to my repo