mechemsi

Use when the user wants the Claude `/deploy` command workflow in Codex, or asks to run `deploy` using the claudet command template.

Use when the user wants the Claude `/fix-issue` command workflow in Codex, or asks to run `fix-issue` using the claudet command template.

Use when the user wants the Claude `/review` command workflow in Codex, or asks to run `review` using the claudet command template.

Use when syncing, auditing, or converting Claude Code and Codex project configuration; when the user says "sync agent configs", "convert Claude project to Codex", "convert Codex project to Claude", "make this project work with both Claude and Codex", or asks to keep AGENTS.md, CLAUDE.md, .claude, .codex, .mcp.json, agents, commands, and skills aligned.

Use when starting a new project from scratch and wanting Claude Code or Codex conventions; when the user says "scaffold from the template", "use claudet", "set up a new project", "init claude config in this repo", "init codex config in this repo", or asks to copy rules/agents/commands/claudedocs structure from the claudet template repo.

Use when the user wants to install or update the claudet rule library (`code-style`, `naming-and-comments`, `file-and-module-structure`, `dependency-management`, `testing`, `api-conventions`, `documentation`) into the current project's `.claude/rules/`; when the user says "sync rules from claudet", "install standard rules here", "update rules in this project", or asks why their rules look outdated compared to claudet's.

Use when designing or reviewing CI/CD pipelines or GitHub Actions workflows; when auditing CI for security or quality gaps; when picking tools (gitleaks, semgrep, trivy, osv-scanner, etc.); when deciding what should fail-the-build vs warn; when shipping AI-generated code that needs harder gates than human code; when a PR slipped through with secrets, hallucinated APIs, broken migrations, or uncovered branches.

Use when about to dispatch a long-running agent task that will modify files and the user wants to keep editing the main checkout; when planning to run two or more agents in parallel on the same repo and worried about file-edit collisions; when reviewing a PR or running a risky/experimental edit without losing current uncommitted state; when bisecting a bug across branches; when comparing two implementations side-by-side; when a destructive operation (large refactor, dependency upgrade, codemod) needs an escape hatch.

Use when the user wants to dispatch a coding task to a remote workspace — fixing bugs, implementing features, running an agentic coding run, or creating a PR automatically. Use this even if the user just says "fix the login bug on myproject" or "run this task" or "create a run" or "implement X on Y". Also use when the user asks to approve or reject a pending run.

Full development workflow orchestration — requirements analysis, architecture planning, implementation, code review, and testing using specialized sub-agents with approval gates. Use when the user wants to develop a complete feature end-to-end, or asks for the full development flow. Triggers on /dev-flow.

Use when the user wants to start an AI agent (Claude, Codex, Gemini, Aider) on a remote workspace server for a project. Use this even if they just say "launch claude on myproject", "start an agent", "open a session on the server", "connect to workspace", or "I want to work on project X remotely".

Use when the user wants to manage projects on the platform — listing configured projects, adding a new repo, updating project settings, or checking if a project is cloned on its workspace. Use this for "show my projects", "add this repo", "register a new project", "which projects do I have", "is this project ready on the workspace", or any project configuration task.

Use when the user asks about workspace servers — listing them, testing SSH connectivity, checking what agents are installed, viewing server details, or troubleshooting server issues. Use this for "show me my servers", "is the server reachable", "what agents are on server X", "test connection to workspace", or any infrastructure-level question about the remote machines.

Use when the user wants to interact with a running agent session on a workspace server — sending commands, reading output, listing active sessions, or closing them. Use this for "send this to the agent", "what's the agent doing", "check session output", "close that session", "list my sessions", or any tmux-based agent interaction.

Use when the user asks about what's happening on the platform — active runs, failed tasks, pending approvals, system health, or analytics. Use this for "what's running", "any failures", "show me the status", "is everything healthy", "how many runs today", or any question about current platform state.

AI workflow editor for CC Workflow Studio. Create and edit visual AI agent workflows through interactive conversation using MCP tools (get_workflow_schema, get_current_workflow, apply_workflow). Use when the user wants to create a new workflow, modify an existing workflow, or edit the workflow canvas in CC Workflow Studio via the built-in MCP server.

Use when the user wants the Claude `/deploy` command workflow in Codex, or asks to run `deploy` using the claudet command template.

Use when the user wants the Claude `/fix-issue` command workflow in Codex, or asks to run `fix-issue` using the claudet command template.

Use when the user wants the Claude `/review` command workflow in Codex, or asks to run `review` using the claudet command template.

Pre-deployment verification for rorch orchestrator

Security audit for rorch runner infrastructure

Use when working inside a local Traefik hub repository (the one shipping snippets/traefik.mk and a top-level docker-compose.yml with a traefik: service) and the developer asks to add a middleware (CORS, basicauth, retry, compress) to a routed consumer, fix dashboard auth, debug a routed-but-404 container, troubleshoot the proxy network, set up autostart on WSL boot, or extend the hub's docs/snippets. Also use for v3 label-syntax questions like IPAllowList vs IPWhiteList or `$$` doubling in compose label values.

Use when a developer asks to wire a dockerized project into a local Traefik reverse-proxy hub, route a service at a friendly *.localhost hostname, add a project to the proxy/Traefik dev hub, or set up Traefik for a docker-compose app. Symptoms include the project having a docker-compose.yml without traefik.mk or docker-compose.traefik.yml, and the developer wanting URLs like http://myapp.localhost instead of localhost:3000.