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/Component/Database/CONTEXT.md
View on GitHub# Database Component
## Purpose
Repository abstraction layer between domain handlers and persistence: `AbstractObjectModelRepository` wraps legacy ObjectModel CRUD inside typed domain exceptions. Does not define any business entities — those live in each domain's adapter layer.
## Layers
| Layer | Path |
|-------|------|
| Core repository base | `src/Core/Repository/AbstractObjectModelRepository.php` |
| Multi-shop variant | `src/Core/Repository/AbstractMultiShopObjectModelRepository.php` |
| Domain repositories (30+) | `src/Adapter/{Domain}/Repository/` |
| Legacy DB adapter | `src/Adapter/Database.php` |
## Non-obvious patterns
- `AbstractObjectModelRepository` wraps all `PrestaShopException`s in typed `CoreException` sub-classes — handlers never catch raw PS exceptions
- `partiallyUpdateObjectModel(array $properties)` — partial updates pass an explicit list of fields to `ObjectModel::update()`; avoids overwriting unloaded fields
- `softDeleteObjectModel()` vs `deleteObjectModel()` — soft delete sets `active=0` rather than deleting the row; used for entities with referential integrity constraints
- `Db::getInstance()` is never used in new repositories — inject `Doctrine\DBAL\Connection` instead
## Canonical examples
- `src/Core/Repository/AbstractObjectModelRepository.php`
- `src/Adapter/Order/Repository/OrderRepository.php`
## Related
- [CQRS Component](../CQRS/CONTEXT.md) — handlers inject repositories to fulfil commands/queries
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 |