agentsclimarketplace

Magento2 breeze child theme

Skill muon-m2/magento2-tools/skills/magento2-breeze-child-theme

End-to-end Magento 2 engineering skills — Claude Code pluginFrom the repository description

Install
npx -y skills add muon-m2/magento2-tools --skill magento2-breeze-child-theme

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 6 stars6 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

6.8 KB, as published. Nobody here has run it

Magento 2 Breeze Child Theme

Scaffolds a Swissup Breeze child theme. Breeze is a high-performance frontend framework that replaces RequireJS/Knockout/jQuery with a Cash-based stack; a Breeze child theme inherits one of the Swissup Breeze parent themes and overrides assets through the Breeze-specific web/css/breeze/ directory.

Core Rules

  • Breeze-required. Resolve magento2-context and read theme.breeze.installed. If it is false, do NOT scaffold — print the install path and stop:
    composer require swissup/breeze-evolution && \
      bin/magento setup:upgrade --safe-mode=1 && \
      bin/magento marketplace:package:install swissup/breeze-evolution
    
  • One theme per invocation. This skill produces exactly one child theme.
  • Append-safe. Never overwrite an existing theme.xml / registration.php; if the target theme directory already exists, stop and report rather than clobber.
  • Parent is a Breeze theme. The <parent> is Swissup/breeze-blank, Swissup/breeze-evolution, or Swissup/breeze-enterprise — default to the detected installed parent (theme.breeze.parent or the matched theme.breeze.packages), else ask.
  • Breeze overrides live in web/css/breeze/. Storefront CSS goes in web/css/breeze/_default.less (auto-included by Breeze on every page) and uses the @critical guard. web/css/source/_extend.less remains the Luma-side hook for any blank/luma fallback.
  • Coding style. Any generated PHP follows PER-CS 3.0 with the Magento 2 coding standard taking precedence; --standard=Magento2 PHPCS is the gate. See magento2-context/references/php-coding-style.md.
  • Source of truth. Generate from templates → shared references → baked-in Magento 2 knowledge → official Magento/Adobe docs (live-fetched only when uncertain). Do NOT read, grep, or "study" other modules under app/code/vendor/*/Magento core to infer conventions, entity shapes, naming, or wiring. Narrow exceptions: the target module/class of this operation, and the specific contract of a module this code explicitly depends on. Affirm sources in the final report. See magento2-context/references/source-of-truth.md.

Workflow

Phase 0 — Context Resolution

Invoke magento2-context. Capture theme.breeze (installed / active / parent / packages) and php_constraint / framework_constraint. Enforce the Breeze-required rule above.

Phase 1 — Inputs

Ask (offer detected defaults):

  • Vendor (PascalCase, e.g. Acme) — default {ctx.vendor}.
  • Theme name (e.g. BreezeCustom).
  • Parent theme: breeze-blank | breeze-evolution | breeze-enterprise — default = detected.
  • Title (human-readable, shown in admin).

Phase 2 — Generate

Target: {ctx.magento_root}/app/design/frontend/{Vendor}/{Theme}/.

If bin/magento is available AND the user opts in, prefer the Breeze generator and then layer the templated overrides on top:

{ctx.magento_cli} breeze:theme:create {vendor_lower}/{theme_lower} --parent=Swissup/breeze-{parent}

Otherwise scaffold manually from templates:

  • registration.php (from templates/theme-registration.php)
  • theme.xml (templates/theme.xml; <parent>Swissup/breeze-{parent}</parent>)
  • composer.json (templates/theme-composer.json)
  • web/css/breeze/_default.less (templates/breeze_default.less)
  • web/css/source/_extend.less (templates/_extend.less)
  • Magento_Theme/layout/breeze_default.xml (templates/breeze_default-layout.xml)

Phase 3 — Verify

  • xmllint --noout on theme.xml and the layout file.
  • php -l on registration.php.
  • Confirm the parent theme code matches an installed theme.breeze.packages entry.
  • Apply the shared module-hygiene baseline (required). After generating the theme's PHP files, run ${CLAUDE_PLUGIN_ROOT}/skills/magento2-context/scripts/add-license-headers.sh {ctx.magento_root}/app/design/frontend/{Vendor}/{Theme} {Vendor} to stamp the standard copyright header onto every new .php (e.g. registration.php; idempotent — it skips files that already carry it). When adding a composer.json require entry, resolve a bounded constraint via ${CLAUDE_PLUGIN_ROOT}/skills/magento2-context/scripts/resolve-dep-constraint.sh <vendor/package> — never "*". See magento2-context/references/module-hygiene.md.

Phase 4 — Report

Files created + activation:

{ctx.magento_cli} setup:upgrade
{ctx.magento_cli} setup:static-content:deploy -f

Then set the theme active in Content → Design → Configuration (per store view) or via config:set design/theme/theme_id.

Inputs

/magento2-breeze-child-theme [--vendor=Acme] [--name=BreezeCustom] [--parent=breeze-evolution]

Outputs

A registered Breeze child theme under {ctx.magento_root}/app/design/frontend/{Vendor}/{Theme}/.

Reference Files

  • references/breeze-theme-patterns.md — directory layout, parent choice, @critical LESS guard, web/css/breeze/ vs web/css/source/ and activation.
  • magento2-context/references/source-of-truth.md — source-of-truth hierarchy + the no-unrelated-module-scanning rule (allowed reads, live-doc fetch protocol, report affirmation).

Templates

  • templates/theme.xml
  • templates/theme-registration.php
  • templates/theme-composer.json
  • templates/breeze_default.less
  • templates/_extend.less
  • templates/breeze_default-layout.xml

Acceptance Criteria

  • The theme registers under app/design/frontend/{Vendor}/{Theme}/ with a Swissup/breeze-* parent.
  • theme.xml and the layout file pass xmllint --noout; registration.php passes php -l.
  • web/css/breeze/_default.less exists and uses the @critical guard.
  • The skill refuses (with the install command) when theme.breeze.installed is false.

Related Skills

PhaseSkill
0magento2-context
(sibling)magento2-frontend-create for non-Breeze themes/components
(next)magento2-breeze-module-adapt to adapt modules to the theme
(check)magento2-breeze-compat-audit to verify a module's Breeze compatibility

Keep looking

Skills are one crate of 610,220. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.