alfredang

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).

End-to-end submission of a native Android app (AAB) to the Google Play Console for review and closed testing, driven through the Play Console web UI with Playwright MCP. Covers building/signing the release bundle, creating the app, store listing, ALL App content declarations (incl. Data safety for location), Store settings, creating a closed-testing track, adding the "All Testers" email list, selecting countries, uploading the AAB, and submitting for review. Includes the Misleading Claims (government-data source link) policy and a field-tested rejection-prevention checklist. Use when asked to "submit/publish an Android app", "push to Play Store", "closed test", or to fix a Play policy rejection.

Set up CI/CD that auto-builds, signs, and uploads a native Android app (AAB) to the Google Play Console on every push to main (GitHub Actions on ubuntu). The build is signed with your release keystore (from GitHub secrets) and uploaded to a chosen track (internal / closed / production) via a Play Developer API service account, with release notes pulled from distribution/whatsnew (or CHANGELOG.md). Handles auto-incrementing versionCode, the "first upload must be manual" rule, secrets, and the Play API gotchas. Use when a user wants automated Play Store releases / "auto submit to Play on push" / a release pipeline for an Android Gradle app.

Add a Material 3 / Jetpack Compose bottom navigation with Feedback and About tabs to a native Android app (matching the Tertiary Infotech house style). The Feedback tab has a Title field, a Message field, and a "Send via WhatsApp" button that opens wa.me/6588666375 with the composed text. The About tab shows the app name + description, a Developer card ("Tertiary Infotech Academy Pte. Ltd." + tertiaryinfotech.com link), an optional Data-source card with a link, and a Version row (BuildConfig). Use when asked to add About/Feedback tabs, a bottom nav, a WhatsApp feedback form, or an in-app source attribution/About screen.

Single-source build pipeline for the WSQ "Application Integration with Docker and Kubernetes" (TGS-2021010366) courseware. One canonical content module (labs_data.py) drives ALL artifacts so they stay 100% aligned — the labs/ folder, the all-white slide deck (PPT), the Lesson Plan (LP), the Learner Guide (LG) and its Markdown mirror. Use to regenerate any courseware after editing course content.

Fill the JD / "Job responsibilities" column (Column F, labelled "aligned with JD") in a Lithan CCP TSC Scoping Matrix workbook. For each technical skill & competency (TSC) row, write a one-line job responsibility aligned with that skill's Objective and the job role, matching the style of an already-filled reference sheet. Use when the user asks to fill, update, write, or summarise the JD / job responsibilities column on the TSC (Technical Skills & Competencies) Scoping Matrix for a Lithan CCP — files named like "CCP TSC Scoping Matrix LOO6*.xlsx" under the Tertiary Infotech/CCP person folders. Each workbook sheet is one job role (e.g. "2.4 AI ML Engineer", "3.3 Software Eng Manager").

Set up CI/CD that auto-builds, signs, uploads, and submits a native iOS/iPadOS app to App Store Connect on every push to main (GitHub Actions on macOS). Use when a user wants automated App Store releases / "auto submit a build on push" / a release pipeline for an Xcode app. Reuses the App Store Connect API key as the upload+submit token; handles signing assets as GitHub secrets, the iOS-26-SDK requirement, and the review-submission race.

Master SwiftUI and Apple Human Interface Guidelines patterns for building native iOS apps. Use when designing iOS interfaces, implementing SwiftUI UI, adding navigation (TabView / NavigationStack), theming, or following Apple's HIG. Includes the Tertiary Infotech Academy house-style bottom-tab nav with Feedback + About tabs.

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.

Health, liveness & performance check of the production LMS-TMS site, with known auto-fixes. Use when asked to check if the site/prod is up, healthy, slow, or "loading forever", or to verify after a deploy/firewall change.

Security posture scan of the production LMS-TMS (TLS, headers, exposed DB ports, firewall integrity, secret leaks). Use when asked to security-check/harden the site or verify the hardening is still in place.

Comprehensive guide for Manim Community - Python framework for creating mathematical animations and educational videos with programmatic control

Operational playbook for THIS project — the lead-qualification n8n workflow + Supabase pgvector + Telegram bot + static web uploader. Use this skill any time the user asks to deploy, set up, activate, debug, or fix anything in the lead-generation pipeline. Knows the specific failure modes (empty tableName silently 500-ing the webhook, Default Data Loader needing expressionData mode, the Code node dropping empty Telegram replies, OpenAI 429s, Supabase service_role vs publishable key confusion). Skip this skill for generic n8n / Supabase / OpenAI questions — only use it for THIS workflow.

Generate a professional GitHub README.md file following open standards with tech badges, architecture diagrams, setup instructions, and acknowledgements.