amakaflow-dev-environment-setup

Start, stop, and troubleshoot the AmakaFlow Docker Compose development stack.

Updated Nov 30, 2025
One-click install
npx skills add https://github.com/Amakaflow/amakaflow-dev-workspace --skill amakaflow-dev-environment-setup-amakaflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: amakaflow-dev-environment-setup
Source: https://github.com/Amakaflow/amakaflow-dev-workspace/tree/main/.claude/skills/amakaflow-dev-environment-setup
Command: npx skills add https://github.com/Amakaflow/amakaflow-dev-workspace --skill amakaflow-dev-environment-setup-amakaflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Managing a multi-service local development environment with five separate services (UI, Chat API, Mapper API, Calendar API, Workout Ingestor) requires remembering many Docker Compose commands, health check URLs, and troubleshooting steps, which slows down daily development. ## Core Features & Use Cases - Service Lifecycle Management: Start, stop, restart, and rebuild all AmakaFlow services or individual ones using Docker Compose or Make commands. - Health Verification: Automatically poll health endpoints for each API (ports 8001, 8003, 8004, 8005) and the UI (port 3000) to confirm the stack is ready. - Troubleshooting Guidance: Diagnose common failures such as missing .env files, port conflicts, failing health checks, and Docker resource exhaustion. - Use Case: A developer clones the workspace, runs the skill to start the full stack, verifies all health checks pass, and receives the URLs for the UI and each API's Swagger docs. ## Quick Start Start the AmakaFlow development environment and verify that all services are healthy.

Frequently Asked Questions about amakaflow-dev-environment-setup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I start all AmakaFlow development services at once?

Run 'make start' or 'docker compose up -d' from the workspace root to start all services in detached mode. Then use 'docker compose ps' and the health check endpoints to confirm each service is running.

How do I check if my Docker Compose services are healthy?

Run 'docker compose ps' to see container status, then curl each health endpoint such as http://localhost:8005/health for the Chat API. The UI is verified by loading http://localhost:3000 in a browser.

Why is my Docker Compose service failing to start?

Check the service logs with 'docker compose logs <service-name>' to find the error. Common causes are missing required keys in the .env file, port conflicts on 3000 or 8001-8005, or insufficient Docker resources.

How do I fix a port already in use error with Docker Compose?

Run 'lsof -i :<port>' to identify the process occupying the port, then either kill that process or change the port mapping in docker-compose.yml. Ports 3000, 8001, 8003, 8004, and 8005 must be free for this stack.

How do I rebuild a single Docker service after code changes?

Run 'docker compose build <service-name> --no-cache' followed by 'docker compose up -d <service-name>' to rebuild and restart only that service. Hot reload via docker-compose.override.yml usually makes rebuilds unnecessary for source edits.