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/Feature/CONTEXT.md
View on GitHub# Feature Domain
## Purpose
Manages product Features and their Values (e.g. "Composition: Cotton"), which are displayed on product pages. Does not handle Product-level feature associations — those live in `src/Core/Domain/Product/FeatureValue/`.
## Layers
| Layer | Path |
|-------|------|
| Core CQRS | `src/Core/Domain/Feature/` — Commands, Queries, QueryResults, ValueObjects, Exceptions |
| Adapter | `src/Adapter/Feature/` — handler implementations, repository, feature-flag helpers |
| Legacy ObjectModel | `classes/Feature.php` (354 lines) — do not add logic here |
| Back-office UI | `src/PrestaShopBundle/Controller/Admin/Sell/Catalog/FeatureController.php` |
## Non-obvious patterns
- `src/Adapter/Feature/` contains `FeatureFeature.php`, `CombinationFeature.php`, `GroupFeature.php`, `MultistoreFeature.php` — these implement `FeatureInterface` and are feature-flag helpers (not Feature domain entities).
- `src/Core/Domain/Feature/FeatureValueSettings.php` holds domain constants (e.g. max value length) that don't warrant a ValueObject.
- Feature and FeatureValue share the same domain folder; both have full CRUD commands and separate ValueObjects (`FeatureId` / `FeatureValueId`).
## Canonical examples
- `src/Core/Domain/Feature/Command/AddFeatureCommand.php` + `src/Adapter/Feature/CommandHandler/` (handler implementation)
## Related
- [CQRS Component](../../Component/CQRS/CONTEXT.md)
- [Forms Component](../../Component/Forms/CONTEXT.md)
- [Grid Component](../../Component/Grid/CONTEXT.md)
- `tests/Integration/Behaviour/Features/Scenario/Feature/` — 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 |