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/Country/CONTEXT.md
View on GitHub# Country Domain
## Purpose
Manages country records including creation, editing, deletion, and zip code format validation. Does not manage states/regions — those are handled by the `State` domain.
## Layers
| Layer | Path |
|-------|------|
| Core CQRS | `src/Core/Domain/Country/` — Commands, Queries, QueryResults, ValueObjects, Exceptions |
| Adapter | `src/Adapter/Country/` — handler implementations, repository, validator, data providers |
| Legacy ObjectModel | `classes/Country.php` (504 lines) — do not add logic here |
| Back-office UI | `src/PrestaShopBundle/Controller/Admin/Improve/International/CountryController.php`, `src/Core/Grid/Definition/Factory/CountryGridDefinitionFactory.php` |
## Non-obvious patterns
- `ZipCodePatternResolverInterface` and its implementation live at the domain root level (not under `ValueObject/`); they convert country-specific zip code format strings into regex patterns usable for validation.
- `CountryId` has a companion `NoCountryId` value object and a `CountryIdInterface` — the interface accommodates contexts where a country may not be set (e.g., optional country fields).
- `src/Adapter/Country/Validate/CountryValidator.php` is a standalone validator consumed by handlers — not a Symfony constraint.
- `src/Adapter/Country/` includes `CountryRequiredFieldsProvider` and `CountryZipCodeRequirementsProvider`, which drive address form field visibility based on per-country configuration.
## Canonical examples
- `src/Core/Domain/Country/Command/AddCountryCommand.php` + `src/Adapter/Country/CommandHandler/` (AddCountryHandler)
## Related
- [CQRS Component](../../Component/CQRS/CONTEXT.md)
- [Forms Component](../../Component/Forms/CONTEXT.md)
- [Grid Component](../../Component/Grid/CONTEXT.md)
- `tests/Integration/Behaviour/Features/Scenario/Country/` — 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 |