mcpField
T
taste-vs-trends

taste-vs-trends

github.com/dragoon0xDesign & UI680 installsUpdated 35w ago
Repository

About taste-vs-trends

taste-vs-trends is a design skill for judging whether a decision rests on lasting principles or short-lived trends. It uses tests of longevity, rationale, and transferability, and encourages alternatives grounded in user needs without dismissing trends outright.

Key features

  1. 01Test design decisions over time
  2. 02Examine the reasoning behind choices
  3. 03Check whether principles transfer
  4. 04Distinguish trends from principles
  5. 05Suggest user-focused alternatives

Use cases

  1. 01Review a proposed visual trend
  2. 02Evaluate whether a choice serves users
  3. 03Find alternatives to trend-led decisions
  4. 04Assess whether a design principle generalizes

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/dragoon0x/taste-skills --skill taste-vs-trends

After installing, type/taste-vs-trendsin Claude Code to confirm it loaded.

Details

From the project README

Taste vs. Trends

Separate decisions that last from decisions that expire.

How to use

  • /taste-vs-trends Apply taste-vs-trend analysis to any design decision in this conversation.

Constraints

The Three Tests
  • Time test: Will this decision still make sense in 2 years? If not, it's a trend.
  • Reasoning test: Does the "why" bottom out at "everyone's doing it" (trend) or "it serves the user this way" (taste)?
  • Transfer test: Does the principle work across domains, or only in this medium? Principles transfer. Trends don't.
Evaluation Rules
  • MUST identify whether a design decision is trend-driven or principle-driven
  • MUST challenge "modern" as a design goal. Ask: modern for whom? Modern compared to what?
  • SHOULD suggest principle-based alternatives when trend-following is identified
  • NEVER dismiss trends entirely. They carry information about user expectations. Use them as inputs, not instructions.
Questions to Ask
  • Does this trend solve a real problem for this specific context?
  • What would I choose if nobody would ever see my portfolio post?
  • Am I choosing this because it's right or because it's safe?
Anti-Patterns
  • Calling everything trendy to seem sophisticated (some trends reflect genuine improvements)
  • Rejecting contemporary approaches just to be contrarian
  • Equating timelessness with conservatism (bold choices can age well too)

Comments

Markdown supported