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/Notification/CONTEXT.md
View on GitHub# Notification Domain
## Purpose
Provides the back-office notification bell: fetches the latest unread counts and items for orders, customers, and customer messages per employee, and tracks the last-seen element per type. Does not handle email notifications or front-office messaging.
## Layers
| Layer | Path |
|-------|------|
| Core CQRS | `src/Core/Domain/Notification/` — Commands, Queries, QueryResults, ValueObjects, Exceptions |
| Adapter | `src/Adapter/Notification/` — handler implementations (no repository; delegates directly to legacy ObjectModel) |
| Legacy ObjectModel | `classes/Notification.php` (216 lines) — do not add logic here |
## Non-obvious patterns
- The adapter query handler calls `(new Notification())->getActiveLastElements()` directly on the legacy ObjectModel — there is no repository abstraction.
- `ValueObject/Type.php` enumerates exactly three notification types: `order`, `customer`, `customer_message`. Any new notification category requires adding a type here.
- There is no dedicated back-office controller; notification data is consumed by a front-end API endpoint.
## Canonical examples
- `src/Core/Domain/Notification/Query/GetNotificationLastElements.php` + `src/Adapter/Notification/QueryHandler/GetNotificationLastElementsHandler.php`
## Related
- [CQRS Component](../../Component/CQRS/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 |