Claude, Module Generator: 8 questions answered.

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.

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 email me, the page is open-source-friendly even though the site itself isn’t licensed publicly.

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.

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.

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.

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.

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.

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.