dev-environment-bootstrapping

Shopware Dev Environment Bootstrapping

Orchestrate the full first-run Shopware development environment setup. Detects current state, presents a numbered plan, confirms with the user, executes the plan via lifecycle MCP tools, then stops with a handoff message.

Output scope: Executes MCP lifecycle tools and Bash clone commands. Writes no config files. Invokes no dev-tooling skills. Stops after printing the handoff message.

Phase 1 — Detection (no user interaction)

Silently probe the working directory to determine what already exists and what is missing. Do not prompt the user during this phase.

Shopware Checkout State

1. Check composer.json exists and contains shopware/core as a dependency — determines whether this is a Shopware project root.
2. Check src/Core/ directory exists — confirms a full Shopware source checkout vs. a vendor install.
3. Check .env file exists and contains DATABASE_URL — determines if the environment has been configured.
4. Check var/cache/ directory exists — rough indicator that bin/console cache:clear has run at least once.

Environment Clues

Check for these files/directories to infer the intended execution environment:

• docker-compose.yml or docker-compose.yaml — Docker Compose environment
• .ddev/config.yaml — DDEV environment
• Vagrantfile — Vagrant environment
• None of the above — native environment assumed

Plugin State

• Check custom/plugins/ directory exists and list any subdirectories — these are already-present plugins.
• Determine whether the user's stated intent (from their message) involves a specific plugin name.

Database State

• .env with DATABASE_URL present → database may be configured
• var/cache/ present → system:install has likely run before

Dev Tooling Config

• Check for .mcp-php-tooling.json in the project root — if present, environment args are already locked in and will be used by the lifecycle tools automatically.
• Check for .mcp-php-tooling.json in .claude/ — same.