Prompt file imported from Valynt/ValueOS (.windsurf/workflows/init.md). Copyright stays with the author.

Initialize ValueOS

Name: init
Author: Valynt

ValueOS uses a devcontainer-first model. The environment is initialized automatically via Ona automations — no manual multi-terminal setup required.

Standard path (Ona automations)

On environment start, automations run in this order:

installDeps (postDevcontainerStart) — runs bootstrap.sh:
- Validates toolchain versions against .devcontainer/versions.json
- Provisions .env from .env.example if missing
- Runs pnpm install --frozen-lockfile
- Smoke-tests that turbo and tsx resolve
backend service (postEnvironmentStart) — waits for node_modules/.modules.yaml, opens port 3001, starts Express
frontend service (postEnvironmentStart) — waits for node_modules/.modules.yaml, opens port 5173, starts Vite

Check status:

gitpod automations task list
gitpod automations service list

Manual initialization (if automations did not run)

# Install dependencies — always use --frozen-lockfile
bash .devcontainer/scripts/bootstrap.sh

# Start services
gitpod automations service start backend
gitpod automations service start frontend

Required credentials

Before services will start successfully, set in ops/env/.env.backend.local:

SUPABASE_URL=https://your-project-ref.supabase.co
SUPABASE_ANON_KEY=your-anon-key
SUPABASE_KEY=your-anon-key          # same value as SUPABASE_ANON_KEY
SUPABASE_SERVICE_ROLE_KEY=your-service-role-key
DATABASE_URL=postgresql://...
TCT_SECRET=<generate: node -e "console.log(require('crypto').randomBytes(32).toString('hex'))">
WEB_SCRAPER_ENCRYPTION_KEY=<generate: same command>

Verify

curl http://localhost:3001/health
# Expected: {"status":"healthy",...}

Rules

Never use --no-frozen-lockfile — if the lockfile is out of sync, fix it and commit
Never add postCreateCommand or postStartCommand to devcontainer.json — all setup runs through automations
Never install turbo or tsx globally — they are workspace devDependencies

# Initialize ValueOS ValueOS uses a devcontainer-first model. The environment is initialized automatically via Ona automations — no manual multi-terminal setup required. ## Standard path (Ona automations) On environment start, automations run in this order: 1. **`installDeps`** (`postDevcontainerStart`) — runs `bootstrap.sh`: - Validates toolchain versions against `.devcontainer/versions.json` - Provisions `.env` from `.env.example` if missing - Runs `pnpm install --frozen-lockfile` - Smoke-tests that `turbo` and `tsx` resolve 2. **`backend`** service (`postEnvironmentStart`) — waits for `node_modules/.modules.yaml`, opens port 3001, starts Express 3. **`frontend`** service (`postEnvironmentStart`) — waits for `node_modules/.modules.yaml`, opens port 5173, starts Vite Check status: ```bash gitpod automations task list gitpod automations service list ``` ## Manual initialization (if automations did not run) ```bash # Install dependencies — always use --frozen-lockfile bash .devcontainer/scripts/bootstrap.sh # Start services gitpod automations service start backend gitpod automations service start frontend ``` ## Required credentials Before services will start successfully, set in `ops/env/.env.backend.local`: ``` SUPABASE_URL=https://your-project-ref.supabase.co SUPABASE_ANON_KEY=your-anon-key SUPABASE_KEY=your-anon-key # same value as SUPABASE_ANON_KEY SUPABASE_SERVICE_ROLE_KEY=your-service-role-key DATABASE_URL=postgresql://... TCT_SECRET=<generate: node -e "console.log(require('crypto').randomBytes(32).toString('hex'))"> WEB_SCRAPER_ENCRYPTION_KEY=<generate: same command> ``` ## Verify ```bash curl http://localhost:3001/health # Expected: {"status":"healthy",...} ``` ## Rules - **Never** use `--no-frozen-lockfile` — if the lockfile is out of sync, fix it and commit - **Never** add `postCreateCommand` or `postStartCommand` to `devcontainer.json` — all setup runs through automations - **Never** install `turbo` or `tsx` globally — they are workspace devDependencies

{ "prompt": "\n\n# Initialize ValueOS\n\nValueOS uses a devcontainer-first model. The environment is initialized automatically via Ona automations — no manual multi-terminal setup required.\n\n## Standard path (Ona automations)\n\nOn environment start, automations run in this order:\n\n1. **`installDeps`** (`postDevcontainerStart`) — runs `bootstrap.sh`:\n - Validates toolchain versions against `.devcontainer/versions.json`\n - Provisions `.env` from `.env.example` if missing\n - Runs `pnpm install --frozen-lockfile`\n - Smoke-tests that `turbo` and `tsx` resolve\n\n2. **`backend`** service (`postEnvironmentStart`) — waits for `node_modules/.modules.yaml`, opens port 3001, starts Express\n\n3. **`frontend`** service (`postEnvironmentStart`) — waits for `node_modules/.modules.yaml`, opens port 5173, starts Vite\n\nCheck status:\n\n```bash\ngitpod automations task list\ngitpod automations service list\n```\n\n## Manual initialization (if automations did not run)\n\n```bash\n# Install dependencies — always use --frozen-lockfile\nbash .devcontainer/scripts/bootstrap.sh\n\n# Start services\ngitpod automations service start backend\ngitpod automations service start frontend\n```\n\n## Required credentials\n\nBefore services will start successfully, set in `ops/env/.env.backend.local`:\n\n```\nSUPABASE_URL=https://your-project-ref.supabase.co\nSUPABASE_ANON_KEY=your-anon-key\nSUPABASE_KEY=your-anon-key # same value as SUPABASE_ANON_KEY\nSUPABASE_SERVICE_ROLE_KEY=your-service-role-key\nDATABASE_URL=postgresql://...\nTCT_SECRET=<generate: node -e \"console.log(require('crypto').randomBytes(32).toString('hex'))\">\nWEB_SCRAPER_ENCRYPTION_KEY=<generate: same command>\n```\n\n## Verify\n\n```bash\ncurl http://localhost:3001/health\n# Expected: {\"status\":\"healthy\",...}\n```\n\n## Rules\n\n- **Never** use `--no-frozen-lockfile` — if the lockfile is out of sync, fix it and commit\n- **Never** add `postCreateCommand` or `postStartCommand` to `devcontainer.json` — all setup runs through automations\n- **Never** install `turbo` or `tsx` globally — they are workspace devDependencies", "variables": [], "notes": "Initialize the ValueOS development environment", "metadata": { "source": { "provider": "github-windsurf-workflows", "repository": "https://github.com/Valynt/ValueOS", "path": ".windsurf/workflows/init.md", "ref": "8c3196fd7648f6eaf6e1d6e9181760790df4ca40", "url": "https://github.com/Valynt/ValueOS/blob/8c3196fd7648f6eaf6e1d6e9181760790df4ca40/.windsurf/workflows/init.md", "key": "Valynt/ValueOS/.windsurf/workflows/init.md" } } }

init

About

Initialize ValueOS

Standard path (Ona automations)

Manual initialization (if automations did not run)

Required credentials

Verify

Rules

Use it

Manifest

Reviews