Dev Local Setup

OrganizationPopular

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. Use when someone says "set up dev-local", "make a one-command dev launcher", "I want one script to start this repo", "scaffold dev-local for this project".

Overview

Publisher	AI-Builder-Club
Repository	`skills`
Skill name	`dev-local-setup`
Stars	1.3K
Forks	159
Bundled files	1
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
1 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by AI-Builder-Club on GitHub. Read the source before you install it.

Installation

Install the Dev Local Setup AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/AI-Builder-Club/skills.git /tmp/skills
mkdir -p .claude/skills
cp -r /tmp/skills/skills/dev-local-setup .claude/skills/dev-local-setup

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Dev Local Setup in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Dev Local Setup on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Dev Local Setup is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Set up a `dev-local` launcher for this codebase

Goal: 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.

Step 1 — Investigate the repo (don't guess)

Discover the real facts before writing anything:

Package manager & layout — look for 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.
Services to run — each app/package with a 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).
Ports — grep configs and .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.
Infra dependencies — does a backend need Postgres / Supabase / MySQL / Redis / Mongo / Kafka? Check .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).
First-run setup — migrations, seed, codegen, install. Note the commands but keep them OUT of the default up path (offer a separate subcommand).
Env files — confirm a committed .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.

Step 2 — Generate `scripts/dev-local.sh`

Adapt the skeleton in assets/dev-local.template.sh (same directory as this skill). Fill in the discovered services, ports, and infra. Keep these invariants:

One tmux session, one window per long-lived server. Idempotent: re-running up leaves existing windows alone instead of duplicating them.
Preflight that fails fast with install hints when a required tool is missing (tmux, the package manager, Docker if infra needs it).
Infra brought up before servers, reused if already running.
Subcommands: up, down (and down --all to stop infra), status (window list + port check), logs <name>, restart <name>, attach, plus any project-specific one-shots (migrate, seed).
Resolve repo root from the script's own location so it works from any cwd.
No secrets in the script. Print URLs and a port check at the end of up.

If the repo has no infra needs, drop the Docker/DB parts entirely — keep it to preflight + tmux windows. Match the script's complexity to the repo; simpler is better.

Then: chmod +x scripts/dev-local.sh and bash -n scripts/dev-local.sh to syntax-check. Verify the read-only status path runs cleanly. Do not run up.

Step 3 — Write a short skill doc

Create .claude/skills/dev-local/SKILL.md (or the repo's skills location) with: frontmatter (name: dev-local, a description listing trigger phrases), a service/port table, prerequisites, the subcommand list, and brief troubleshooting (port-in-use, a window exited, infra not running). Keep it to one screen — it documents the script, it doesn't re-explain it.

Step 4 — Hand off

Tell the user the exact commands: scripts/dev-local.sh up, plus any first-run step (… migrate). List the URLs. Note any prerequisite they must install or start (e.g. Docker Desktop) before the first up.

Principles

Discover, don't assume. Ports and start commands come from the repo, never from convention alone.
Idempotent & safe to re-run. No duplicate servers, no clobbered infra.
Right-sized. A 3-service monorepo with Postgres+Redis needs the full skeleton; a single Vite app needs ~30 lines. Don't over-build.
Never run servers or print secrets. Generate, syntax-check, hand off.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

assets/dev-local.template.sh6 KB

Frequently asked questions

What does the Dev Local Setup AI skill do?

Why use Dev Local Setup on TypingMind?

Because you install it once and use it with any model. Dev Local Setup is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Dev Local Setup in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/AI-Builder-Club/skills/tree/main/skills/dev-local-setup. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Dev Local Setup?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Dev Local Setup?

As many as you like. As long as a model supports skills, you can use Dev Local Setup with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Dev Local Setup AI skill free?

It is published on GitHub by AI-Builder-Club. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Diagnosing Bugs

mattpocock

CommunityPopular

Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.

Implement

Implement a piece of work based on a spec or set of tickets.

Improve Codebase Architecture

mattpocock

CommunityPopular

Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

Prototype

Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Set up a dev-local launcher for this codebase

Step 1 — Investigate the repo (don't guess)

Step 2 — Generate scripts/dev-local.sh

Step 3 — Write a short skill doc

Step 4 — Hand off

Principles

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now

Set up a `dev-local` launcher for this codebase

Step 2 — Generate `scripts/dev-local.sh`