By zone1987
Shopware 6 Framework-Features: ScheduledTasks, MessageQueue, Rules, Flow-Builder, Store-/Admin-API-Routes, Webhooks, App-Scripts, Mail, Media.
Scaffold einer Shopware-6 Flow-Builder-Action (PHP + Admin-Komponente) inkl. requirements und Registrierung.
Scaffold einer Shopware-6 Custom Rule (PHP Rule + Admin-Bedingungs-Komponente) für den Rule Builder, inkl. Registrierung.
Scaffold eines Shopware-6 ScheduledTask + Handler inkl. services.xml-Registrierung (Task-Tag + Message-Handler).
Scaffold einer Shopware-6 Store-API-Route (Abstract + Route + Response-Struct) mit _routeScope store-api und Registrierung.
Eigener Admin-API-Endpunkt (Aktion) in Shopware 6: Controller mit _routeScope api, /api/_action/..., Auth via Bearer, ACL-Absicherung. Trigger: "Admin API Controller", "api/_action eigener endpoint", "_routeScope api", "custom admin api route", "Aktion Admin API", "AbstractController shopware api". Shopware 6.7.
Zugriffsrechte (ACL) für Admin-API/Backend in Shopware 6: _acl-Route-Default, Privileges (entity:read/update/...), Privilegien für eigene Entities/Aktionen registrieren, Zusammenspiel mit Admin-ACL. Trigger: "API ACL", "_acl route", "Privileges shopware", "Berechtigung api", "acl privilege entity:action", "Rechte Admin API". Shopware 6.7.
App Scripts in Shopware 6 (Twig-basierte Server-Logik für Apps): Script-Hooks, Resources/scripts/<hook>/, Services (data/store/cart), ohne eigenen App-Server. Trigger: "App Script", "Script Hook", "Resources/scripts shopware", "app scripting", "cart app script", "data loader script", "twig script app". Shopware 6.7.
Eigene Rule (Bedingung) für den Shopware-6 Rule Builder: Rule-Klasse (extends Rule), match(), constraints(), Admin-Komponente, Registrierung. Trigger: "Custom Rule", "Rule Builder eigene Bedingung", "extends Rule", "match() rule", "RuleConstraints", "eigene Regel shopware", "rule scope". Shopware 6.7. Scaffolder: /sw-rule.
Shopware Elasticsearch eigene Entities/Felder erweitern. Aktiviere wenn: eigene Entity in Elasticsearch indizieren, AbstractElasticsearchDefinition implementieren, eigene Felder in ES-Index, Custom Fields Mapping ES, ElasticsearchCustomFieldsMappingEvent, ElasticsearchFieldBuilder::translated, Produkt-Index erweitern, AbstractAdminIndexer eigene Admin-Suche, getMapping Shopware Elasticsearch.
Uses power tools
Uses Bash, Write, or Edit tools
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Ein Claude-Code-Marketplace mit 22 Plugins, 597 Skills, 38 Agents, 41 Commands und 3 Hooks — eine wachsende Sammlung von Wissens- und Werkzeug-Bibliotheken für verschiedene Web-Plattformen. Aktuell abgedeckt:
Weitere Plattformen/Frameworks sind geplant — die Struktur (Themen-Plugins mit Skills/Agents/Commands/Hooks) ist bewusst erweiterbar.
Das Wissen ist aus den offiziellen Quellen destilliert (Shopware-Trunk-Source, developer.shopware.com, docs.shopware.com, die offiziellen GitHub-Repos sowie die OCTO-/Ventrata-/Go-City-Doku) und in den Skills eingebettet (keine externen Laufzeit-Abhängigkeiten). Skills sind schlank; die Tiefe liegt in references/. Agents/Commands nutzen das je Aufgabe günstigste Modell (haiku/sonnet/opus).
1. Marketplace hinzufügen (GitHub oder lokaler Pfad):
/plugin marketplace add https://github.com/zone1987/claude-a-dev-team
2. Plugin(s) installieren — interaktiv über /plugin (Browse & install) oder gezielt:
/plugin install shopware-core@claude-a-dev-team
/plugin install shopware-data@claude-a-dev-team
/plugin install octo-api@claude-a-dev-team
# ... je nach Bedarf
3. Nutzung: Skills laden bei passendem Kontext automatisch; Commands stehen als /<command> bereit; Agents werden vom Orchestrator shopware-dev (bzw. octo-api-expert, shopware-merchant-guide) oder direkt genutzt.
Tipp: Für reine Shopware-Entwicklung genügen oft
shopware-core,shopware-data,shopware-framework,shopware-storefront,shopware-admin. Headless zusätzlichshopware-frontends/shopware-api; Bedienung/Betriebshopware-merchant.
{
"extraKnownMarketplaces": {
"claude-a-dev-team": { "source": { "source": "github", "repo": "zone1987/claude-a-dev-team" } }
},
"enabledPlugins": [
"shopware-core@claude-a-dev-team",
"shopware-data@claude-a-dev-team"
]
}
Jedes Plugin ist ein eigenständig installierbares Themenpaket. Details in der jeweiligen Plugin-README (Plugin-Name verlinkt).
| Plugin | Wofür | Skills | Agents | Commands |
|---|---|---|---|---|
shopware-core | Plugin-Fundament: DI, Decoration, Events/Subscriber, CLI, Config, Logging, Filesystem, Rate-Limiter, Feature-Flags, NumberRange, SystemConfig + Event-Katalog. | 18 | 3 | 4 |
shopware-data | DAL komplett (Entities/Fields/Flags/Associations/Translations/Criteria/Hydration) + vollständige Core-Entity-Referenz (312 Entities) + Entity-Introspektion. | 33 | 2 | 5 |
shopware-framework | ScheduledTasks, MessageQueue, Rules, Flow, Store-/Admin-API-Routen, ACL, Webhooks, App-Scripts, Mail (+Variablen-Baum), Media, Elasticsearch, Redis. | 25 | 1 | 4 |
shopware-checkout | Cart-Pipeline, Payment (6.7) & App-Payment, Shipping, Order-StateMachine, Dokumente (ZUGFeRD), Promotions, Kunden. | 20 | 1 | 3 |
shopware-cms | Eigene CMS-Blöcke, CMS-Elemente und DataResolver (Erlebniswelten). | 7 | 1 | 2 |
| Plugin | Wofür | Skills | Agents | Commands |
|---|---|---|---|---|
shopware-storefront | Controller/Pages/Twig/SCSS/Themes, JS-Storefront-Plugins, TypeScript, Accessibility + JS-Plugin-/Event-/SCSS-Introspektion. | 39 | 2 | 4 |
shopware-admin | Vue 3 / Pinia / Vite / Meteor: Module, Komponenten, Routing, Data-Handling, Services, ACL, Admin-SDK, TypeScript + Admin-Introspektion. | 29 | 2 | 3 |
shopware-frontends | Headless (Shopware Frontends): api-client, composables, api-gen, cms-base, Vue 3 / Nuxt, Routing/i18n/B2B. | 19 | 1 | 0 |
npx claudepluginhub zone1987/claude-a-dev-team --plugin shopware-frameworkShopware 6 Versions-Migration: 6.6→6.7→6.8, Meteor-/Vite-/Pinia-Migration, Deprecation-Handling, Upgrade-Guides.
Shopware 6 Qualität: Coding-Guidelines, ADR-Wissen, Domain-Exceptions, Static-Analysis, README-Generator — plus selbstaktualisierender Knowledge-Sync.
Shopware 6 Checkout: Cart-Processors, LineItems, Preise, Tax, Payment-Handler, Shipping, Order-StateMachine, Dokumente, Promotions.
Shopware Frontends — headless/composable storefronts: @shopware/api-client, @shopware/composables, @shopware/api-gen, cms-base, helpers, Vue 3 / Nuxt.
Shopware 6 App-Entwicklung: Manifest, Webhooks, Auth, App-Scripts, Payment-/Tax-/CMS-/Flow-Gateways, IAP, JS-/PHP-SDK.
Comprehensive UI/UX design plugin for mobile (iOS, Android, React Native) and web applications with design systems, accessibility, and modern patterns
Multi-model consensus engine integrating OpenAI Codex CLI, Gemini CLI, and Claude CLI for collaborative code review and problem-solving.
Ultra-compressed communication mode. Cuts ~75% of tokens while keeping full technical accuracy by speaking like a caveman.
Standalone image generation plugin using Nano Banana MCP server. Generates and edits images, icons, diagrams, patterns, and visual assets via Gemini image models. No Gemini CLI dependency required.
Write feature specs, plan roadmaps, and synthesize user research faster. Keep stakeholders updated and stay ahead of the competitive landscape.
Curate auto-memory, promote learnings to CLAUDE.md and rules, extract proven patterns into reusable skills.