How do I install the Local Up skill?

Run npx skillmds@latest add tomevault-io/local-up in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Local Up safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Local Up?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Local Up free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Local Up?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Local Up by tomevault-io — Agent Skill

Name: Local Up
Author: tomevault-io

Local Up

Start the local Docker Compose stack (backend + frontend) for development. Use when the user wants to spin the app up locally, test a feature in a browser, or bring the stack back after changes. Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

Start the local dev stack

The local stack is defined in docker/docker-compose.local.yml. It already sets AUTH_MODE=none and ALLOW_INSECURE_LOCAL=true on the backend, so no extra env vars are needed.

Steps

Check whether containers are already running:

docker compose -f docker/docker-compose.local.yml ps

If nothing is up, start the stack in the background:
```
docker compose -f docker/docker-compose.local.yml up -d --build
```
Use --build so code changes since the last run are picked up. Omit it if the user explicitly wants a fast restart without rebuilding.

After up returns, confirm both services are healthy:

docker compose -f docker/docker-compose.local.yml ps

Print the URLs:
- Frontend: http://localhost:3000
- Backend API: http://localhost:8000
- Backend docs (FastAPI Swagger): http://localhost:8000/docs

If the user wants live logs, tail them:

docker compose -f docker/docker-compose.local.yml logs -f

Troubleshooting

Port 3000 or 8000 already in use: identify the holder with lsof -i :3000 / lsof -i :8000 and ask the user before killing anything.
Backend can't write to /data/db: the named volume dolls_db is docker-managed — no host path needed. Don't propose bind-mounts unless the user asks.
Frontend hot reload not working: Dockerfile.dev runs vite with host: 0.0.0.0; confirm the container has the source mounted if someone customized the compose file.
Auth errors despite AUTH_MODE=none: ALLOW_INSECURE_LOCAL=true must also be set — the backend refuses none without it. Both are already in docker-compose.local.yml; if missing, the file was edited.

Shutting down

docker compose -f docker/docker-compose.local.yml down

Add -v only if the user explicitly wants to wipe the SQLite DB and uploaded photos.

Source: bronweg/doll-inventory — distributed by TomeVault.

---name: local-updescription: Start the local Docker Compose stack (backend + frontend) for development. Use when the user wants to spin the app up locally, test a feature in a browser, or bring the stack back after changes. Use when this capability is needed.---# Start the local dev stackThe local stack is defined in `docker/docker-compose.local.yml`. It already sets `AUTH_MODE=none` and `ALLOW_INSECURE_LOCAL=true` on the backend, so no extra env vars are needed.## Steps1. Check whether containers are already running: ```bash docker compose -f docker/docker-compose.local.yml ps ```2. If nothing is up, start the stack in the background: ```bash docker compose -f docker/docker-compose.local.yml up -d --build ``` Use `--build` so code changes since the last run are picked up. Omit it if the user explicitly wants a fast restart without rebuilding.3. After `up` returns, confirm both services are healthy: ```bash docker compose -f docker/docker-compose.local.yml ps ```4. Print the URLs: - Frontend: http://localhost:3000 - Backend API: http://localhost:8000 - Backend docs (FastAPI Swagger): http://localhost:8000/docs5. If the user wants live logs, tail them: ```bash docker compose -f docker/docker-compose.local.yml logs -f ```## Troubleshooting- **Port 3000 or 8000 already in use**: identify the holder with `lsof -i :3000` / `lsof -i :8000` and ask the user before killing anything.- **Backend can't write to `/data/db`**: the named volume `dolls_db` is docker-managed — no host path needed. Don't propose bind-mounts unless the user asks.- **Frontend hot reload not working**: `Dockerfile.dev` runs `vite` with `host: 0.0.0.0`; confirm the container has the source mounted if someone customized the compose file.- **Auth errors despite `AUTH_MODE=none`**: `ALLOW_INSECURE_LOCAL=true` must also be set — the backend refuses `none` without it. Both are already in `docker-compose.local.yml`; if missing, the file was edited.## Shutting down```bashdocker compose -f docker/docker-compose.local.yml down```Add `-v` only if the user explicitly wants to wipe the SQLite DB and uploaded photos.---> Source: [bronweg/doll-inventory](https://github.com/bronweg/doll-inventory) — distributed by [TomeVault](https://tomevault.io).

Frequently asked questions