MIG Hub, an Internal Operations Console for an Artisan Boutique

This project grew out of my internship at Mes Indes Galantes .

Where It Started

Over about two months, I built one standalone tool at a time to solve whatever problem the boutique’s Magento 2 store raised that week: a category tree explorer, a catalogue generator, an SEO audit, a stock inventory sheet, photo and video optimizers (sixteen separate tools in total, each its own scrappy folder, none of them talking to each other).

The Pattern

Every one of those tools was independently re-parsing the same Magento CSV export and re-solving the same quirks (trailing spaces creating phantom duplicate categories, inconsistent category-path prefixes, orphan products invisible to customers). Once that pattern was obvious, the fix was equally obvious: stop rebuilding the same parsing logic sixteen times.

What It Is

MIG Hub is an app-grid launcher, one branded interface where the team reaches every tool as a tile, built on:

• A shared data layer, one normalized model for products and categories, parsed once from the Magento export, sitting behind a DataSource interface designed so a live Magento API integration can drop in later without touching a single module.
• A module registry, every tool is headless logic (callable functions) plus an optional view. Adding a tool is a drop-in, never a refactor.
• A conversational assistant, Claude, with tool-calling mapped directly to each module’s actions, so instead of opening five screens you can just ask “which categories are empty?” or “what should I prioritize today?”

Built with Next.js, TypeScript, and Tauri (for the desktop-only media optimizers), and trilingual across French, English, and Bahasa Indonesia to match the team.

Status

Under active development. The category tree, catalogue generator and viewer, stock inventory, and media optimizers are live; the audit modules and the assistant are still being built out.