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/ShowcaseCard/CONTEXT.md
View on GitHub# ShowcaseCard Domain
## Purpose
Manages the open/closed display state of informational "showcase" cards shown in the back-office (e.g. categories, customers, SEO URLs). It does not manage any catalog or user data — only UI visibility preferences stored in `configuration` table.
## Layers
| Layer | Path |
|-------|------|
| Core CQRS | `src/Core/Domain/ShowcaseCard/` — Commands, Queries, ValueObjects, Exceptions |
| Adapter | `src/Core/Domain/ShowcaseCard/CommandHandler/`, `src/Core/Domain/ShowcaseCard/QueryHandler/` — handlers live inside Core, no `src/Adapter/ShowcaseCard/` |
| Back-office UI | `src/PrestaShopBundle/Controller/Admin/Configure/ShowcaseCardController.php` |
## Non-obvious patterns
- Handlers are located inside `src/Core/Domain/ShowcaseCard/CommandHandler/` and `QueryHandler/` (not under `src/Adapter/`) — an unusual placement in this codebase.
- Card-to-configuration-key mapping is centralised in `ConfigurationMap.php`, using the template `PS_SHOWCASECARD_%s_CLOSED`; each card name maps to a `configuration` row.
- `ValueObject/ShowcaseCard.php` holds string constants for every supported card name (e.g. `SEO_URLS_CARD`, `CATEGORIES_CARD`).
## Canonical examples
- `src/Core/Domain/ShowcaseCard/Command/CloseShowcaseCardCommand.php` + `src/Core/Domain/ShowcaseCard/CommandHandler/CloseShowcaseCardHandler.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 |