Skip to content
5.0 Upwork, 100+ reviews Adobe Certified since 2021 New: become your own Magento developer Learn more →
Free · Runs in your browser · No signup

Generate a Claude-Code-ready Magento module: in 30 seconds

Configure the form, watch the file tree fill in, then download. Then learn the workflow one topic at a time, with the prompts I use on real stores.

  • 100% client-side, nothing uploaded
  • Up to 18 files per module
  • Magento 2.4.4 to 2.4.9
  • CLAUDE.md and slash-commands included
Panth_CustomerLoyalty.zip 18 files · built in your browser
  • Adobe Certified since 2021
  • 60+ free MIT extensions
  • Hyvä and Luma
  • Magento 2.4.4 to 2.4.9
  • 5.0 from 100+ Upwork reviews
Free module generator

Configure your module

The file tree rebuilds as you type. The ZIP is built in your browser: no upload, no API key, no tracking.

Describe your module (smart-fill)

Describe what you want in normal words. Click Smart-fill: keywords like "admin grid", "cron", "email", "plugin around", "GraphQL", "Hyvä", "queue", "indexer" toggle options + add rows below.

Quick-start presets
Identity
Stack
Includes: Magento boilerplate
Includes: quality + AI workflow

Each table generates db_schema.xml entries + whitelist + an idempotent seed patch.

Each grid emits routes + acl + menu + controller + UIComponent listing + DataProvider.

UIComponent admin form + DataProvider + Save/Delete controllers per entity.

Routes XML + controller + layout + ViewModel + Luma/Hyvä template per row.

email_templates.xml + .html template + EmailSender helper per row.

crontab.xml + Cron/<JobName>.php with LockManagerInterface.

etc/<area>/events.xml + Observer/<Name>.php per row.

etc/di.xml <type> entries + Plugin/<Name>.php with correct method signature.

system.xml + config.xml defaults per group.

communication + queue_consumer + queue_topology + queue_publisher + Consumer class.

indexer.xml + mview.xml + Model/Indexer/<Name>.php (ActionInterface).

cache.xml + cache instance class implementing FrontendInterface bridge.

Tip: ⌘ + Enter to download

Vendor and Module must be PascalCase letters/digits only.

After download

Three commands to a running module

  1. 1

    Unzip into app/code/

    $ unzip Panth_CustomerLoyalty.zip -d app/code/

    The folder lands as app/code/Vendor/Module.

  2. 2

    Enable and upgrade

    $ bin/magento module:enable Panth_CustomerLoyalty
    $ bin/magento setup:upgrade --keep-generated

    The module registers on a clean 2.4.4 to 2.4.9 install.

  3. 3

    Open in Claude Code

    $ cd app/code/Panth/CustomerLoyalty
    $ claude

    Claude reads the generated CLAUDE.md first. Try /scaffold-feature as your first prompt.

Inside the ZIP

Honest, hand-tuned Magento boilerplate

Every file comes from a template I refined across 60+ shipped Magento extensions. No filler comments, no TODOs to delete, no dead code.

  • phpcs Magento2
  • phpstan L6
  • setup:upgrade
  • Magento-correct on first compile

    registration.php, composer.json, module.xml and di.xml aligned to your Magento version. PSR-12 ready, PHP 8.x type hints.

  • Declarative schema, never raw SQL

    Optional db_schema.xml and whitelist, plus an idempotent DataPatchInterface seed.

  • ACL + admin-grid done right

    acl.xml, menu, routes, the controller and a UI component listing.

  • CLAUDE.md tuned to your module

    Your vendor and module names in a hard-rules file: PSR-12, no vendor edits, plugins over rewrites.

  • Slash-commands ready to use

    /scaffold-feature and /run-tests with a .claude/settings.json permission allowlist.

  • Tests, not afterthoughts

    An optional MFTF action and a PHPUnit test that runs. The skeleton ships green.

FAQ

Honest answers about the generator

Form data uploaded
None
Signup or email gate
None
Price
Free
Is this really free? What’s the catch?

Genuinely free, no signup, no email gate. The page is a static HTML/JS bundle running on this Magento store; the ZIP build happens entirely in your browser using JSZip. No telemetry, no API key, no upload. The catch (if you want to call it that): if you want the module shipped, tested, and Marketplace-pass rather than just scaffolded, that’s what I do for a living.

Where does my form data go?

Nowhere. The form values, the file templates, and the ZIP-build all run inside your browser tab. Open the network tab in dev-tools while you click Download, you’ll see zero outbound requests. Only the page itself was loaded from this server. The optional Share config link button encodes your form state into a URL locally and copies it to your clipboard; it’s only sent anywhere if you choose to paste and share it.

Will the generated module actually compile and activate?

Yes. Every template is hand-written from 60+ shipped Magento extensions and tested end-to-end, the output passes phpcs --standard=Magento2, phpstan --level=6, and bin/magento module:enable + setup:upgrade on a clean Magento 2.4.4-2.4.9 install. Drop the unzipped folder into app/code/<Vendor>/<Module>/, run the three commands shown on this page, and your module is registered.

What do you mean by “2050-grade”?

Honestly, marketing speak. What I actually mean: every optional flag generates the modern Magento pattern, not the legacy one.

  • Service Contracts, Api/Data interfaces + Repository, the way Adobe’s own modules ship.
  • GraphQL schema, declarative queries + mutations + filters, wired to the Repository.
  • etc/webapi.xml, REST CRUD that re-uses the same Repository (no duplicated logic).
  • GitHub Actions CI, phpcs + PHPStan + PHPUnit gates on every push.
  • Sub-agents, .claude/agents/code-reviewer.md + test-writer.md, ready for Claude Code to spawn in parallel.
  • Conventional Commits + SemVer + CHANGELOG, release-ready from day 0.
Should I use a preset or build from scratch?

Use a preset to set the right baseline, then tick / untick individual options. Recommended starting points:

  • Hyvä storefront, Tailwind + Alpine.js, no Luma cruft.
  • B2B with API, service contracts + REST + GraphQL, no storefront.
  • Marketplace-pass, everything on, EQP-aligned.
  • Minimal, just registration.php + module.xml + a tuned CLAUDE.md. For when you want to build the rest yourself.
Can I customise the templates the generator uses?

The templates live as JavaScript string-literals inside the /claude page’s phtml, not behind a build step. Right-click → View source, search for templates(). Every template is one function returning a string. If you want changes upstreamed, open a PR or message me on WhatsApp, the page is open-source-friendly even though the site itself isn’t licensed publicly.

How does the “Share config link” button work?

It encodes every form field (vendor, module name, description, version, frontend, type, and the 16 option toggles) into URL query parameters and copies the resulting URL to your clipboard. Send the link to a teammate, when they open it, the form pre-fills with the exact same configuration. Useful for “here’s the module spec, just download the ZIP” handoffs.

How does this help me on day 0 with Claude Code?

The generated CLAUDE.md is pre-filled with your Vendor/Module names, your Magento version, your frontend choice, and a hard-rules block that locks Claude into PSR-12, phpcs Magento2, no-vendor-edits, plugins-over-rewrites, db_schema not raw SQL, MFTF + PHPUnit alongside features. The .claude/commands/scaffold-feature.md and .claude/commands/run-tests.md slash-commands are ready to invoke. Open the unzipped folder in claude, type /scaffold-feature, and you’re shipping. Full setup guide here.

Claude Code for Magento Free prompts and tools Ask me