Claude Code + Hyvä

Claude Code reads your full theme stack — vendor/hyva-themes/magento2-default-theme (parent), app/design/frontend/<Vendor>/<child-theme>, plus any reset / brand layer in between. When asked to override a phtml, it follows Magento’s fallback rules: it places the new file in your child theme’s correct module path (e.g. app/design/frontend/Brand/child/Magento_Catalog/templates/product/list.phtml) without editing the Hyvä vendor file. It also respects theme.xml parent declarations and won’t accidentally break the inheritance chain.

Yes — that’s one of the highest-value tasks Claude Code does on Hyvä projects. It reads your composer.lock, identifies installed Luma-only extensions (Amasty, Mageplaza, Mirasvit, Aheadworks, Wyomind, etc.), checks hyva-themes.com/compatibility for first-party bridges, and for the gaps it scaffolds the missing etc/hyva-themes.xml, view/frontend/templates overrides, and any required Magewire components. We’ve shipped 50+ extension bridges this way — including custom-built modules where no public bridge exists.

100% accurate to your tailwind.config.js — not generic Tailwind defaults. We seed CLAUDE.md with: “Always read tailwind.config.js before writing utility classes. If a colour / spacing / font scale isn’t in the config, propose a config edit instead of using an arbitrary value.” Claude Code also runs the Tailwind JIT compiler against generated phtml in CI — any class that doesn’t exist in your config fails the build before merge. Net result: 0 hallucinated utility classes across 80+ Hyvä projects shipped.

Yes, measurably. On Hyvä, the codebase is small (~3% of Luma’s frontend code), modern (Tailwind + Alpine.js have huge LLM training corpora), and idiomatic (every component follows the same x-data + ViewModel pattern). Claude Code rarely needs more than 1 round of revision per Hyvä task. On Luma, the RequireJS + KnockoutJS + UIComponent stack is more obscure and Magento-specific — Claude Code is good but slower. Net effect: AI-paired Hyvä dev runs 5–10× faster than hand-written, vs 3–5× on Luma. See our Claude Code + Magento page for the Luma-side workflow.

Yes — this is one of the trickiest Hyvä tasks and Claude Code shines here. Hyvä Checkout 1.x uses Magewire components, not Magento_Checkout’s KnockoutJS. The contract is: Hyva\Checkout\Magewire\Payment\AbstractPaymentMethod for the renderer, Magento\Payment\Model\MethodInterface for the gateway. Claude Code reads your gateway code, generates the Magewire renderer, the corresponding .phtml, and the etc/frontend/di.xml wiring. We’ve shipped Stripe, PayPal, Klarna, Adyen, Mollie, Razorpay and Authorize.Net adapters this way.

Yes — we encode Hyvä’s Alpine conventions in CLAUDE.md: use x-data with a function returning a typed object, prefer $dispatch/$nextTick over jQuery, hydrate from hyva.getCookie() not localStorage, use Hyvä’s built-in event bus (document.addEventListener('reload-customer-section-data', ...)) instead of inventing new events. Claude Code reads vendor/hyva-themes/magento2-default-theme/app/design/frontend/Hyva/default/Magento_Theme/templates/page/js/init.phtml as the source of truth for Hyvä Alpine helpers.

Five deliverables, all written, no obligation: (1) theme inheritance map (parent → brand → child) with override hot-spots; (2) Hyvä-Compatibility gap report — every Luma extension you have, with its compat status; (3) Lighthouse Mobile baseline on PDP, PLP, cart, checkout (live URL); (4) axe-core a11y baseline with WCAG AA violation count; (5) AI-assisted change plan with file paths, ticket sizes, fixed-price quote. We deliver this within 24 business hours of your booking. If you don’t engage, you keep the audit — no strings.

Three CI gates plus one launch-night gate: (1) every PR runs Lighthouse against staging — below 95 fails the build; (2) Tailwind JIT purge runs in CI to ensure unused classes don’t bloat CSS; (3) Alpine.js tree-shaking + critical-CSS inlining are enforced; (4) launch night, we run Lighthouse against the production URL across PDP, PLP, cart, checkout and CMS — if any page drops below 95, we hold cutover. Once live, we run a daily Lighthouse drift check during the 14-day stabilisation window so regressions never make it past day 1.

Plain Alpine.js for any UI that’s purely client-side (toggles, dropdowns, modal triggers, tab switchers, accordion). Magewire for any UI that needs server-side state (mini-cart line totals, configurable-product price recalc on swatch change, address autocomplete with server validation, Hyvä Checkout step transitions). Claude Code knows the cost: Magewire requires a network round-trip, so it suggests Alpine first and only escalates to Magewire when state has to be authoritative on the server. We seed this rule in CLAUDE.md so it’s consistent across the codebase.

Yes — the Hyvä Themes licence (EUR 1,000 one-off per store, paid to hyva-themes.com) is required to use Hyvä in production. That’s separate from our dev fee — you pay Hyvä directly, we don’t mark it up. The licence covers unlimited child themes and updates. Hyvä Checkout is bundled in the same licence as of 2026. We can run the audit and dev work against your existing licence; if you don’t have one yet, we’ll help you scope which tier you need (single store, multi-store, agency).

Yes — this is one of our most-requested workflows. Drop a Figma file URL (or export the dev-mode JSON), and Claude Code generates: (1) a tailwind.config.js patch with your real brand colours, font scales, spacing, breakpoints; (2) phtml component files with semantic HTML + Tailwind utility classes that match the design 1:1; (3) Alpine.js x-data for any interactive states (hover, modal, dropdown) shown in Figma; (4) design-system documentation auto-generated from the components. Output matches design pixel-for-pixel — no “close enough” drift. See our Claude Code UI/UX page for the design-side workflow.

14 days of free post-launch coverage on every Hyvä project — same warranty whether the code came from human keystrokes or AI suggestions. Bug-fix scope explicitly includes Lighthouse drops below 95 and axe-core a11y regressions. After day 14, optional retainer (USD 999/mo) for continued Lighthouse drift watch + a11y monitoring. What’s not covered: third-party extension issues outside the Hyvä-compat bridge, server / hosting performance, Lighthouse score drops caused by client-uploaded heavy images. Every fix is itself reviewed by Claude Code + a human before re-deploy — so we don’t paper over root causes.