| name | dev |
| description | Development workflows for WordPress ATmosphere plugin including wp-env setup, testing commands, linting, and build processes. Use when setting up development environment, running tests, checking code quality, or working with wp-env. |
ATmosphere Development Cycle
Quick reference for everyday workflows. Full reference: docs/development-environment.md.
Core Commands
npm run env-start
npm run env-stop
npm run env-test
npm run env-test -- --filter=pattern
npm run env-test -- --group=name
composer test
composer lint
composer lint:fix
composer dump-autoload
npm run release
Default URLs
Typical Loop
composer dump-autoload
npm run env-test -- --filter=FeatureName
composer lint
WP-CLI Inside wp-env
npm run env -- run cli wp plugin list
npm run env -- run cli wp option get atmosphere_settings
npm run env -- run cli wp transient delete --all
npm run env -- run cli wp db cli
When to Read the Full Docs
Read docs/development-environment.md when you need:
- Prerequisites (Node version, Docker setup, Composer,
gh CLI).
- Troubleshooting (Docker not running, port conflicts, DB connection errors, slow performance on macOS).
- Code coverage (Xdebug coverage mode, HTML coverage reports).
- PHPUnit argument reference (every flag we use).
- wp-env configuration (overriding PHP / WP versions, mounts, custom ports).
Related Skills
- code-style — PHP conventions, hooks, security, error handling.
- test — PHPUnit patterns, the Publisher capture fixture, simulating in-flight races.
- pr — pre-PR checklist, commit format, special situations.
- release —
npm run release, patch releases.