mojovoice

UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 9 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient. Integrations: shadcn/ui MCP for component search and examples.

Use when the user wants to quickly add a single task to the plan without full planning. Triggers on "add a task", "quick add", "append a task", "add this to the plan", or /maximus-add. For backlog items ("queue this for later", "add to the queue"), use the queue skill instead.

Use when a Maximus Loop batch is complete and you need to wrap up the worktree — archive, clean, then choose merge/PR/keep/discard. Triggers on "finish the worktree", "wrap up the batch", "merge the worktree", "close out this batch", "done with the batch", or /maximus-finish.

Use when the user asks to "set up maximus", "configure maximus", "initialize maximus", "create maximus config", "scaffold maximus", "bootstrap maximus", or "maximus init".

Use when the user wants to create, update, extend, or replace a Maximus Loop task plan (plan.json). Triggers on "create a plan", "plan this feature", "generate tasks", "break this down into tasks", "add tasks for", "scope this work", "plan the next phase", "update the plan", or /maximus-plan.

Use when the user wants to view, add to, promote from, or manage the .maximus/queue.md backlog. Triggers on "show the queue", "add to the queue", "queue this for later", "what's in the queue", "promote from queue", "archive the queue", or /maximus-queue.

Use when the user wants to review Maximus Loop results, analyze run performance, or check execution status. Triggers on "review the run", "analyze maximus results", "check status", "how is the run going", "show me the summary", "what's the progress", or when the user wants post-execution analysis with cost/performance insights.

Use when the user asks to "validate maximus", "check maximus config", "verify maximus setup", "is my maximus config correct", "is my project ready to run", "lint my config", or before running the engine.