Claude Code + Hyvä FAQ
All 10 answers
How does Claude Code handle Hyvä theme inheritance and child themes?
Hyvä uses Magento’s theme fallback: your child theme in app/design/frontend/<Vendor>/<theme> names its parent in theme.xml, and a template override goes in the child theme under the module path, for example Magento_Catalog/templates/product/list.phtml. Claude Code can read the parent template under vendor/hyva-themes and write the override in your theme, but it can also put a file in the wrong place or edit vendor/. Say in CLAUDE.md where overrides go, block vendor/ edits with a hook and check the diff.
Will Claude Code write Hyvä-Compatibility-Module bridges for my Luma extensions?
It can help write one. A Hyvä compatibility module re-implements the parts of a Luma module that do not work on a Hyvä storefront. Check the Compatibility Module Tracker first, because many already exist. A new one registers in etc/frontend/di.xml by adding itself to the compatModules argument of Hyva\CompatModuleFallback\Model\CompatModuleRegistry; price renderer templates are the exception and are overridden in layout XML. Claude Code can draft the module and the template ports, and a developer tests each one on the storefront.
How accurate are the Tailwind classes Claude Code generates for Hyvä?
Not always accurate. Claude Code can write utility classes that your theme does not use or that belong to another Tailwind version. Hyvä 1.4.0 and later ship Tailwind CSS v4, while 1.2.x and 1.3.x use v3, so state your version in the prompt. Then run npm run build in the theme’s web/tailwind directory and check the page in a browser before you commit.
Is Claude Code more accurate on Hyvä than on Luma?
There is no measured figure for this, and this site does not claim one. Hyvä templates use Alpine.js and Tailwind CSS instead of RequireJS, Knockout and UI components, so there is less front-end code to read. The same checks apply on both: name the files, run the theme build or the tests, and review every diff.
Can Claude Code scaffold Hyvä Checkout payment adapters?
It can draft one, with a developer checking it. Hyvä Checkout is built on Magewire, not on the Knockout checkout, and it is a separate commercial product with its own licence. Check the Hyvä Checkout docs first: they list existing payment, shipping and address integrations, so you may not need to build anything. For a new integration, test the full payment flow on staging before release.
Does Claude Code know Alpine.js patterns specific to Hyvä?
It knows Alpine.js in general, not your theme’s own conventions, so write those in CLAUDE.md. Hyvä Default Theme 1.2.x and later use Alpine.js v3 (1.0.x and 1.1.x used v2), so state the version. Point Claude at an existing component in your theme as the pattern to copy, and check the result in the browser.
When does Claude Code reach for Magewire vs plain Alpine.js?
Use plain Alpine.js for state that lives in the browser, such as toggles, tabs and modals. Magewire is for components that need state on the server; Hyvä Checkout is built on it. A Magewire update sends a request to the server, so it is the heavier choice. Write the split you want in CLAUDE.md so Claude Code follows it across the theme, and review each component.
Do I need a Hyvä Themes licence to work with Claude Code?
Not for the theme. Claude Code does not change Hyvä licensing, and according to hyva.io the Hyvä Theme has been free and open source (OSL3 and AFL3) since 10 November 2025. Hyvä Checkout, Hyvä Commerce and Hyvä Enterprise are still commercial products, and Hyvä UI is sold separately, so check hyva.io for the terms of anything beyond the theme.
Can Claude Code convert Figma designs into Hyvä Tailwind components?
It can draft components from a design, but not pixel for pixel. Give it the sizes, colours and states from the design, your Tailwind version and an existing component to follow. Claude Code writes the template and the Alpine.js state; you compare the result with the design in a browser at each breakpoint and fix the gaps.
What if AI-generated Hyvä code regresses Lighthouse or breaks a11y?
The same way as any other regression. Lighthouse and accessibility checks run on staging before a release and are reported as measured, not promised as a score. If a check gets worse, the change is reviewed before it ships. What happens after launch is agreed per project when you ask for a quote.
Related FAQ topics
All FAQ topics-
Magento Upgrade
Common questions about upgrading Adobe Commerce / Magento Open Source. -
Hyvä Development
Common questions about Hyvä theme development, migration from Luma, and Hyvä Checkout.
-
Magento Performance
Common questions about Magento performance optimization, Lighthouse... -
Emergency Bug Fixing
Common questions about emergency e-commerce bug fixing across... -
Hiring a Freelance Magento Developer
Questions about Magento project scope, quotes, start dates... -
Magento B2B Development
Common questions about Adobe Commerce B2B, Magento B2B development...