Topic

Design Systems

All digests tagged Design Systems

Training Taste — Thais Castello Branco, Taste Labs thumbnail

· 15:06

Training Taste — Thais Castello Branco, Taste Labs

Taste Labs addresses the problem of 'AI slop'—the homogenization and lack of context in AI-generated content—by proposing a shift in focus from model training to the application layer (inference time). The core methodology involves quantifying subjective domains like design by training 'probes' (small classifiers) on massive datasets (over 2 million websites). This approach allows for the measurement and prediction of slop, which is superior to traditional LLM-as-a-judge methods. Solutions include the 'Brand API' for structuring brand guidelines into machine-readable components and the 'Creativity API' for intentionally generating out-of-distribution content while respecting domain rules.

Key takeaways

  1. Defining Slop and Greatness 4:13

    Slop is defined by three characteristics: repetition, lack of fit (contextual incoherence), and low intent. While defining 'greatness' is subjective, defining slop is easier, as it represents a general sense of soullessness and convergence.

  2. Measuring Slop Quantitatively 5:46

    Taste Labs analyzed over 2 million websites from the past decade to understand design trends. They developed 'probes'—small classifiers—that extract objective features (e.g., contrast, alignment, palette) to predict slop, achieving higher accuracy than LLM-as-a-judge methods.

  3. Focusing on Inference Time 5:46

    The most critical intervention point is the application layer (inference time), where user context and intent are exchanged. Improving quality here is considered equally, if not more, important than improving the base model itself.

Watch on YouTube Full article

Design at the Speed of Adjectives — Paul Bakaus, Renaissance Geek, Inc. thumbnail

· 15:59

Design at the Speed of Adjectives — Paul Bakaus, Renaissance Geek, Inc.

The talk introduces 'Impeccable,' a design skill designed to enhance coding harnesses (like Copilot and Claude Code) by providing a vocabulary to steer AI-generated design. The core thesis is that good design cannot be 'oneshot' or fully automated because it is context-rich, iterative, and requires human decision-making. Instead of automating the process, Impeccable allows users to inject specific adjectives and verbs (e.g., 'bolder,' 'quieter,' 'distill,' 'harden') to guide the AI toward specific design goals, thereby improving the quality of the human-AI collaboration.

Key takeaways

  1. Design is not a one-shot process 9:58

    Good design must be context-rich and iterative. The speaker argues that fully automating design is currently impossible, as human judgment is required to define the emotional territory and audience.

  2. Impeccable facilitates steering, not abdication 13:50

    The tool's purpose is to give users the necessary control to steer the agent using specific design vocabulary. The speaker explicitly rejects the idea of an automatic mode, stating that the point is guiding the process, not letting the AI do all the work.

  3. The traditional design handoff is collapsing 4:16

    The traditional 'waterfall' process (PM $ ightarrow$ Design $ ightarrow$ Engineer) is rapidly breaking down, leading to a blurring of roles where engineers and designers must increasingly work in shared, fluid processes.

Watch on YouTube Full article