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/CustomerMessage/CONTEXT.md
View on GitHub# CustomerMessage Domain
## Purpose
Handles sending messages from the back office to customers in the context of an order (via `AddOrderCustomerMessageCommand`). Does NOT manage the customer-service thread lifecycle — that belongs to the CustomerService domain.
## Layers
| Layer | Path |
|-------|------|
| Core CQRS | `src/Core/Domain/CustomerMessage/` — Commands, CommandHandlers, Exceptions |
| Adapter | no `src/Adapter/CustomerMessage/`; the concrete handler lives in `src/Core/Domain/CustomerService/CommandHandler/` |
| Legacy ObjectModel | `classes/CustomerMessage.php` (177 lines) — do not add logic here |
## Non-obvious patterns
- This domain is command-only at the CQRS layer — there are no Query or QueryResult subdirectories. Reading messages is done through the CustomerService domain or legacy controllers.
- `CannotSendEmailException` signals that the message was persisted but the email delivery failed — callers must handle this non-fatal case separately from hard persistence failures.
- The single command is `AddOrderCustomerMessageCommand`, meaning every message is scoped to an order; there is no generic "send message" without an order context.
## Canonical examples
- `src/Core/Domain/CustomerMessage/Command/AddOrderCustomerMessageCommand.php` + `src/Core/Domain/CustomerService/CommandHandler/AddOrderCustomerMessageHandler.php`
## Related
- [CQRS Component](../../Component/CQRS/CONTEXT.md)
- [CustomerService Domain](../CustomerService/CONTEXT.md)
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 |