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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
설치 방법 보기설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
Define a coherent design POV that can explain the major visual choices without naming trendy libraries.
Create three structurally different routes. Each route must specify:
Do not submit three palette variants of the same layout.
Plan the page as tension and release. Alternate emphasis intentionally: peak → pause → dense evidence → quiet bridge → signature moment → resolution. Avoid a page where every section has equal visual volume.
Choose one memorable idea that could be described 24 hours later. It must be connected to the product/brand, not novelty for novelty's sake.
Write what the site must not feel like. Examples: “not a generic SaaS dashboard”, “not card-heavy”, “not luxury-through-black-and-gold cliché”. Use this to reject plausible but wrong choices.
아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use as an independent design-review pass after rendering a website; evaluates macro, meso, micro craft, applies the Design Quality rubric, identifies root causes, and prioritizes changes without defending the implementation intent.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.