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/Hook/CONTEXT.md
View on GitHub# Hook Domain
## Purpose
Manages Hook entity metadata and status (enabled/disabled) through CQRS. Does not implement hook dispatching or module registration — those live in `src/Adapter/Hook/HookDispatcher.php` and the legacy `Hook` class.
## Layers
| Layer | Path |
|-------|------|
| Core CQRS | `src/Core/Domain/Hook/` — Commands, Queries, QueryResults, ValueObjects, Exceptions |
| Adapter | `src/Adapter/Hook/` — handler implementations, `HookDispatcher.php`, `HookInformationProvider.php` |
| Legacy ObjectModel | `classes/Hook.php` (1616 lines) — do not add logic here |
## Non-obvious patterns
- The CQRS surface is intentionally narrow: only status toggling (`UpdateHookStatusCommand`) and read queries exist. Hook dispatching (calling module listeners) is handled entirely outside this domain via `HookDispatcher`.
- `src/Adapter/Hook/HookInformationProvider.php` provides hook metadata for the back-office hook debugger, not covered by any Query.
## Canonical examples
- `src/Core/Domain/Hook/Command/UpdateHookStatusCommand.php` + `src/Adapter/Hook/CommandHandler/`
## 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 |