メニュー
Runs the full stack locally with Docker Compose. Use when starting local development, running docker compose, debugging containers, or testing the full application locally.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | docker-local-dev |
| description | Runs the full stack locally with Docker Compose. Use when starting local development, running docker compose, debugging containers, or testing the full application locally. |
| argument-hint | Optionally specify which services to run or debug |
Exact commands for running the full application stack locally using Docker Compose.
Configure environment:
cp .env.example .env
# Default .env works for local dev (STORAGE_MODE=inmemory, OTEL_EXPORTER=console)
Build and start all services:
docker compose up --build
This starts:
http://localhost:8001 (FastAPI with healthcheck)http://localhost:5173 (React via nginx)Verify health:
# Backend health (waits for container healthcheck to pass)
curl http://localhost:8001/healthz
# Expected: {"status": "ok"}
# Frontend loads
open http://localhost:5173
View logs:
# All services
docker compose logs -f
# Backend only
docker compose logs -f backend
# Frontend only
docker compose logs -f frontend
Rebuild after changes:
# Rebuild specific service
docker compose up --build backend
# Full rebuild
docker compose down && docker compose up --build
Stop:
docker compose down
Backend (direct):
cd py/apps/app-template
uv pip install -e .[dev]
uv run uvicorn main:app --reload --port 8001
Frontend (direct):
cd ts
pnpm install
pnpm --filter ui-copilot-template dev
API_PORT in .env or update docker-compose.yml port mapping..env is present and has required vars.CORS_ORIGINS includes frontend URL. Check nginx proxy config.docker compose logs backend..env file exists (copied from .env.example)docker compose up --build succeedsReference for using and extending agentkit — YAML-driven agent specification loading and validation. Use when defining agent specs, loading YAML configs, extending AgentSpec with custom fields, or managing multiple agent configurations.
Validates the entire template stack works end-to-end — tests, Docker, infra, health checks. Use after making cross-layer changes, before PRs, or when verifying template integrity.
Reference for using and extending evalkit — evaluation framework with protocol-based evaluators, weighted rubric scoring, quality gates, and coaching moments. Use when creating custom evaluators, configuring rubrics, understanding scoring, or extending the evaluation framework.
Reference for using and extending foundrykit — Azure AI Foundry client, AgentManager, ToolRegistry, and FoundrySettings. Use when working with Azure AI credentials, creating/running agents, registering tools, or extending foundrykit for custom needs.
Validates performance and concurrency behavior of backend endpoints. Use when preparing for production, checking latency under load, or verifying system stability.
Confirms deployability and basic system health after deployment or container start. Use after azd deploy, docker compose up, or any deployment to verify the system is alive.