Codai#

Orchestration skill for the codai-dev local development environment. Routes user requests to the correct plugin without requiring the user to remember which script handles what.

Plugin Map#

What user asksPluginCommandsubir/start MySQLmysql-manager``./mysql/run.sh startparar/stop MySQLmysql-manager``./mysql/run.sh stopstatus MySQLmysql-manager``./mysql/run.sh statusdump de main para <x>``mysql-manager``./mysql/run.sh dump codai_main codai_<x>subir/start PostgreSQLpostgres-manager``./postgres/run.sh startparar/stop PostgreSQLpostgres-manager``./postgres/run.sh stopdump postgres para <x>``postgres-manager``./postgres/run.sh dump codai_main codai_<x>subir/start Redisredis-manager``./redis/run.sh startparar/stop Redisredis-manager``./redis/run.sh stopflush Redisredis-manager``./redis/run.sh flushsubir/start proxyproxy-manager``./nginx-proxy/run.sh startconectar proxy <x>``proxy-manager``./nginx-proxy/run.sh connect <x>criar worktree <x>``worktree-manager``./run.sh create-worktree <x>subir worktree <x>``worktree-manager``./run.sh start <x>parar worktree <x>``worktree-manager``./run.sh stop <x>remover worktree <x>``worktree-manager``./run.sh remove-worktree <x>listar instânciasworktree-manager``./run.sh liststatus geraltodosrun each status in order

Plugin Locations in codai-dev-base#

text

codai-dev-base/
├── run.sh                  # worktree-manager entry point
├── mysql/run.sh            # mysql-manager
├── nginx-proxy/run.sh      # proxy-manager
└── .claude/skills/         # all plugin SKILL.md files

Redis and PostgreSQL are optional extras — install their directories when needed.

Startup Order#

Always follow this sequence:

bash

./nginx-proxy/run.sh start      # 1. creates nginx-proxy_net network
./mysql/run.sh start            # 2. MySQL joins the network
./run.sh start main             # 3. main app instance (seeds db, starts containers, connects proxy)

For Redis or Postgres (if in use):

bash

./redis/run.sh start
./postgres/run.sh start

Multi-Step Workflows#

Create and start a new worktree from scratch#

bash

./run.sh create-worktree <name>   # creates branch worktree/<name>, .worktrees/<name>, .env.worktree-<name>
./run.sh start <name>             # creates db, dumps codai_main→codai_<name>, starts containers, connects proxy

Result: http://<name>.frontend.localhost and http://<name>.backend.localhost

Dump main database to a feature branch#

bash

./mysql/run.sh dump codai_main codai_<name>
# For PostgreSQL:
./postgres/run.sh dump codai_main codai_<name>

Remove a worktree completely (confirm first)#

Confirm: "Remover worktree ''? Isso apaga os containers, banco de dados, git worktree (branch worktree/<name>) e o env file."

bash

./run.sh remove-worktree <name>

Full environment status#

bash

./run.sh list                   # worktrees + infra status
./mysql/run.sh status           # MySQL databases
./nginx-proxy/run.sh status     # proxy routes

Rules#

• Always confirm before remove-worktree — it is irreversible.
• Always report URLs after starting a worktree: frontend and backend.
• Check infra first: if MySQL or proxy is not running, start them before trying to start an instance.
• Startup order matters: proxy → databases → app instances.
• If the user says "sobe tudo" or "start everything", start in order: proxy → mysql → run.sh start main.
• Never run ./mysql/run.sh drop-db codai_main — it is the source of truth.

Environment Variables (shared across plugins)#

VariableDefaultUsed byMYSQL_CONTAINER``codai_dbmysql-manager, worktree-managerMYSQL_ROOT_PASS``secretmysql-manager, worktree-managerMYSQL_MAIN_DB``codai_mainmysql-manager, worktree-managerPROXY_CONTAINER``codai_nginx_proxyproxy-manager, worktree-managerCODAI_NETWORK``nginx-proxy_netall pluginsPROJECT_PREFIX``codai-devproxy-manager, worktree-manager