Warden environment operations for Magento 2: database queries, Magento CLI commands, DB import/export, environment management, and shell access. Use when user asks to "run warden", "check database", "warden db connect", "run magento command", "import db", "export db", "warden shell", or any task involving the Warden local development environment. Do NOT use for code generation, frontend, or non-Warden environments.
Scaffold Magento 2 backend modules, system.xml admin configs, widgets with parameters and templates, plugins/events/observers, transactional email with trigger setup, and Hyva-compatible .phtml templates with ViewModels. Use when user asks to "create module", "scaffold module", "generate plugin", "add system config", "create widget", "setup email template", "create hyva template", or any Magento 2 backend code generation. Do NOT use for frontend-only tasks, CSS/JS theming, or Magento 1.x.
Magento 2 best practices for database queries and CSV exports. Use when writing SQL queries, fetching data from DB, or exporting data to CSV files. Triggers on tasks involving raw SQL, SELECT queries, JOIN operations, CSV generation, or file export adapters. DO NOT use for frontend, caching, or search topics.
Custom per-class log files in Magento 2 using di.xml virtual types — no PHP class needed. Use when the user says "custom logger", "dedicated log file", "separate log file", "log to my own file", "virtual type logger", or wants a Console Command / Service to write to a specific var/log/ path. DO NOT use for general Magento logging via \Psr\Log\LoggerInterface already injected by the framework, or for frontend/JS logging.
Database query optimization patterns for Magento 2 — bulk operations, EAV manipulation, CSV multiselect replacement, and custom loggers. Use when writing migration scripts, Console Commands with DB loops, bulk update operations, or any code where a loop contains DB queries. DO NOT use for frontend, caching, indexing, or search performance topics.