ai-mms

Bring a franchise partner storefront (Ghana .com.gh, Malaysia .com.my, or a new country) to full parity with Singapore for NON-WSQ courses — import courses, mirror the category tree + mega-menu, sync product↔category assignments, category banners/descriptions, currency switcher, remove SG-only funding text, fix fonts/banners, WhatsApp, contact/footer/trainer info, and the blog. Use when asked to "make GH same as Singapore", "port courses to the partner site", "the <country> categories/menu/blog/footer are different from SG", "add currency switcher / WhatsApp to <country>", "remove funding on <country>", or when onboarding/refreshing a franchisee site. Everything here is PARTNER-DB-ONLY (never a repo/code change, never touch SG).

Enforce the storefront category listing order — WSQ (TGS- SKU) courses first, then non-WSQ (C- SKU) courses ALPHABETICALLY by course name, then partner (M-prefix / other) last — in EVERY category. Also covers DISABLING an empty category (no products on the storefront). Use when asked to "sort courses in a category", "WSQ first", "list WSQ courses before non-WSQ", "order the category alphabetically", "fix the course order on a category page", "disable this empty category", "hide the empty category", or after adding/renaming a course that must slot into the right place in its category listing. Delivered as an idempotent migrations/NNN-*.sql that renumbers catalog_category_product.position AND mirrors it into catalog_category_product_index. Partner-safe (no SKU list; prefix convention holds on every site).

Control the Infortis UltraMegamenu dropdown structure on the storefront — which category levels render as MEGA multi-column panels vs CLASSIC vertical lists, via the umm_dd_type category attribute. Use when asked to "make the menu classical", "convert the mega menu", "nested dropdown should be a plain list", "child categories are missing from the menu", "the menu column is empty", "fix the mega menu", or when a category flyout renders as a grid with empty columns. Covers the level map, the level-3 trap that hides all children, the EAV+flat dual write, and the reindex/flush needed for the menu to re-render.

