← ClaudeAtlas

taste-distillerlisted

This skill should be used when the user wants to understand why a product, interface, writing style, or codebase feels unusually good, or to extract the hidden governing rules behind a reference. Responds to "I like this but I can't explain why", "what makes this work", "extract the design principles", "distill the taste", "what rules is this obeying", or any request to learn from a reference without copying it.
pyros-projects/limitless · ★ 9 · AI & Automation · score 75
Install: claude install-skill pyros-projects/limitless
# Taste Distiller ## Overview This skill extracts the hidden governing rules behind something that feels unusually good. It is not about copying surface features. It is about finding the deeper constitution: pacing, density, tone, restraint, naming, interaction cadence, and the small repeated choices that create the feeling. ## When to Use Use this when: - the user says "I like this, but I can't explain why" - a reference feels promising but still fuzzy - the team needs stronger language for taste and direction - someone wants to learn from a reference without making a cheap clone Do not use this for generic design critique. This skill is for extracting the rules beneath the style. ## What to Produce Distill the reference into: - governing rules - recurring patterns - what it consistently avoids - how tone, spacing, density, or interaction create the effect - a short "constitution of taste" summary When useful, separate: - direct observation - inference - likely consequences if these rules are broken ## Working Loop 1. Gather the reference carefully. Look at a product, interface, writing sample, or codebase with enough surface area to reveal patterns. 2. Ignore first-order imitation. Do not start with colors, animations, or other obvious artifacts. Instead, inspect concrete dimensions such as: - information density - pacing between actions or beats - what gets prominent placement versus what stays hidden - how errors, empty states, and uncerta