local-up

Name: local-up
Author: tomevault-io

DevOps Community

Repo stars 0
Author updated Live
Author repo skills-registry

Fluxly profile Facts only: domain, agents, trust score, runtime, permissions and network

Domain: DevOps
Compatible agents: Claude Code
Cursor
Cline
Codex
Windsurf
Gemini CLI

+20
Trust score: 88 / 100 · community maintained
Author / version / license: @tomevault-io · no license declared
Token usage: Lean
Setup complexity: Guided setup
External API key: Not required
Operating systems: Docker
Runtime requirements: Docker
Permissions: Read-only
Write / modify
Env read
Network behavior: Local-only
Install commands: 26 variants

Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.

Heads up: 未限定 allowed-tools，默认拥有全部工具权限。

Output preview local-up.preview

---
name: local-up
description: Start the local Docker Compose stack (backend + frontend) for development. Use when the user wan…
category: devops
runtime: Docker
---

# local-up output preview

## PART A: Task fit
- Use case: 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..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Steps / Troubleshooting / Shutting down” and do not present inference as author intent.

## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “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.”.
- **02** When the source has headings, the agent prioritizes “Steps / Troubleshooting / Shutting down” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files, read environment variables; mostly runs locally; usually needs no extra API key.

## Running Rules
- read files, write/modify files, read environment variables; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options.

SKILL.md SKILL.md

---
name: local-up
description: Start the local Docker Compose stack (backend + frontend) for development. Use when the user wan…
category: devops
source: tomevault-io/skills-registry
---

# local-up

## When to use
- Start the local Docker Compose stack (backend + frontend) for development. Use when the user wants to spin the app up…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.

## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.

## Execution rules
- Organize steps around “Steps / Troubleshooting / Shutting down” and keep inference separate from source facts.
- read files, write/modify files, read environment variables; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.

## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies.

Evidence boundary and execution chain

The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.

skill "local-up" {
  input      -> user goal + target files + boundaries + acceptance criteria
  context    -> Steps / Troubleshooting / Shutting down
  rules      -> SKILL.md triggers / order / output contract
  runtime    -> Docker | read files, write/modify files, read environment variables | mostly runs locally
  guardrails -> usually needs no extra API key + small-sample validation + diff/log review
  output     -> copyable result + checklist + next iteration
}

Interpretation is structured for decision-making; original keeps the upstream SKILL.md unchanged.

Decide Fit First

Core job: Start the local Docker Compose stack (backend + frontend) for development. Use when the user wants to spin the app up locally, t…
Best fit: Use it when the task has reusable inputs, steps, and validation criteria rather than a one-off answer.
Avoid forcing it: If the source lacks commands, platform support, or external-service evidence, keep those fields unknown instead of guessing.

Design Intent

Structure: The skill is organized around “Steps”, “Troubleshooting”, “Shutting down”, showing how the author expects the agent to judge fit, collect context, and produce verifiable output.
Trigger evidence: Prioritize the author’s wording around when to use it, what context to collect, and what output shape to produce.
Evidence boundary: Author text states facts, repository files prove commands and paths, and Fluxly only adds fit, limits, and usage judgment.

How To Use It

Inputs: Provide target material, scope, expected result, forbidden changes, and validation method.
Invocation: Name local-up directly; if the source includes slash commands, start with the command and then add task context.
Validation: Start small and check whether the result follows “Steps / Troubleshooting / Shutting down” before expanding.

Boundaries And Review

Dependencies: It usually needs no extra API key, so start with a small validation task.
Permissions: Declared permissions include read / write / env-read; ask the agent to state file, command, and rollback boundaries before acting.
Quality bar: A useful result names the deliverable, evidence, and next action. Generic prose means the task needs tighter context.

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.

Install command

One-click installPick a runner, click Copy, paste into your terminal, press enter

npx skills add tomevault-io/skills-registry/bronweg--doll-inventory--local-up -y

Open general install guide

View skill source

Works with

Claude Code
Cursor
Cline
Codex
Windsurf
Gemini
OpenCode
Roo Code
AAide
+Augment
GitHub Copilot
OpenClaw
KKiro
Junie
WWarp
Goose
Trae
Kilo Code
OpenHands
Amp
Zencoder
CContinue
AIAider
CodeBuddy
CodeGeeX
Replit Agent

Security audit

88 / 100

Community

未声明 license/许可。
未声明 version。
未限定 allowed-tools，默认拥有全部工具权限。

Metadata

Source: github
tomevault-io/skills-registry
中文

More by @tomevault-io

Category & tags

Category DevOps