sylius

What problem does it solve?

Sylius plugin development can be slow and error-prone when you need to correctly follow Symfony bundle patterns, register resources, extend forms/templates, and integrate with API Platform and the admin UI without breaking multi-channel behavior.

Core Features & Use Cases

• Sylius plugin architecture guidance: Understand how a Sylius plugin is structured as a Symfony bundle distributed via Composer, including configuration, services, doctrine mappings, grids, routing, templates, and optional migrations.
• Resource model & CRUD integration: Set up Sylius ResourceBundle resources so your entities automatically get controllers, factories, repositories, forms, and admin routing patterns.
• Extension mechanisms: Use service decoration, form type extensions, template events (Twig blocks), and event listeners to customize behavior while staying compatible with Sylius updates.
• API Platform integration: Expose plugin entities via REST/GraphQL using serialization groups, custom operations, providers, and processors following Sylius 1.13+/2.0 conventions.
• Development practices & guardrails: Avoid common anti-patterns (controller overriding, hardcoding entity classes, bypassing the resource layer), and follow testing setup guidance (Behat, PHPSpec, PHPUnit) for reliable plugin iteration.

Quick Start

Use the sylius skill to build a new Sylius plugin bundle that registers a resource, adds admin UI template-event blocks, and exposes the resource through API Platform for both shop and admin contexts.