ddtcorex/maestro-skills / skills/magento2-hyva-dev
magento2-hyva-dev
FlaggedUse when creating a Hyvä theme or child theme, building an Alpine.js component, making markup CSP-compliant, adding Tailwind classes, or converting Luma to Hyvä. DEPENDENT on magento2-dev-core.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 8.2 KB |
| references/alpine.md | markdown | 3.7 KB |
| references/compatibility-modules.md | markdown | 1.3 KB |
| references/csp.md | markdown | 3.2 KB |
| references/migration.md | markdown | 1.2 KB |
| references/review-checklist.md | markdown | 4.3 KB |
| references/tailwind.md | markdown | 2.7 KB |
| references/theme-and-child.md | markdown | 2.4 KB |
| references/view-models.md | markdown | 1.6 KB |
references/compatibility-modules.md
View on GitHub# Third-party compatibility modules
How a third-party extension gets a Hyvä compatibility module, and the naming and layout it
follows.
A Luma-built third-party extension needs a Hyvä compatibility module to override its templates and JS, check the vendor's GitHub for an existing one (many ship under `hyva-themes/*`) before writing your own.
To build one: create a module that requires the original module, copy only the `.phtml` templates you need to override, replace any jQuery/Knockout JS with CSP-compatible Alpine, and sequence it after both the original module and `Hyva_Theme` in `module.xml`. Then register it so Hyvä actually picks it up:
```xml
<!-- etc/frontend/di.xml -->
<type name="Hyva\CompatModuleFallback\Model\CompatModuleRegistry">
<arguments>
<argument name="compatModules" xsi:type="array">
<item name="hyva_vendor_module" xsi:type="array">
<item name="original_module" xsi:type="string">Vendor_Module</item>
<item name="compat_module" xsi:type="string">Vendor_ModuleHyva</item>
</item>
</argument>
</arguments>
</type>
```
Without this `CompatModuleRegistry` registration, Hyvä has no way to know the compat module should override the original's frontend output, the templates get copied but never actually take effect.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |