mcpField
C
cross-domain-seeing

cross-domain-seeing

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

About cross-domain-seeing

A design skill for extracting transferable principles from non-digital fields and applying them to screen design. It focuses on analyzing the underlying idea rather than copying a domain’s visual style.

Key features

  1. 01Observe non-digital domains
  2. 02Identify underlying design principles
  3. 03Translate principles for screens
  4. 04Draw from architecture, fashion, film, industry, and music

Use cases

  1. 01Finding screen-design ideas beyond apps
  2. 02Turning spatial choices into layout principles
  3. 03Applying rhythm or contrast to interface design

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/dragoon0x/taste-skills --skill cross-domain-seeing

After installing, type/cross-domain-seeingin Claude Code to confirm it loaded.

Details

From the project README

Cross-Domain Seeing

Learn design principles from everything that isn't a screen.

How to use

  • /cross-domain-seeing Apply cross-domain observation principles to this conversation.
  • /cross-domain-seeing <domain> Extract design principles from a specific non-digital domain.

Constraints

Transferable Principles
  • MUST identify the underlying principle, not the surface aesthetic
  • MUST translate observations into screen-applicable language
  • "The museum uses a single material palette with one contrast accent" becomes "restrained palette with one accent color"
  • "The restaurant spaces tables far apart" becomes "generous whitespace signals premium positioning"
  • NEVER copy an aesthetic literally. Extract the principle and reapply it.
Domains to Draw From
  • Architecture: spatial hierarchy, material relationships, light direction, density vs. openness
  • Fashion: proportion, rhythm, texture contrast, restraint, the role of fit
  • Film: pacing, focal point, color grading, tension, the cut as a design decision
  • Industrial design: form following function, material honesty, ergonomics as interface
  • Music: rhythm, dynamics, silence as design element, tension and resolution
Anti-Patterns
  • Saying "inspired by Japanese minimalism" without naming the specific principle
  • Collecting cross-domain references without connecting them to design problems
  • Using architectural terms as jargon rather than genuine analytical tools

Comments

Markdown supported