Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

fe-design-review

Étoiles10

Forks1

Mis à jour15 juillet 2026 à 10:47

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.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

aturzone

aturzone/MasterClaude

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Concepteurs web et d'interfaces numériquesProfessions informatiques et mathématiques·SOC 15-1255

SKILL.md

readonly

Plus depuis ce dépôt

même dépôt

guardian

aturzone/MasterClaude

Scope & verification discipline for a working session. Triggers when about to claim "done / fixed / passing", when a test is about to be weakened, skipped, commented out or deleted to get a suite green, when a refactor, abstraction or dependency appears that the task never asked for, and on "audit this diff" / "did we actually verify that?". Guidance the model follows — it is not enforcement; nothing here can block a tool call.

2026-07-1610

master-claude

aturzone/MasterClaude

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.

2026-07-1610

compactor

aturzone/MasterClaude

Continuity across long sessions. Snapshots in-progress work before context compaction and restores it after, and nudges auto-compaction toward a natural breakpoint so nothing important is lost mid-task.

2026-07-1610

claude-current

aturzone/MasterClaude

Stay current with Claude Code and Claude itself. Triggers on "what's new", "what can Claude Code do now", "is there a newer/better way", "update master claude", "which model should I use", or before relying on any claim about a Claude Code feature, model, price, or limit. Checks the installed version, the live changelog, and the harness surface MASTER CLAUDE depends on — then reports only the deltas that matter for this project.

2026-07-1610

model-router

aturzone/MasterClaude

How MASTER CLAUDE picks the right model for each agent and task. Triggers on "which model", "pick a model", "model selection", "use haiku/sonnet/opus", "cheaper model", "model per agent", or whenever spawning a subagent/team and choosing its model, or optimizing cost vs. quality on a long run. Gives a role→model heuristic, the "turn count beats token price" rule, the effort dial, and the cost math so the team is both strong where it matters and cheap where it doesn't.

2026-07-1610

subagent-orchestration

aturzone/MasterClaude

How MASTER CLAUDE delegates work to subagents and teams. Triggers on "delegate", "spawn agents", "parallel agents", "fan out", "run these in parallel", "subagent", "orchestrate", "build a team for this", or whenever a task splits into independent chunks, needs a fresh-eyes review, or means reading many files. Teaches the orchestrator-worker pattern: pick the right primitive (subagent vs agent-team vs background session), write a complete delegation brief, parallelize only when it pays, scale effort to the task, and verify with an adversarial reviewer. Use to plan and run any multi-agent push.

2026-07-1610

name	fe-design-review
description	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.
allowed-tools	Read, Grep, Glob, Bash

Frontend design review — catch it before users do

An unsentimental design pass over the UI. Output findings as blocker / major / minor, each with where (file or element) + a concrete fix, then a one-line verdict and the single first thing to fix.

Review in priority order

Walk the ui-intel ladder top-down and stop pretending a spacing nit matters while a control is keyboard-unreachable. Severity comes from the band, not from how much it bothers you:

Band	1 a11y	2 touch/interaction	3 perf	4 style coherence	5 layout/responsive	6 type/colour	7 motion	8 forms	9 nav	10 charts
Floor	blocker	blocker	major	major	major	minor	minor	major	major	minor

A band-1 miss is a blocker even if the page is gorgeous. A band-6 nit is a minor even if it offends you.

node <ui-intel>/uikit.mjs --domain ux-rules "<topic>"     # the full rule + its anti-pattern
node <ui-intel>/uikit.mjs --contrast "#64748B" "#F1F5F9"  # settle a contrast argument with a number

The checklist

Hierarchy — is the one primary action obvious? does the eye land where it should? is there a clear h1?
Spacing & alignment — a consistent rhythm from the scale? aligned to a grid? no cramped or random gaps?
Type — readable body (≥ 15px)? sane line length (≤ ~75ch)? a clear scale? not too many fonts/weights?
Color & contrast — one restrained accent? text ≥ 4.5:1, UI ≥ 3:1 (WCAG AA)? meaning never by color alone?
A11y — semantic HTML? keyboard-operable with visible focus? labels / alt / names present? (spot-check the DOM.)
States — hover · focus · active · disabled · loading · empty · error all handled, not just the default?
Responsive — works 360px → 1440px? tap targets ≥ 44px? no horizontal scroll? do tables reflow?
Consistency — uses the design-system tokens (not one-off colors/spacing)? components reused, not re-styled?
Polish — transitions present and reasonable? respects prefers-reduced-motion? loading isn't a lone spinner?

How to run it

Read the component + styles; if it runs, exercise it (the preview tools or a quick build) and inspect the rendered result + DOM for the contrast / a11y / state items rather than guessing. Tie every finding to a checklist item — no hand-waving — and lead with the highest-severity, highest-impact fix.

Check against the project's own system, not your taste. If .mc/design/MASTER.md exists, it — plus any pages/<page>.md override — is the baseline. A deviation from MASTER is a finding; disagreeing with MASTER is a conversation to have with the human, not a finding to file.

The frontend sibling of cap-self-review. Uses ui-intel's ladder for severity and fe-design-system / .mc/design/MASTER.md as the consistency baseline; hands deep a11y work to fe-a11y and slowness to fe-perf. Credits: WCAG, the WAI-ARIA APG, shadcn/Radix accessibility patterns.