Skip to content
Skills Library
Programming · Building & coding

breeze-theme

/breeze-theme

Scaffold a Swissup Breeze (Breezefront) child theme: theme.xml with a Swissup/breeze-* parent, a Breeze-only layout handle, and web/css/breeze/_default.less overrides. Use for a new Breeze child or custom theme. Detects Breeze via magento2-tools:context (theme.breeze) and refuses when absent. Sibling to magento2-tools:frontend (generic Luma/Hyva/custom themes); this is Breeze-specific. Adapt a module: magento2-tools:breeze-adapt; check compatibility: magento2-tools:breeze-compat.

Licence
MIT
Last repository change
04.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
8
Scripts
1
HTML comments
0
URLs in SKILL.md
1
Deprecation

No signals detected. Repository changed on 04.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What to check before installing
  • 1 scripts in this package. Review them before installing, as Claude may execute them.

Scripts: templates/theme-registration.php

What it does and when to use it

Scaffold a Swissup Breeze (Breezefront) child theme: theme.xml with a Swissup/breeze-* parent, a Breeze-only layout handle, and web/css/breeze/_default.less overrides. Use for a new Breeze child or custom theme. Detects Breeze via magento2-tools:context (theme.breeze) and refuses when absent. Sibling to magento2-tools:frontend (generic Luma/Hyva/custom themes); this is Breeze-specific. Adapt a module: magento2-tools:breeze-adapt; check compatibility: magento2-tools:breeze-compat.

Original author description

Scaffold a Swissup Breeze (Breezefront) child theme: theme.xml with a Swissup/breeze-* parent, a Breeze-only layout handle, and web/css/breeze/_default.less overrides. Use for a new Breeze child or custom theme. Detects Breeze via magento2-tools:context (theme.breeze) and refuses when absent. Sibling to magento2-tools:frontend (generic Luma/Hyva/custom themes); this is Breeze-specific. Adapt a module: magento2-tools:breeze-adapt; check compatibility: magento2-tools:breeze-compat.

How it works

  1. Core Rules
  2. Workflow
  3. Inputs
  4. Outputs
  5. Reference Files
  6. Templates
  7. Acceptance Criteria
  8. Related Skills
Original SKILL.md headings · 135 lines, 672 words
SKILL.md preview
---
name: breeze-theme
version: 1.0.2
description: >-
  Scaffold a Swissup Breeze (Breezefront) child theme: theme.xml with a Swissup/breeze-* parent, a
  Breeze-only layout handle, and web/css/breeze/_default.less overrides. Use for a new Breeze child
  or custom theme. Detects Breeze via magento2-tools:context (theme.breeze) and refuses when absent.
  Sibling to magento2-tools:frontend (generic Luma/Hyva/custom themes); this is Breeze-specific.
  Adapt a module: magento2-tools:breeze-adapt; check compatibility: magento2-tools:breeze-compat.
---

# Magento 2 Breeze Child Theme

Scaffolds a [Swissup Breeze](https://breezefront.com/docs/child-theme) 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 `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
  `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
  `context/references/source-of-truth.md`.

## Workflow

### Phase 0 — Context Resolution

Invoke `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/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/context/scripts/resolve-dep-constraint.sh <vendor/package>`
  — never `"*"`. See `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

```
/breeze-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.
- `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

| Phase | Skill |
|-------|-------|
| 0 | `context` |
| (sibling) | `frontend` for non-Breeze themes/components |
| (next) | `breeze-adapt` to adapt modules to the theme |
| (check) | `breeze-compat` to verify a module's Breeze compatibility |
Files in this package (8)
  • SKILL.md 6 KB
  • references/breeze-theme-patterns.md 3 KB
  • templates/_extend.less 1 KB
  • templates/breeze_default-layout.xml 1 KB
  • templates/breeze_default.less 1 KB
  • templates/theme-composer.json 1 KB
  • templates/theme-registration.php 1 KB
  • templates/theme.xml 1 KB

Versions

The database has no other skills named breeze-theme.

Database snapshot: 13.11.2026 · package version 8fa1811cf1a6 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100frontend
    Frontend scaffolding for Magento 2: themes, RequireJS modules, Knockout components, LESS/CSS, transactional email templates, static asset wiring. Use to add frontend behaviour or a theme. Detects Luma, Hyva, or a custom theme and generates matching scaffolds. For Swissup Breeze…
  • 100breeze-adapt
    Adapt an existing Magento 2 module to Swissup Breeze by generating a companion module {Vendor}_{Module}Breeze that converts RequireJS/Knockout/jQuery widgets to Cash `$.widget`. Never edits the target, so it works on vendor/ modules. Use to make a module work with Breeze (needs…
  • 100breeze-x402-payment-api
    Operates Breeze x402 payment-gated endpoints for balance checks, deposits, and withdrawals on Solana. Use when the user asks to manage Breeze positions or execute paid x402 API calls.
  • 100magento-hyva
    Hyvä theme development for Magento 2 / Mage-OS / Adobe Commerce: building and customizing Hyvä storefronts with Alpine.js and Tailwind CSS, Magewire reactive server-driven components, child-theme setup and the Tailwind build, overriding Hyvä/Luma templates and layout XML, and…
  • 100airflow-aware
    This skill should be used when working in the apache/airflow repository as a contributor (not as a Dag author). It surfaces the conventions Airflow's own AGENTS.md enforces — naming, Breeze/uv environment, Ruff/Mypy style, coding rules, pytest patterns, PR hygiene — so any task…
  • 95bricks-child-theme-patterns
    Set up or debug a Bricks child theme, including asset loading and extension registration. Use for theme-level PHP/files, not ordinary Builder edits.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.