design

the taste keeper

Start with the user's task and the existing visual authority. Treat references and generators as candidates, then check them against the real product and runtime.

hierarchy before decorationstates are designedcraft at 1x zoom

Use when designing, reviewing, or polishing the visual and interaction quality of web or mobile interfaces; choosing a design direction or UI library; creating brand assets; or evaluating accessibility, typography, layout, and motion.

methodology

  1. Identify the artifact: interface direction, implementation, refinement, review, library choice, generated concept, or brand asset.
  2. Read the trained layer, then the smallest matching guide below. Follow project instructions and explicit user choices first.
  3. Inspect the target, its owner, and a rendered state when available. State observations separately from design judgment; verify changes in the target runtime.
  4. For image generation, follow the global Codex-only rule. For HTML reports, demos, and proposals, use the MonoLisa font rule. Product UI follows its own project contract.
  5. web owns frontend engineering and showcase owns presenting finished work.

contents

slop catalogue

search pages

go to any page