runner-selection — Claude Code skill for Symfony command runners
The runner-selection skill detects whether Symfony commands belong in Docker, DDEV, or the host environment. Use it when the right command prefix is unclear or containers may be stopped.
MIT ★ 234 updated 2026-10-05
npx skills add dev-toolings/superpowers-symfony --skill runner-selection -a claude-codeWhat runner-selection does
Before the first PHP, Composer, console, or test command, the skill checks the project environment through the library's runtime context CLI. It identifies the Docker setup and whether its containers are running, then supplies prefixed commands such as docker compose exec php bin/console. Scripts can use the --format=env output.
When containers are stopped, the skill follows the CLI's startup guidance and checks the environment again. It keeps the same command prefix throughout the session. The skill is intended for Symfony applications; without one, the CLI prints nothing. Do not run host php or composer when the project expects containers.
What it helps with
- choose command prefixes for Docker Compose, DDEV, or the host
- check whether project containers are running
- start stopped containers using the CLI guidance
- avoid running host PHP and Composer for a container-based project
Example prompts for the agent
- Check the Symfony environment and give me the console, Composer, and test commands.
- Find the right command prefix for running this project's tests.
- The containers may be stopped. Detect the Docker setup and tell me how to start them.
How to install runner-selection
1Skills CLI (Vercel)
npx skills add dev-toolings/superpowers-symfony --skill runner-selection -a claude-code2Manually: put the files in place
~/.claude/skills/runner-selection/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/runner-selection/
1Skills CLI (Vercel)
npx skills add dev-toolings/superpowers-symfony --skill runner-selection -a codex2Manually: put the files in place
.agents/skills/runner-selection/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add dev-toolings/superpowers-symfony --skill runner-selection -a cursor2Manually: put the files in place
.cursor/skills/runner-selection/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install dev-toolings/superpowers-symfony content/skills/runner-selection2Manually: put the files in place
.github/skills/runner-selection/SKILL.md1Skills CLI (Vercel)
npx skills add dev-toolings/superpowers-symfony --skill runner-selection -a gemini-cli2Platform CLI
gemini skills install https://github.com/dev-toolings/superpowers-symfony --path content/skills/runner-selectionManually: put the files in place
.devin/skills/runner-selection/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about runner-selection
How do I install runner-selection in Claude Code?
Run npx skills add dev-toolings/superpowers-symfony --skill runner-selection -a claude-code. The skill file is at ~/.claude/skills/runner-selection/SKILL.md.
What does runner-selection do?
It detects the Symfony project's execution environment and provides prefixes for console, Composer, and test commands. It also gives guidance for starting stopped containers.
Can I use host commands when the project expects containers?
No. The skill instructs Claude Code not to run host php or composer when the project expects containers.
Source text
SKILL.md · MIT
--- name: runner-selection description: Select and configure the appropriate command runner based on Docker Compose standard, Symfony Docker (FrankenPHP), or host environment capabilities: [read, search] tags: [workflow] # projected by `bun run build` — do not edit by hand allowed-tools: - Read - Glob - Grep --- # Runner Selection (Symfony) ## Use when - Before the first PHP, console, composer or test command of a session. - A command fails with a missing PHP, extension or database that the container provides. - The project uses Docker Compose, Symfony Docker (FrankenPHP), DDEV or the host and the right prefix is unclear. - The containers may be stopped and the commands must not silently run on the host. ## Default workflow 1. Run the library's runtime context CLI with `--format=markdown` (or `--format=env` for scripts). 2. Read the detected Docker type (`ddev`, `symfony-docker`, a Compose file, or `none`) and whether the containers are running. 3. Use the prefixed console, composer and test commands it prints, such as `docker compose exec php bin/console`. 4. If the containers are stopped, start them with the guidance it prints (`ddev start` or `docker compose up -d`), then run it again. 5. Reuse the same prefix for every command in the session. ## Guardrails - Never run the host `php` or `composer` when the project expects containers. - Do not guess the Compose service name: take it from the detected commands. - Without a Symfony application the CLI prints nothing: say so instead of inventing a runner. - Do not start or stop containers the task does not need. ## Progressive disclosure - Use this file for execution posture and risk controls. - Open references when deep implementation details are needed. ## Output contract - The detected environment (Docker type, running state, test framework). - The prefixed console, composer and test commands for this session. ## References
© dev-toolings · MIT · dev-toolings/superpowers-symfony