jeffsenso/prestashop-skills / skills/prestashop-module-development
prestashop-module-development
VerifiedComplete PrestaShop module development workflow using modern architecture and best practices. Use when: creating new PrestaShop modules, updating legacy modules to modern code, implementing hooks and actions, setting up module configuration pages, adding front office features, handling database operations, implementing security measures, managing translations, creating cart rules and vouchers, building Symfony console commands, or modernizing existing PrestaShop modules from legacy patterns to current standards.
ps9-core-ai/Domain/State/CONTEXT.md
View on GitHub# State Domain
## Purpose
Manages geographic states/regions (e.g. US states, Canadian provinces) used in address forms, linked to countries and zones. It does not manage order states — those belong to the `OrderState` domain.
## Layers
| Layer | Path |
|-------|------|
| Core CQRS | `src/Core/Domain/State/` — Commands, Queries, QueryResults, ValueObjects, Exceptions |
| Adapter | `src/Adapter/State/` — handler implementations, repository, `CountryStateByIsoCodeProvider` |
| Legacy ObjectModel | `classes/State.php` (250 lines) — do not add logic here |
| Back-office UI | `src/PrestaShopBundle/Controller/Admin/Improve/International/StateController.php` |
## Non-obvious patterns
- Two controllers exist: `International/StateController.php` (geographic states) and `Configure/ShopParameters/OrderStateController.php` (order states) — they are entirely separate domains despite similar names.
- `ValueObject/NoStateId.php` and `StateIdInterface.php` allow nullable state references in address commands where a state is optional (e.g. countries without states).
- `CountryStateByIsoCodeProvider` in the adapter wraps the legacy `State::getIdByIso()` static call for use in import/address scenarios.
- `StateSettings.php` at the domain root defines validation constants (max name length, ISO code pattern) used by form types.
## Canonical examples
- `src/Core/Domain/State/Command/AddStateCommand.php` + `src/Adapter/State/CommandHandler/AddStateHandler.php`
## Related
- [CQRS Component](../../Component/CQRS/CONTEXT.md)
- [Forms Component](../../Component/Forms/CONTEXT.md)
- [Grid Component](../../Component/Grid/CONTEXT.md)
- `tests/Integration/Behaviour/Features/Scenario/State/` — Behat behavior scenarios
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |