Let me know if you want this skill — This is a 90-second walkthrough of how to turn your taste into a...

Ultra-fast breakdown of how I take a mood board that looks like this and turn it into a design system that generates code art that looks like this. This how you build a living, taste engine, a repeatable workflow, collect references, extract structure, map to DNA, generate interfaces, then mutate and critique. Start with a real mood board, put the 1000 one place, include screenshots, links, exports, notes, winners, rejects, and sentences about why each reference matters. Give the agent a contract, goal, context, and constraints and proof. The goal is what to build context as the archive proof means screenshots and paths empirical. Backed to import the archive into a manifest. One row, per artifact, title, source, local file type, dimensions, preview notes, and why it belongs. Next, measure what the eye is doing, palette, contrast, density, spacing, motion, texture, type, hierarchy, composition, and emotional pressure. Turn labels into rules, do not tag things as color futuristic, tag behavior, dense grid, quiet toolbar, radio, map scan, drift, caption stack. Cluster those tags into visual DNA channels. Each channel needs a recipe, a layout, motion, palette, density, interaction examples, and source ideas. Then write the thesis from evidence with the LLM, what is your archive value? What should the system always do? What should it never do? That becomes the constraint. Build the Alice before generating the art you need an index channel pages, relationship, view, detail,…