← ClaudeAtlas

veldlisted

Orchestrate local dev environments with veld. Use this skill when the user wants to start, stop, or restart services; check run status or logs; configure veld.json (nodes, services, dependencies, presets, health checks, ports, URL templates); or debug environment issues like port conflicts or health-check failures. Also use when the user wants to show their UI to a human for review, get visual feedback on changes, watch for comments, or run a feedback loop — even if they say "let me check," "show the user," "wait for feedback," or "let them review it." Also use when they want to customize the Veld IDE for a project — add a status badge (pull request state, CI, a deploy tag), a button that opens the worktree in an editor, a menu of project actions, a terminal pane that runs a coding agent, a picker that offers that agent's earlier sessions to resume, or tell the team something changed. Covers any `veld` CLI command.
prosperity-solutions/veld · ★ 12 · Code & Development · score 78
Install: claude install-skill prosperity-solutions/veld
# Veld Veld orchestrates local dev environments. It starts services from `veld.json`, wires dependencies, and gives each service an HTTPS URL like `https://frontend.my-feature.myproject.localhost`. ## The documentation is in the CLI This file is a pointer, on purpose. The veld binary carries its own agent documentation, so what you read describes **the veld installed here** rather than whichever version this file was written against: ```sh veld skills # the index: thirteen topics, one line each veld skills basics # start here — the command surface and the traps veld skills <topic> # the one you need, when you need it ``` Read `veld skills basics` before your first `veld` command. Fetch any other topic only when the task reaches it; each one is a full reference and there is no reason to pay for all thirteen. **Do not load project state up front either.** Nothing about *this* project — its presets, nodes, ports or config — belongs in your context until you have a question it answers. Ask then: ```sh veld presets # what this project can start, with each preset's `when_to_use` veld nodes # every node and variant, and where it is defined veld status # what is running now veld <subcommand> --help ``` `veld config` prints the whole resolved configuration and is routinely tens of thousands of characters. Reach for `veld presets`, `veld nodes` or `veld config --files` instead; reach for `veld config` only when you genuinely ne