Use when a web project needs business goals, audience, information architecture, conversion priorities, content hierarchy, constraints, or design CTQs clarified before visual design begins.
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Capture only information that changes the design:
Translate adjectives into observable requirements.
Do not stall on low-risk gaps. Infer reasonable defaults, label them as assumptions, and continue. Ask only when a missing decision would materially change business logic, brand, legal requirements or architecture.
Produce a concise design brief with: Goal, Audience, Primary Job, Primary Action, Content Priority, Brand, Anti-Direction, Constraints, CTQs.
When imagery, logos, footage, 3D models, fonts, or external references affect the direction, read references/asset-protocol.md and record ownership, rights, fidelity, fallback, and delivery status before treating an asset as available.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Use for release-level accessibility and performance review, including WCAG 2.2 AA, keyboard/focus, target size, reduced motion, semantic controls, Core Web Vitals, images/fonts/JavaScript, and animation or 3D performance budgets.
The English summary is being prepared. Showing the original description.
Use to audit a generated or heavily templated interface for generic AI aesthetics, unjustified trend patterns, component-registry residue, vague copy, repetitive motion, novelty theater, or visual decisions that lack brand/UX rationale.
The English summary is being prepared. Showing the original description.
Use when a website needs a strong visual point of view, distinct concept routes, composition, typography, color/materiality, imagery direction, spatial rhythm, or a memorable signature idea.
The English summary is being prepared. Showing the original description.
Use when deciding whether to implement UI from native HTML/CSS, accessible primitives, shadcn-style source components, or visual component registries such as 21st.dev, Aceternity, React Bits, Motion Primitives, Magic UI, or Animate UI.
The English summary is being prepared. Showing the original description.
Use after substantial web projects or repeated design defects to convert evidence into reusable skill improvements through root-cause analysis, regression scenarios, and controlled proposals without silently changing the core OS.
The English summary is being prepared. Showing the original description.
Use when the design concept calls for Three.js or React Three Fiber 3D, WebGL/WebGPU, Rive, Spline, Theatre.js, SVG, canvas, shaders, particle systems, or other immersive creative-web techniques.
The English summary is being prepared. Showing the original description.