From shopware-migration
Migration der Shopware-Admin-Komponenten von sw-* zu Meteor mt-* (6.6→6.7): Komponenten-Mapping, geänderte Props/Events/ Slots, v-model:value, Ersetzungsstrategie. Trigger: "sw- zu mt-", "Meteor migration", "mt-button mt-text-field mt-select", "Komponenten mapping shopware", "sw-card mt-card", "v-model:value meteor". Shopware 6.7.
How this skill is triggered — by the user, by Claude, or both
Slash command
/shopware-migration:sw-meteor-component-mapThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
In 6.7 lösen Meteor-Komponenten (`mt-*`) die Legacy-`sw-*`-Komponenten ab. Migration = Komponenten ersetzen +
In 6.7 lösen Meteor-Komponenten (mt-*) die Legacy-sw-*-Komponenten ab. Migration = Komponenten ersetzen +
geänderte Props/Events/Slots anpassen.
| Legacy | Meteor | Häufige Änderung |
|---|---|---|
sw-card | mt-card | Slots/Props teils anders |
sw-button | mt-button | variant/ghost statt alter Props |
sw-text-field | mt-text-field | v-model:value statt v-model |
sw-select/sw-single-select | mt-select | Optionen/Events angepasst |
sw-alert | mt-banner | — |
sw-modal | mt-modal | — |
Vorgehen: Template-Komponenten ersetzen, v-model → v-model:value (wo nötig), Event-Namen prüfen, Deprecation-Warnungen
auflösen. Mapping-Details + Beispiele in den References des Skills shopware-6.7-migration.
→ ../shopware-6.7-migration/references/component-mapping.md, ../shopware-6.7-migration/references/component-examples.md
Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.
npx claudepluginhub zone1987/claude-a-dev-team --plugin shopware-migration