Some projects are too valuable to abandon.
After years of working with Magento, I’ve seen how much time developers spend repeating familiar steps, tracing configuration across files, and fixing mistakes that better tooling could help prevent.
The Magento PhpStorm plugin was built by community members who invested their time and ideas in it. When its future became uncertain, I didn’t want that work—or a tool developers relied on—to disappear. I decided to take responsibility for bringing it back and building on what was already there.
Almost a year to restore access.
Restoring the access and permissions needed to maintain and distribute the plugin took almost a year.
A COMMUNITY EFFORT
I’m deeply grateful to the entire Magento Community Engineering team, especially Igor Miniailo, Olena Orobei, and Sergii Ivashchenko, for their help throughout that process. Without them, bringing the plugin back would not have been possible.
From revival to long-term maintenance.
As the primary maintainer, I guide the plugin’s technical direction, develop features, review contributions, investigate issues, maintain automated tests, check compatibility with new JetBrains IDE releases, and prepare releases. I work with contributors to keep improving the tool and make it dependable for the community.
Automate the repetitive work.
I’ve always been drawn to automation. When I catch myself repeating the same steps or tracing the same configuration across files, I start thinking about how a tool could handle that work.
Saving time is part of it. So are reducing mistakes, improving consistency, and making a complex system easier to understand. Good automation gives developers more control: they can see what is happening, inspect the result, and spend their attention where engineering judgment matters.
That idea connects my work on this plugin with automated testing, code coverage, and AI-assisted development.
Magento knowledge, inside the IDE.
The Magento 2 and Adobe Commerce IDE Plugin brings platform-specific understanding into everyday development. Its features help both people and connected AI assistants work with the actual project.
Start with the right structure
Generate modules, plugins, observers, controllers, CLI commands, and other Magento components without rebuilding the same boilerplate by hand.
Follow the connections
Move between dependency injection, plugins, observers, layouts, XML configuration, JavaScript components, and templates.
Catch mistakes earlier
Use Magento-aware inspections and completion to spot configuration and code problems while working in the editor.
Use the right environment
Discover CLI wrappers and n98-magerun2 commands so developers and AI tools can run Magento commands in the project’s intended Docker, local, or remote environment.
Give AI project context
Through MCP integration, connected AI assistants can query Magento configuration and use deterministic generation tools as part of AI-assisted development.
Work in PhpStorm or WebStorm
The plugin supports PhpStorm and WebStorm. Available features depend on the IDE and its PHP support.
Explore the plugin’s project intelligence and MCP workflow ↗
Small improvements, shared widely.
The plugin is downloaded thousands of times every month.
Knowing that developers around the world use and benefit from the work makes maintaining it especially meaningful to me.
Keep building for what comes next.
I want to keep improving the plugin’s MCP integration so AI assistants can work with real Magento configuration and use reliable tools that developers can review.
Long-term sustainability matters just as much. Tests, compatibility work, documentation, thoughtful reviews, and welcoming contributors help make progress something the community can continue to build on.
BUILT FOR THE COMMUNITY
Use it. Improve it. Keep it alive.
Try the plugin, report an issue, suggest an improvement, test a release, or contribute code or documentation.