version-archaeology
Version Archaeology
The decisions that survive redesigns are the load-bearing walls.
How to use
/version-archaeologyApply evolutionary analysis to a product's design history.
Constraints
Analysis Method
- MUST compare at least 3 versions of the same product over time
- MUST document for each version: what changed, what stayed, what was tried and reverted
- MUST identify the persistent decisions (things that survived multiple redesigns)
- SHOULD note the ratio of cosmetic changes to structural changes
What Persistence Means
- Elements that survive 3+ redesigns are core taste decisions
- Elements that change every redesign are cosmetic/trend-following
More from dragoon0x/taste-skills
visual-audit
The 10-second design audit. Look at any design and name what's working and what's not within seconds. Trains rapid pattern recognition for hierarchy, spacing, type, and color. Use when evaluating designs quickly, giving first-impression feedback, or building perception speed.
21daily-routines
15-minute daily taste exercises. Monday through Friday. Compound effect over time. Use when building personal practice habits, training a team's design eye, or adding structure to professional development.
15taste-as-strategy
Use taste as a competitive moat and business advantage. In the AI and vibe-coding era, execution is commoditized. Taste is the defensible edge. Use when advising founders on product differentiation, building product culture, evaluating why some products win despite fewer features, or understanding taste as a strategic asset.
15teaching-taste
Help other designers develop judgment without imposing your style. Use when mentoring designers, running design education, or building team-wide quality standards.
15motion-design
Animation as communication. Feedback, orientation, emphasis, delight. If motion doesn't serve one of these four purposes, it shouldn't exist. Use when evaluating animation quality, designing transitions, or deciding whether motion adds or subtracts.
15tradeoff-assessment
Name what was prioritized, what was sacrificed, and whether the tradeoff was right. Every design decision trades something. Use when evaluating design decisions, defending choices, or helping teams understand what they're giving up.
14