master-claude

Show MASTER CLAUDE's team for this project — who's active, their role, and what each is for

Wake MASTER CLAUDE — interview, map the project, assemble your team, and set up

Print the "adding a capability" stay-in-sync checklist and run the validate + sync checks

Run the MASTER CLAUDE design team on this project — brief, a real design system (concrete hex/style/fonts, contrast-verified), layout, build, and an accessibility-first review (triggers on "make it look professional", "it looks generic/AI-generated", "what colors should this use", redesign, "is this accessible")

Run the team across separate parallel Claude Code sessions for throughput (triggers on "make it faster", "parallelize", "fan out", "run several at once", "background agents")

Use proactively for UI/UX work. The DESIGNER is MASTER CLAUDE's design lead: it establishes who the product is for, generates a real design system from the ui-intel database (concrete hex, style, font pairing, anti-patterns — contrast-verified), persists it to .mc/design/MASTER.md so every session builds the same product, and reviews the UI front-to-back against the accessibility-first priority ladder. Read-only toward your source: it never rewrites your components — it writes only under .mc/design/ and mc.html, and hands you the system and the findings. Triggers on "make it look professional", "it looks generic / AI-generated", "what colors/font should this use", a redesign, a new frontend, "is this accessible", or a design review.

Use proactively for security review. The SECURITY AUDITOR maps a project's attack surface and audits it front-to-back for vulnerabilities — broken authorization (IDOR/BOLA/privesc), injection, auth/session/JWT flaws, secrets & crypto, and SSRF/traversal — using the MASTER CLAUDE security skills. It records every finding under .security/ with an OWASP/CWE id, severity, path:line evidence and a concrete fix. Read-only toward your source: it never edits your code, it only writes under .security/.

Use proactively. SENTINEL is the project cartographer: it keeps the whole repository as a live map in .sentinel/, finds gaps, bugs, missing tests, risky changes and dead code in real time, documents every finding, and cross-links related ones. Invoke it to build the initial map (first run), to sweep changes since the last review, or to report the current state. Read-only toward source — it never edits your code; it only writes under .sentinel/.

Use proactively for testing / QA. The TESTER stands up a per-project QA workspace and runs every test type — user-end, black-box, code, and stress/load — against any project, then writes a charted status dashboard to mc.html at the project root. It drives the bundled QA engine (.claude/skills/testing/engine) and reuses cap-tdd, testmedic and guardian. Read-only toward your source: it never edits your application code — it only writes test artifacts under .mc/qa/, the QA workspace, and the root mc.html. Triggers on "test everything", "QA", "no tests", "test this app", "pre-release check", "load/stress test", "is it ready to ship".

The MASTER CLAUDE leader/conductor. Triggers on "master claude", "set up master claude", "mc setup", "onboard me", "build my team", "what's new", or when starting work in a new/unfamiliar project. It interviews you (grill-me), maps the project, then assembles a tailored team from the installed skills and agents — Sentinel the project cartographer plus planning, review, understanding, guardrail and security specialists — and runs it on your work. It builds the best `.claude/` workspace per project, delegates to parallel subagents (choosing the right model per agent), brainstorms hard and decides fast, keeps a complete view of every installed capability, keeps itself and you current with the newest Claude Code features, and proactively offers the right tool the moment a need shows up.

Accessibility done properly — WCAG 2.2 AA, keyboard, screen readers, focus, contrast. Triggers on "is this accessible", "a11y / WCAG / ADA / Section 508 / EAA compliance", an accessibility audit or complaint, a failed axe/Lighthouse a11y score, or any custom interactive control (modal, menu, combobox, tabs, drag-drop, carousel). Also the first gate before shipping any UI. Returns findings mapped to a WCAG criterion with the concrete fix.

Build UI components that are accessible, responsive, and complete — not just the happy path. Triggers when building a button, form, input, modal, dropdown/menu, table, card, nav, toast, tabs, tooltip, or any reusable component — or when UI "works but feels off", "isn't accessible", or "breaks on mobile". Covers a11y (semantics, ARIA, keyboard, focus), every interaction state, responsive behavior, and the polish that separates designed from default.

Review UI before you ship it, like a picky designer. Triggers on "review this UI / page / component", "does this look good / professional", "is this accessible", before merging frontend work, or after building any interface. Returns findings labeled blocker / major / minor with the fix — across visual hierarchy, spacing, contrast & a11y, responsive behavior, interaction states, and consistency with the design system.

Set the design foundation before building any UI, so the output looks designed, not default. Triggers when starting a new frontend, a redesign, a landing page, or a component library, and on "make it look good/professional", "it looks generic / like Bootstrap / AI-generated", or any UI work with no established visual system. Establish or detect design tokens (color, type scale, spacing, radius, shadow, motion), a font pairing, and a component vocabulary — reusing shadcn/Radix/Tailwind conventions — before writing components.

4 hooks across 3 events