Review OpenMage 1.x / Magento 1 LTS code in this LMS repo. Use when reviewing a PR, before committing custom-module changes, when asked "is this Magento-correct?", or proactively after writing PHP/XML/phtml in app/code/local/MMD/* or app/design/*. Covers OpenMage 1.x conventions (not Magento 2 — DI XML, service contracts, declare(strict_types) do NOT apply here). Enforces local-codepool overrides, ACL invariants, and migration patterns specific to this repo.

Ensure every SG course (WSQ TGS- and non-WSQ C-) shows at least 5 "Recommended Courses" on its product page, topping up any shortfall with related WSQ courses. Use when the user says "recommended courses", "related courses", "upsell", "make sure courses have 5 recommendations", "the recommended courses section is empty/short", "add related courses", or after bulk-importing/enabling courses that may lack upsells. SG production only (partner sites are a no-op).

Design and continuously improve the SG agentic-flyer newsletter (the MailerLite course flyer). Use when writing/curating a course's flyer pitch, adding a per-course pitch or accent/logo, changing the flyer copy or layout, or working the open-rate/click-rate improvement loop (pre-design + post-blast hooks, learnings log). Covers the HARD RULES, the per-course pitch registry, colour/logo variation, and the data-driven optimisation process. SG-only; the render/flow code is MMD_Marketing.

Repurpose an SG non-WSQ (C-prefix) course into the "AI Vibe Coding Series" and manage that series — rename to "AI Vibe Coding for/with <topic>", rewrite overview + 4 topics (2 per day), set 2 days / 15h / $700, regenerate the branded cover, add the red "AI Vibe Coding Series" badge, and point the Funding block at the matching WSQ/IBF course. Also covers disabling retired courses. Use when asked to "replace this course with AI Vibe Coding for X", "add to the AI vibe coding series", "add the vibe coding badge", "make it 2 days $700 4 topics", "change the funding link", or "disable this course". SG production only, delivered as idempotent migrations/NNN-*.sql.

Design system for the OpenMage admin panel — branding, color tokens, buttons, grids, toolbars, badges. Use when styling or reviewing any adminhtml UI (dark theme, custom modules, RoleManager, dashboards, grids), when a button/toolbar/badge "looks off" or inconsistent, when adding a new admin page, or on requests like "make the admin look more professional", "modern button design", "consistent backend design", "fix the dark theme". Keeps every admin screen visually consistent with the existing token system.

Performance tuning playbook for the LMS — caching (Redis/Magento cache types/FPC/OPcache), page speed, and MySQL 5.7 memory/query optimization. Use when asked to "speed up the site", "tune mysql", "optimize caching", "reduce memory", "site is slow", or for a periodic performance review. Orchestrates the caching-speed-optimizer and mysql-memory-optimizer agents, then applies ONLY approved quick wins with full verification.

Daily security monitoring runbook for the Tertiary Courses LMS (runs scheduled at 7am, or on demand via /security-monitor). Checks production HTTP security posture across all 6 country domains, exposed-file probes, SSL expiry, admin login surface, suspicious DB signals, and diffs the repo for newly introduced risky patterns. Writes a dated report to var/security-reports/ and raises an admin notification on CRITICAL findings. Use when asked to "run the security monitor", "daily security check", "morning security sweep", or by the scheduled job.

Run the "anything broken?" sweep for the LMS — localhost Docker stack and/or production HTTP — and get a PASS/FAIL table. Use when asked to "check site health", "is anything broken", "smoke test", "verify localhost before push", after container restarts, after theme/CSS changes, or as the mandatory verification gate before the admin decides to push. Delegates to the site-health-checker agent.

Audit SEO for the Tertiary Courses LMS — multi-country (SG/MY/GH/NG/BT/IN) Magento 1 storefronts with course catalog. Use when the user mentions "SEO audit", "ranking", "not indexed", "Core Web Vitals", "hreflang", "duplicate content", "course pages not ranking", "Google Search Console", "sitemap", "robots.txt", "meta titles", or any organic-search diagnostic. Tailored to this site's stack (OpenMage 1.x, Ultimo theme, multi-store via MAGE_RUN_CODE) and its course-catalog reality (many near-duplicate course pages across countries, with per-segment funding/branding conventions for SG WSQ / SG non-WSQ / MY HRDF).

Wire a new country domain (e.g. tertiarycourses.com.<cc>) to its Magento store view. Use when adding a new market storefront, fixing a country domain that redirects to the default site, or normalizing an existing store's code/base_url to match the SG/MY/GH/NG/BT/IN pattern. Triggers on phrases like "add Malaysia store", "wire .com.<tld> to store", ".com.<x> redirecting to ai-mms", "country domain not showing", "set up new country", "configure new store".

Build a new custom module for this OpenMage 1.x LMS, in the MMD vendor namespace under app/code/local/MMD/. Use when the user asks to create a new admin feature, scaffold a module, add a custom controller/model/block, wire an event observer, or add a class rewrite. Tailored to this repo's conventions (no Setup/Install scripts — use migrations/NNN-*.sql; MMD_ prefix; existing modules like RoleManager, Courses, BankPayment as reference patterns).

Plan lead magnets that capture emails and turn into course bookings for the Tertiary Courses LMS. Use when the user mentions "lead magnet", "free download", "PDF brochure", "course syllabus", "free trial class", "newsletter signup", "email capture", "downloadable", "subsidy eligibility checker", "SkillsFuture credit", "HRDC claim", "ebook", or any conversion-funnel content. Tailored to a B2B/B2C training-provider context with country-specific subsidy hooks (SG SkillsFuture, MY HRDC) and Magento 1's existing newsletter + customer infrastructure.

Build or modify the customer-facing storefront for this OpenMage 1.x LMS — Infortis Ultimo theme. Use when the user mentions "frontend", "storefront", "Ultimo", "homepage", "category page", "product page", "course page", "checkout", "header", "footer", "responsive", "mobile", "category navigation", or any customer-facing UI. Covers layout XML, phtml templates, Prototype.js/jQuery patterns (NOT RequireJS/KnockoutJS — those are Magento 2), and LESS/CSS overrides. For admin/backend UI, use the backend-design skill instead.

Use when building or reviewing UI components for accessibility (a11y). Covers WCAG 2.1 compliance, semantic HTML, keyboard navigation, ARIA attributes, color contrast, focus management, and screen reader testing. Use when creating forms, modals, dropdowns, navigation, or any user-facing HTML.

Plan and review MySQL/InnoDB schema, indexing, query tuning, transactions, and operations. Use when creating or modifying MySQL tables, indexes, or queries; diagnosing slow/locking behavior; planning migrations; or troubleshooting replication and connection issues. Load when using a MySQL database.