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/Shipment/CONTEXT.md
View on GitHub# Shipment Domain
## Purpose
Manages shipments within an order — creating, editing, splitting, merging, and switching carriers for shipments and their product quantities. It does NOT manage order-level payment or delivery address; those remain in the Order domain.
## Layers
| Layer | Path |
|-------|------|
| Core CQRS | `src/Core/Domain/Shipment/` — Commands, Queries, QueryResults, ValueObjects, Exceptions, Service interfaces |
| Adapter | `src/Adapter/Shipment/` — handler implementations, delivery options, `OrderShipmentCreator`, `ShipmentMerger`, `ShipmentSplitter`, `ShipmentTotalsCalculator` |
| Doctrine Entity | `src/PrestaShopBundle/Entity/Shipment.php`, `ShipmentProduct.php`, `Entity/Repository/ShipmentRepository.php` |
## Non-obvious patterns
- This domain uses Doctrine entities (no legacy ObjectModel) — `Shipment` and `ShipmentProduct` are in `src/PrestaShopBundle/Entity/`.
- Service interfaces (`ShipmentMergerInterface`, `ShipmentSplitterInterface`) are declared in `Core/Domain/Shipment/Service/` rather than in the Adapter, making the core self-contained for testing.
- `OrderDetailId` / `OrderDetailsId` / `OrderDetailQuantity` are domain value objects here rather than borrowing from the Order domain, reflecting that shipments operate at the order-line level.
- Shipment is partially embedded in the Order viewing result (`OrderProductForViewing` references shipment data) but has its own dedicated query stack.
## Canonical examples
- `src/Core/Domain/Shipment/Command/CreateShipment.php` + `src/Adapter/Shipment/CommandHandler/` (handler)
- `src/Core/Domain/Shipment/Query/GetShipmentForEditing.php` + `src/Core/Domain/Shipment/QueryResult/ShipmentForEditing.php`
## Related
- [CQRS Component](../../Component/CQRS/CONTEXT.md)
- `tests/Integration/Behaviour/Features/Scenario/Shipment/` — 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 |