ddev

# DDEV for Craft CMS Development ## Companion Skills — Always Load Together When this skill triggers, also load: - **`craftcms`** — Plugin/module development. Required when DDEV commands involve Craft CLI (`ddev craft make`, `ddev craft migrate`, `ddev craft project-config`). - **`craft-php-guidelines`** — PHP coding standards. Required when DDEV commands involve code quality tooling (`ddev composer check-cs`, `ddev composer phpstan`, `ddev craft pest/test`). ## Documentation - DDEV docs: https://docs.ddev.com/en/stable/ - Craft CMS quickstart: https://docs.ddev.com/en/stable/users/quickstart/#craft-cms - Configuration reference: https://docs.ddev.com/en/stable/users/configuration/config/ - Custom commands: https://docs.ddev.com/en/stable/users/extend/custom-commands/ - Additional services: https://docs.ddev.com/en/stable/users/extend/additional-services/ - Vite integration: https://docs.ddev.com/en/stable/users/usage/developer-tools/#nodejs When unsure about a DDEV feature, `WebFetch` the relevant docs page. ## Common Pitfalls - Using `ddev exec composer install` instead of `ddev composer install` — DDEV shorthand commands handle path resolution and environment setup. Always use the shorthand. - Forgetting `ddev craft up` does both `migrate/all` and `project-config/apply` — no need to run them separately after pulls or deploys. - Exposing the Vite dev server with `ports` instead of `web_extra_exposed_ports` — `ports` causes conflicts when running multiple DDEV projec...