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/Carrier/CONTEXT.md
View on GitHub# Carrier Domain
## Purpose
Manages shipping carriers, their shipping ranges (by price and weight), and zone assignments. Does not handle order shipping state or tracking — those belong to the Order domain.
## Layers
| Layer | Path |
|-------|------|
| Core CQRS | `src/Core/Domain/Carrier/` — Commands, Queries, QueryResults, ValueObjects, Exceptions |
| Adapter | `src/Adapter/Carrier/` — handlers, repositories (CarrierRepository, CarrierRangeRepository), validator |
| Legacy ObjectModel | `classes/Carrier.php` (1709 lines) — do not add logic here |
| Back-office UI | `src/PrestaShopBundle/Controller/Admin/Improve/Shipping/CarrierController.php` |
## Non-obvious patterns
- Carriers have **two distinct identifiers**: `CarrierId` (the row primary key, changes on edit when assigned to an order because PrestaShop duplicates the carrier) and `CarrierReferenceId` (stable reference id that persists across edits). Always use `CarrierReferenceId` when linking carriers to other entities across versions.
- Shipping ranges are first-class ValueObjects: `CarrierRangePrice`, `CarrierRangeZone`, `CarrierRangesCollection` — range management is handled via a dedicated `CarrierRangeRepository`.
- `CarrierConstraints.php` (plural) holds all constraint constants — note the plural naming differs from the singular pattern used in most other domains.
## Canonical examples
- `src/Core/Domain/Carrier/Command/AddCarrierCommand.php` + `src/Adapter/Carrier/CommandHandler/AddCarrierCommandHandler.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/Carrier/` — Behat behavior scenarios
- [GOTCHAS.md](../../GOTCHAS.md) — CarrierId vs CarrierReferenceId dual identity trap
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 |