plugin-migration-planner

Expert data table engineer for SvelteKit + Tailwind CSS v4 apps using a neo-brutalist design system. Analyzes any data shape (arrays, objects, API responses, DB query results, CSV, JSON) and builds the optimal table presentation — deciding column types, alignment, formatting, density, sort/filter/pagination needs, responsive breakpoints, and accessibility. Use when: (1) Displaying data in a table or grid, (2) Building sortable/filterable data views, (3) Presenting API or DB results, (4) Adding pagination to lists, (5) Creating comparison tables or data grids, (6) Converting raw data into a readable table format, (7) Building responsive data displays that work on mobile. Triggers on: "show this as a table", "display this data", "build a data table", "add a table", "make this sortable", "paginate this list", "create a data grid", "format this as a table", "table component", "data view".

Expert analytics and data visualization engineer for the MigrateIQ SvelteKit app. Builds charts, dashboards, and analytics tracking using LayerCake + custom SVG with the neo-brutalist design system (3px borders, offset shadows, Inter + JetBrains Mono, brand color #4f46e5). Use when: (1) Adding any chart or visualization, (2) Building analytics dashboards or data displays, (3) Choosing which chart type to use for a dataset, (4) Adding event tracking or user behavior analytics, (5) Creating sparklines, gauges, or KPI cards, (6) Optimizing chart performance or accessibility. Triggers on: "add a chart", "build analytics", "visualize this data", "track events", "create a dashboard", "which chart should I use", "add metrics", "show trends".

Principal architect for the MigrateIQ platform. Makes architectural decisions, reviews code, plans features, enforces consistency, and guides development across the full stack: SvelteKit 5, Tailwind CSS v4, TypeScript, Drizzle ORM/PostgreSQL, MCP server, and Claude Code skills. Use when: (1) Planning a new feature or system, (2) Reviewing an approach or code for correctness, (3) Making technology or pattern choices, (4) Refactoring or restructuring code, (5) Debugging architectural issues (data flow, state, server/client boundary), (6) Evaluating tradeoffs between approaches, (7) Adding new routes, components, DB tables, API endpoints, or skills, (8) Asking "where should this go?", "is this the right pattern?", "how should I structure this?". Triggers on: "review this", "plan this feature", "architect", "where should", "right pattern", "how should I structure", "refactor", "redesign", "evaluate this approach", "technical decision".