OBSERVABILITY
Seq MCP
Give an AI assistant access to structured events, SQL queries, and traceable runtime evidence. Pair it with Magento Seq for local instrumentation.
VITALII BOIKO / DEVELOPER & OPEN-SOURCE MAINTAINER
Make AI
more
predictable.
I build deterministic tools that give AI agents real context, observable behavior, and verifiable feedback. Less guesswork. Better engineering.
Telemetry. Code coverage. IDE intelligence.
THE FEEDBACK LOOPDESIGNED FOR EVIDENCE
Adobe Commerce architect. Tools for a more reliable development loop.
MAGENTOJETBRAINSOPEN SOURCE
01 / SELECTED WORKTools that close
Tools that close
the feedback loop.
A connected approach to AI-assisted development: understand the code, observe the system, then test the change.
↗
TESTING & COVERAGE
MageLens
See which code your browser tests actually execute. Bring PHP, JavaScript, and Magento template coverage into one browsable report.
PROJECT INTELLIGENCE
Magento and Adobe Commerce IDE plugin
Give agents Magento-specific context: modules, dependency injection, observers, layouts, and configuration. Built on the project open in your IDE.
Built in the open, for real development workflows.
All repositories02 / THE APPROACHGive AI something
Give AI something
it can check.
An agent’s proposal is a starting point. I build the tools that let it inspect the project, compare its assumptions with runtime behavior, and verify a change.
- 01Get context from the actual project.
- 02Make runtime behavior observable.
- 03Check outcomes with tests and coverage.
The goal is a more predictable workflow. The model still reasons; the tools make its claims easier to verify.
ANATOMY OF A BETTER ANSWER
Which observer handles this event?
source Magento IDE / MCP event checkout_submit_all_after module Acme_Checkout evidence etc/events.xml:8 → A declaration the agent can inspect.
What happened during this request?
source Seq / structured events request checkout-demo-001 event payment.authorize result upstream_timeout → A runtime signal to investigate.
Did the test reach the changed code?
source MageLens / coverage test checkout retry scenario PHP retry handler executed template error binding not exercised → A specific gap for the next test.
ILLUSTRATIVE WORKFLOW · Sample data, not a live tool response.
03 / THE PERSON BEHIND THE TOOLSBuilt in the open.
Built in the open.
Grounded in practice.
Vitalii BoikoAdobe Commerce architect & developer
I work on large B2B Magento and Adobe Commerce projects, developer tooling, and test automation. My focus is turning complex systems into software that teams can understand, change, and verify.
I maintain the Magento and Adobe Commerce IDE plugin and build open-source tools around observability, coverage, and practical AI workflows.
That experience shapes a simple conviction: AI development gets more useful when its feedback comes from the real system.
04 / IN PRACTICE
See the tools at work.
Walkthroughs from my development workflow.
LET’S BUILD SOMETHING VERIFIABLE
Better tools.
More dependable AI.
Working on AI developer tools, Magento architecture, or a testing problem? Let’s compare notes.
05 / CERTIFICATIONSExperience, backed
Experience, backed
by credentials.
Adobe Commerce certifications across architecture, development, and the front end. Each badge links to its Adobe verification record.
