Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →ai-builder-club/dev-local-setup
Scaffold a one-command `dev-local` launcher for ANY codebase. Investigates the repo to find its services, ports, and infra dependencies, then generates a single `scripts/dev-local.sh` (up/down/status/logs/restart) that runs every dev server in one tmux session, plus a short skill doc describing it.
6 of 25 test cases passed with the skill.
Tokens, turns and time describe resource use, not a dollar price.
Lift withheld: 7 comparable cases; this report requires 8.
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
What should `scripts/dev-local.sh up` output to terminal right before completing its execution?
| Checked | Without skill | With skill |
|---|---|---|
| Prints accessibility URLs for configured application services | Passed | Passed |
| Performs a port availability check at the end of stack startup | Missed | Passed |
The instructions your model reads when the skill loads.
dev-local launcher for this codebaseGoal: produce one script (scripts/dev-local.sh) that a person or agent runs
to bring the whole local stack up — every long-lived dev server in its own tmux
window, plus any infra (DB, cache, queues) the app needs — and a short skill doc
so it's discoverable later.
Do NOT start any dev servers yourself. You are generating the launcher, not running it. Build it, syntax-check it, then hand it to the user to run.
This is the local, single-stack launcher. For concurrent agents that each need their own isolated stack (one laptop can't run N), see
crabbox-setup— the cloud counterpart. It reuses this script's service/port discovery, so set this up first.
Discover the real facts before writing anything:
pnpm-workspace.yaml / turbo.json /
nx.json / lerna.json (monorepo) or a single package.json, Cargo.toml,
go.mod, pyproject.toml, Makefile, Procfile, docker-compose.yml.dev/start/serve script, or
each Procfile line, or each docker-compose service. Note the exact command
to start each (e.g. pnpm --filter <name> run dev, npm run dev, cargo run,
uvicorn app:app --reload)..env for the port each service binds
(PORT, listen(, server.port, framework config like rsbuild.config,
vite.config, next.config). Record which talks to which..env(.local), ORM config, docker-compose,
and connection-string defaults. Decide how to provide each locally
(supabase start, a Docker container, an existing docker-compose).install. Note the commands
but keep them OUT of the default up path (offer a separate subcommand)..env.example/.env; never invent or
print secrets. The script must not inject credentials.Write down a small table: service → command → port → depends-on. That table is the spec for the script.
test cases passed with the skill
More skills from the same source and nearby in the registry, with their headline benchmark lift.