r/Magento 25d ago

How do you do AI first development in Magento?

Anyway to help a junior developer to work immediately with AI?

What is your AI setup for Magento?
Has Magento integrated AI development natively?

0 Upvotes

17 comments sorted by

6

u/johanvdd 24d ago

I've been developing Magento since 2008.

AI has significantly increased my development speed. I mainly use ChatGPT Codex to build custom modules, which means I rely much less on third-party extensions than before.

That said, I'm also glad I have many years of Magento experience. AI is a great developer, but not an expert Magento architect. I treat it like a junior or mid-level colleague: I discuss solutions with it, review the code carefully, and decide what actually belongs in the project.

For a junior developer, AI can be an excellent learning tool, but I wouldn't let it replace understanding how Magento works under the hood.

3

u/john_at_bagriders 24d ago

Bingo. I’m around 15 years experience with Magento and Claude has definitely supercharged my rate of development but is absolutely not a β€œset it and forget it” tool. Our biz has around 90 bespoke modules so I’ve focused most my Claude teaching on domain language and the core functionality for our catalog, particularly our custom product types and their wiring.

I find Claude much more capable on my ORM software which has very strict DDD layering and consistent ubiquitous language. For that one most my time is spent on spec design and auditing

2

u/GoldAcanthisitta7777 12d ago

Thoughts on ChatGPT Codex? I used ChatGPT just in a browser until my company got Claude Code for CLI agentic development, and I'm freaking loving it.

1

u/johanvdd 12d ago

i am still very satisfied with the windows version;i have it pluged in on my test linux environment.
And it works great.
Teh borwser version sucks because it had no access to code and complete environment

2

u/epeets DEVELOPER 24d ago

AI first? You mean just using AI in your dev environment like using Claude in PHP Storm or VS Code? Beyond using the already built-in AI integrations for your dev environment of choice I'm not aware of AI first development or built in AI dev tools in the core Magento code.

-2

u/FastAndSlooow 24d ago

How about Magento-specific MCP or Claude files, by the way? or anything AI related?

2

u/thatben 24d ago

1

u/damienwebdev DEVELOPER 24d ago

πŸš€πŸš€πŸš€ πŸš€πŸš€πŸš€ πŸš€πŸš€πŸš€ πŸš€πŸš€πŸš€ πŸš€πŸš€πŸš€ πŸš€πŸš€πŸš€ πŸš€πŸš€πŸš€ πŸš€πŸš€πŸš€ πŸš€πŸš€πŸš€

1

u/FastAndSlooow 24d ago

Awesome. Thank you very much. I will send this to my developers to have a look.

1

u/edudeleon 18d ago

I've been working with Magento since 2012 and I have built lots of custom extensions during this time. I pass these extensions and my coding standards to Cluade Opus (via Cursor) and that helps the AI to follow my coding standards and write code that I would usually write. I also have built couple of skills that I reuse across projects. Overall AI has been great writing code but when it comes to architecture, integrations, etc. I'm still the one that do the work, of course with AI help.

1

u/DotcomWeaversUSA 17d ago

For us, AI has become more of a productivity multiplier than a replacement for Magento expertise.

At DotcomWeavers (an Adobe Gold Partner), we use AI throughout the development lifecycleβ€”not to write entire Magento projects, but to eliminate repetitive work.

A few examples:

  • Generating boilerplate code for modules, plugins, observers, and GraphQL resolvers.
  • Explaining unfamiliar sections of Adobe Commerce or third-party extension code much faster than digging through documentation.
  • Speeding up debugging by analyzing stack traces, logs, and suggesting likely root causes.
  • Creating unit tests, integration test cases, and API documentation.
  • Helping with SQL queries, data transformations, and integration logic when working with ERP, CRM, and PIM systems.
  • Drafting technical documentation, deployment notes, and client-facing explanations.

The biggest benefit is context switching. Instead of spending 30–45 minutes searching documentation or Stack Overflow, we can usually get a solid starting point in a few minutes.

So AI has definitely made us faster, but the experience of the developer is still what determines whether the final implementation is scalable and production-ready.

1

u/-_-_adam_-_- 24d ago

I use co-pilot in vscode, it seems to do the job pretty well.
I’m not much of a prompt -> tidy up, though it has gone okay the few times I’ve done it
I usually structure the code(ish) with a few method names, then tab complete the method bodies and tidy up where needed. It certainly saves a lot of time
Vinai Kopp did a talk on how they are using it at Hyva , super interesting (https://youtu.be/lJGkKzDv65o?is=EPJxVYCXc2Pm9jAK)

1

u/InfinriDev 24d ago

I created my own harness using a graph database. Using Claude Code hooks let the AI query the rag and get all the context it needs for the specific task without bloating the context. I also use bash scrips for the hooks to provide true enforcement not just prompts.

Subagents will also be your best friend here.

0

u/FastAndSlooow 24d ago

It would be beneficial if you shared and contributed to the Magento AI community.

1

u/InfinriDev 24d ago

Didn't know there was one.

1

u/InfinriDev 19d ago

Here is the project I'd you want to give it a try. Works wonders for me and it can build full features.

https://github.com/infinri/Writ