Research a career field and create full radar content (cards, sources, metrics). Use when asked to add a new career to radar, research a career field, update radar data, or seed radar content. Covers web research, data validation, DB writes to both local and production.
Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.
Manage hackathon journey phases and activities — create, edit, and organize multi-phase hackathon programs with activities, content, and assessments. Works like PathLab but for hackathon programs.
Edit and improve learning map content in Supabase through natural-language prompts, including deep updates to learning_maps metadata, map_nodes, node_content, node_assessments, and quiz_questions. Use when user asks to revise map copy, replace node instructions, adjust assessments, or edit checklist/quiz structures in MCP.
Generate strict PathLabMapStructure JSON for solo, self-paced, day-based PathLab explorations that end with a Continue/Pause/Quit decision. Use when a user asks to create PathLab map JSON, map drafts, or curriculum maps that must follow exact schema fields, day sequencing, node/edge integrity, and JSON-only output constraints.