What problem does it solve? Working on OpenCart 1.5.6 codebases requires following legacy conventions that differ sharply from modern frameworks like Laravel, and mixing them up leads to broken assumptions about architecture, tooling, and PHP features. ## Core Features & Use Cases - Legacy MVC Guidance: Enforces OpenCart's classic controller/model/view structure under catalog/ and admin/ with registry-based dependency injection and thin controllers. - vQmod Awareness: Directs debugging toward the compiled vqcache files rather than original sources, and preserves existing vqmod XML modifications. - PHP Version Matching: Requires matching the exact production PHP version per project and avoiding modern PHP features unless confirmed available. - Use Case: When adding a customizable label to a multi-site OpenCart store, the Skill ensures the value comes from a theme_settings database field instead of a hardcoded literal that would break other sites sharing the core code. ## Quick Start Apply the opencart-legacy conventions while modifying the product controller in this OpenCart 1.5.6 project.