ddtcorex/maestro-skills / skills/magento2-dev-core
magento2-dev-core
VerifiedUse for Magento 2 module work: architecture, dependency injection, repositories, plugins, secure backend code, CLI, cron. Core skill, always load it first. Keywords dependency injection, plugin.
references/config-files.md
View on GitHub# Configuration files
The `etc/` files a module ships, what each one declares and when it is required.
Quick lookup for what each `etc/` XML file controls:
| File | Purpose |
|------|---------|
| `di.xml` | Dependency injection: preferences, plugins, virtual types |
| `events.xml` | Observer registration |
| `crontab.xml` / `cron_groups.xml` | Cron jobs / cron group tuning |
| `acl.xml` | Admin permission tree |
| `routes.xml` | Frontend/adminhtml controller routing |
| `webapi.xml` | REST route declarations |
| `system.xml` | Admin configuration fields |
| `config.xml` | Default config values |
| `indexer.xml` + `mview.xml` | Indexer declaration + its change tracker (enables schedule mode) |
| `extension_attributes.xml` | Extend a core entity without a preference |
| `view.xml` | Theme image/gallery sizing, layout config |
| `communication.xml` + `queue_topology.xml` + `queue_publisher.xml` + `queue_consumer.xml` | Message queue topics, exchanges and bindings, publishers, consumers (the single `queue.xml` is legacy since 2.2) |
| `widget.xml` | CMS widget declaration |
| `email_templates.xml` | Transactional email template registration |
**Rule of thumb**: stale *data* is an indexer problem (check `indexer:status`); stale *output* is a cache problem (`cache:clean`/`cache:flush`). Diagnose in that order rather than assuming a cache bug.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |