By staksoft
Claude skills for Magento 2 / Mage-OS / Adobe Commerce development: module scaffolding, plugin/observer/DI conventions, declarative schema, REST/GraphQL, CLI/cron, PHPUnit testing, Hyva theme development (Alpine/Tailwind/Magewire), debugging playbooks, and storefront performance audits.
Performance audit of a Magento 2 / Mage-OS / Adobe Commerce storefront: full-page cache misses and cacheable="false" leaks, Varnish/Redis configuration, indexer modes and cron health, TTFB, payload sizes, and Core Web Vitals. Use this skill whenever the user says a Magento store is slow, asks to audit/review/check storefront performance, mentions FPC or cache hit rate, X-Magento-Cache-Debug, Varnish not caching, high TTFB, stuck or realtime indexers, cron problems, or Core Web Vitals / PageSpeed scores for a Magento or Mage-OS site. Works from a URL alone, from a codebase alone, or both. For writing or fixing module code, use the magento-module skill instead.
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 Luma-to-Hyvä compatibility. Use this skill whenever the user mentions Hyvä (hyva), or is doing Magento frontend work with Alpine.js, Tailwind, or Magewire — creating or styling a Hyvä theme, writing Alpine components in .phtml, configuring tailwind.config.js, building a Magewire component, fixing a Luma module that breaks on Hyvä, or converting a storefront from Luma to Hyvä. Strong triggers: "hyva theme", "alpine.js in magento", "tailwind in magento", "magewire", "my hyva component isn't reactive", "convert luma to hyva". For backend/module work (plugins, observers, db schema, DI, REST/GraphQL, CLI) use the magento-module skill; for storefront performance audits use the magento-audit skill.
Correct Magento 2 / Mage-OS / Adobe Commerce module development: scaffolding new modules, extending or customizing core behavior (plugin vs observer vs preference decisions), declarative schema and custom tables, product/EAV attributes, dependency injection, checkout/cart/totals and custom order or shipping fee logic, admin configuration (system.xml/ACL), admin grids and ui_components, layout XML and view models, upgrading or migrating custom modules (incl. to Mage-OS) and their composer.json constraints, and debugging playbooks for setup:di:compile failures, layout not applying, and observers/plugins that don't fire. Use this skill whenever the user is writing, modifying, or debugging custom Magento, Mage-OS, or Adobe Commerce code — creating or extending a module/extension, intercepting core behavior, adding database tables or attributes, building admin settings or grids, frontend blocks or templates, or fixing errors from bin/magento commands — even if they don't say "module" explicitly. Strong triggers: "how do I override X in Magento", "my Magento layout/plugin/observer isn't working", "do I use an observer or a plugin", or anything touching app/code, di.xml, events.xml, db_schema.xml, or layout XML. Do NOT trigger for storefront performance/cache audits (use the magento-audit skill), buying or recommending third-party extensions, operational admin tasks (creating coupons, importing product CSVs, session/login settings), Magento hosting/sizing questions, content/SEO copy, or non-Magento platforms like Shopify or WooCommerce.
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.
magento-claude-skills is a free, open-source Claude Code plugin that gives Claude (and the Claude Agent SDK) expert, current knowledge of Magento 2, Mage-OS, and Adobe Commerce development. It makes the AI scaffold modules correctly, choose the right extension mechanism, and audit storefront performance — producing code that compiles with bin/magento setup:di:compile and passes phpcs --standard=Magento2 on the first try.
Maintained by StakSoft, a software studio with 10+ years of Magento and e-commerce engineering experience. Verified against Mage-OS 3.0.0 / Magento 2.4.9 on PHP 8.3.
Three skills that load on demand when you ask Claude a relevant question:
| Skill | What it does | Triggers on |
|---|---|---|
magento-module | Scaffold and extend Magento modules the right way — plugin vs observer vs preference decisions, declarative schema, dependency injection, admin UI, layout XML, REST/GraphQL APIs, CLI/cron/queues, PHPUnit testing, and debugging playbooks. | "create a Magento module", "observer or plugin?", "my layout XML isn't working", "setup:di:compile fails" |
magento-hyva | Hyvä theme development — Alpine.js + Tailwind CSS components, Magewire reactive components, child-theme setup and the Tailwind build, overriding templates/layout, and Luma→Hyvä compatibility. | "build a Hyvä theme", "Alpine.js in Magento", "Tailwind in Magento", "Magewire", "convert Luma to Hyvä" |
magento-audit | Performance audit of a Magento storefront — full-page cache leaks (cacheable="false" scanner), Varnish/Redis/env.php config, indexer and cron health, TTFB and Core Web Vitals. Works from a URL, a codebase, or both. | "my Magento store is slow", "audit storefront performance", "Varnish not caching", "FPC hit rate" |
In a benchmark of real module-build and debugging tasks, the magento-module skill scored 100% vs an 86% baseline (no skill) on a Mage-OS 2.4.9 install — every generated module compiled and passed the Magento coding standard.
Option 1 — npx skills (recommended, fastest): the vercel-labs/skills CLI installs all three skills into .claude/skills/. No clone needed.
npx skills add staksoft/magento-claude-skills -a claude-code
Add -g for a global install (all projects), or -y for non-interactive/CI.
Option 2 — Claude Code plugin marketplace: installs the whole plugin.
claude plugin marketplace add staksoft/magento-claude-skills
claude plugin install magento-skills
Option 3 — from a local clone:
git clone https://github.com/staksoft/magento-claude-skills.git
claude plugin install ./magento-claude-skills
The skills trigger automatically from natural language, or you can invoke them explicitly.
npx claudepluginhub staksoft/magento-claude-skills --plugin magento-skillsComprehensive skill pack with 66 specialized skills for full-stack developers: 12 language experts (Python, TypeScript, Go, Rust, C++, Swift, Kotlin, C#, PHP, Java, SQL, JavaScript), 10 backend frameworks, 6 frontend/mobile, plus infrastructure, DevOps, security, and testing. Features progressive disclosure architecture for 50% faster loading.
Develop, test, build, and deploy Godot 4.x games with Claude Code. Includes GdUnit4 testing, web/desktop exports, CI/CD pipelines, and deployment to Vercel/GitHub Pages/itch.io.
Comprehensive feature development workflow with specialized agents for codebase exploration, architecture design, and quality review
Design fluency for frontend development. 1 skill with 23 commands (/impeccable polish, /impeccable audit, /impeccable critique, etc.) and curated anti-pattern detection.
Behavioral guidelines to reduce common LLM coding mistakes, derived from Andrej Karpathy's observations on LLM coding pitfalls
Tools to maintain and improve CLAUDE.md files - audit quality, capture session learnings, and keep project memory current.