The taste-file standards
Other people have already argued about what belongs in a file like this. Read one before you write yours, and steal the vocabulary.
- TASTES.md, opens in a new tab The standard the book borrows its structure from: hard rejections, thresholds, reference anchors, and the tensions you refuse to resolve.
- PitayaK/taste.md, opens in a new tab A personal taste file the agent reads at the start of a session and updates as it watches you work. The version of the idea that maintains itself.
- Taste Skill, opens in a new tab An installable skill aimed squarely at the flat default look. Worth it if you would rather correct a maintained baseline than start from a blank page.
- The Awesome DESIGN.md collection, opens in a new tab Fifty-eight real products, from Linear to Stripe to Airbnb, with their visual systems written as rules an agent can read. The mood board done right.
- Installing skill files in AI coding agents, opens in a new tab The plumbing: where the file has to sit for each agent to find it, and why an aspirational rule has to become a measurable one. The 4px example in chapter 4 is theirs.
- Ten AI skills for real design taste, opens in a new tab A survey of what people are actually installing. Useful mostly as a map of which problems the community has decided are worth a skill.
Add unlimited notes to any activity
Comments & Discussion
Add a Comment
Recent Comments (3)
This workshop was incredibly effective for our remote team! We adapted it slightly for a virtual setting and it worked wonderfully. The key was breaking into smaller breakout rooms.
Great resource! One tip: prepare all materials the day before to avoid any last-minute rushes.
Used this for our quarterly planning session. The structured approach really helped us stay on track!