/nw-sci-fi-design-patterns
Catalog of UI patterns from games, anime, and films with analysis of why they work -- structural principles extractable to real interfaces
Claude Code
$ npx -y skills add nWave-ai/nWave --skill nw-sci-fi-design-patterns --agent claude-code
Codex
$ npx skills add nWave-ai/nWave --skill nw-sci-fi-design-patterns -a codex -y
Cursor
$ npx skills add nWave-ai/nWave --skill nw-sci-fi-design-patterns -a cursor -y
Gemini CLI
$ npx skills add nWave-ai/nWave --skill nw-sci-fi-design-patterns -a gemini-cli -y
GitHub Copilot
$ npx skills add nWave-ai/nWave --skill nw-sci-fi-design-patterns -a github-copilot -y
OpenCode
$ npx skills add nWave-ai/nWave --skill nw-sci-fi-design-patterns -a opencode -y
Windsurf
$ npx skills add nWave-ai/nWave --skill nw-sci-fi-design-patterns -a windsurf -y
SKILL.md
nw-sci-fi-design-patterns.SKILL.mdname: nw-sci-fi-design-patterns
description: Catalog of UI patterns from games, anime, and films with analysis of why they work -- structural principles extractable to real interfaces
user-invocable: false
disable-model-invocation: true
Sci-Fi Design Patterns
Pattern Categories
1. Diegetic UI (Interface Lives in the World)
**Source**: Dead Space (health bar on spine), Iron Man (JARVIS holographic workspace), Mass Effect (Omni-tool)
**Why it works**: Eliminates the cognitive split between "looking at the interface" and "being in the experience." Users stay immersed. Information is spatially anchored to the object it describes.
**Extractable principles**:
- Status indicators attached to the element they describe (badge on avatar, not separate panel)
- Context menus appear at the point of interaction, not in a fixed sidebar
- Progress indicators are part of the action element (button fills as it processes)
- Health/status of a system component shown ON the component representation
**Key insight**: Dead Space's diegetic UI works because it eliminates the split-attention effect from Cognitive Load Theory — information in the same visual plane as the game world means eyes never dart to screen corners. The trade-off (harder to parse quickly) is intentional for horror, but for productivity tools, make diegetic elements easy to read.
**Deeper examples**: Navigation waypoint (glowing floor line instead of minimap), holographic inventory that exists in real-time (enemies can attack while browsing), stasis energy as wearable semicircular meter.
**Web/App translation**: Inline editing|contextual toolbars|progress-as-button-state|status-as-color-on-node (monitoring dashboards)
2. Holographic Layering (Depth Through Transparency)
**Source**: Iron Man (JARVIS floating panels), Minority Report (gesture layers), Halo (holographic briefings)
**Why it works**: Creates spatial hierarchy without consuming screen real estate. Background layers provide context; foreground layers demand attention. Parallax between layers communicates depth.
**Extractable principles**:
- 3-4 depth layers: background (environmental/ambient) | mid-ground (contextual/secondary) | foreground (primary interaction) | overlay (urgent/modal)
- Each layer has distinct opacity range: background 10-30% | mid-ground 40-60% | foreground 70-90% | overlay 90-100%
- Blur increases with depth (backdrop-filter: blur scales per layer)
- Interactive elements always on foreground or overlay -- never bury clickable things in background layers
**Web/App translation**: Glassmorphism with semantic layers|modal stacking with blur gradients|dashboard panels at different z-depths with transparency
3. Scan-Line / Data Stream Aesthetic
**Source**: Ghost in the Shell (Standalone Complex), Blade Runner 2049, The Matrix
**Why it works**: Communicates "live data" and "processing" without explicit loading spinners. The visual noise IS the signal that the system is alive and working. Creates atmosphere of technological depth.
**Extractable principles**:
- Subtle horizontal scan-line overlays (1px lines at 5-10% opacity) on data-heavy panels
- Monospaced typography for data values (not for labels)
- Numbers that increment/decrement with visible digit transitions
- Background data streams (scrolling hex, log entries) behind primary content at very low opacity
**Web/App translation**: CSS pseudo-element scan-lines on cards|counting animations on metrics|scrolling log panels as ambient background|typewriter effects on status messages
4. Utilitarian / Belter Style (Function as Aesthetic)
**Source**: The Expanse (Belter ship interfaces), Alien (Nostromo terminals), Evangelion (NERV control panels)
**Why it works**: Raw functionality creates its own beauty. Dense information displays feel competent and trustworthy. Users who need power tools want density, not whitespace. The interface looks like it was built by engineers for engineers.
**Extractable principles**:
- High information density with clear grid structure
- Color used semantically only (green=nominal, amber=warning, red=critical, blue=informational)
- Monospaced fonts, ALL CAPS for labels, mixed case for values
- Minimal decoration -- borders are thin lines, not shadows or gradients
- Status communicated through color temperature shifts across the entire panel, not individual alerts
**Web/App translation**: Terminal-style dashboards|grid-based monitoring|semantic-only color palettes|data tables with inline sparklines
5. Neural / Organic Interface
**Source**: Ghost in the Shell (brain-computer interfaces), Warframe (modular organic UI), Sword Art Online (AR menus)
**Why it works**: Organic curves and flowing animations feel responsive and alive. The interface appears to react to the user rather than just executing commands. Creates intimacy between user and system.
**Extractable principles**:
- Rounded containers with flowing transitions (not snapping)
- Elements that slightly breathe (subtle scale oscillation, 0.5-1% over 3-4 seconds)
- Connection lines between related elements (bezier curves, not straight lines)
- Radial menus and circular navigation patterns
- Particle effects at interaction points (click ripples, hover auras)
**Web/App translation**: Radial menus for power-user shortcuts|breathing indicators for active/live elements|bezier connections in node graphs|ripple effects on interaction
6. Minimal AI Interface
**Source**: Her (OS1 interface), Blade Runner 2049 (Joi), Steins;Gate (future gadgets)
**Why it works**: When the AI is the interface, chrome disappears. Conversation becomes the UI. Visual elements serve the dialogue, not the reverse. Maximum content, minimum decoration.
**Extractable principles**:
- Large typography as primary interface element
- Generous whitespace (the anti-density approach)
- Single focal point per screen state
- Transitions are content-driven (new text appears, old fades) not chrome-driven (panels slide
Read more
name: nw-sci-fi-design-patterns description: Catalog of UI patterns from games, anime, and films with analysis of why they work -- structural principles extractable to real interfaces user-invocable: false disable-model-invocation: true
Sci-Fi Design Patterns
Pattern Categories
1. Diegetic UI (Interface Lives in the World)
**Source**: Dead Space (health bar on spine), Iron Man (JARVIS holographic workspace), Mass Effect (Omni-tool)
**Why it works**: Eliminates the cognitive split between "looking at the interface" and "being in the experience." Users stay immersed. Information is spatially anchored to the object it describes.
**Extractable principles**:
- Status indicators attached to the element they describe (badge on avatar, not separate panel)
- Context menus appear at the point of interaction, not in a fixed sidebar
- Progress indicators are part of the action element (button fills as it processes)
- Health/status of a system component shown ON the component representation
**Key insight**: Dead Space's diegetic UI works because it eliminates the split-attention effect from Cognitive Load Theory — information in the same visual plane as the game world means eyes never dart to screen corners. The trade-off (harder to parse quickly) is intentional for horror, but for productivity tools, make diegetic elements easy to read.
**Deeper examples**: Navigation waypoint (glowing floor line instead of minimap), holographic inventory that exists in real-time (enemies can attack while browsing), stasis energy as wearable semicircular meter.
**Web/App translation**: Inline editing|contextual toolbars|progress-as-button-state|status-as-color-on-node (monitoring dashboards)
2. Holographic Layering (Depth Through Transparency)
**Source**: Iron Man (JARVIS floating panels), Minority Report (gesture layers), Halo (holographic briefings)
**Why it works**: Creates spatial hierarchy without consuming screen real estate. Background layers provide context; foreground layers demand attention. Parallax between layers communicates depth.
**Extractable principles**:
- 3-4 depth layers: background (environmental/ambient) | mid-ground (contextual/secondary) | foreground (primary interaction) | overlay (urgent/modal)
- Each layer has distinct opacity range: background 10-30% | mid-ground 40-60% | foreground 70-90% | overlay 90-100%
- Blur increases with depth (backdrop-filter: blur scales per layer)
- Interactive elements always on foreground or overlay -- never bury clickable things in background layers
**Web/App translation**: Glassmorphism with semantic layers|modal stacking with blur gradients|dashboard panels at different z-depths with transparency
3. Scan-Line / Data Stream Aesthetic
**Source**: Ghost in the Shell (Standalone Complex), Blade Runner 2049, The Matrix
**Why it works**: Communicates "live data" and "processing" without explicit loading spinners. The visual noise IS the signal that the system is alive and working. Creates atmosphere of technological depth.
**Extractable principles**:
- Subtle horizontal scan-line overlays (1px lines at 5-10% opacity) on data-heavy panels
- Monospaced typography for data values (not for labels)
- Numbers that increment/decrement with visible digit transitions
- Background data streams (scrolling hex, log entries) behind primary content at very low opacity
**Web/App translation**: CSS pseudo-element scan-lines on cards|counting animations on metrics|scrolling log panels as ambient background|typewriter effects on status messages
4. Utilitarian / Belter Style (Function as Aesthetic)
**Source**: The Expanse (Belter ship interfaces), Alien (Nostromo terminals), Evangelion (NERV control panels)
**Why it works**: Raw functionality creates its own beauty. Dense information displays feel competent and trustworthy. Users who need power tools want density, not whitespace. The interface looks like it was built by engineers for engineers.
**Extractable principles**:
- High information density with clear grid structure
- Color used semantically only (green=nominal, amber=warning, red=critical, blue=informational)
- Monospaced fonts, ALL CAPS for labels, mixed case for values
- Minimal decoration -- borders are thin lines, not shadows or gradients
- Status communicated through color temperature shifts across the entire panel, not individual alerts
**Web/App translation**: Terminal-style dashboards|grid-based monitoring|semantic-only color palettes|data tables with inline sparklines
5. Neural / Organic Interface
**Source**: Ghost in the Shell (brain-computer interfaces), Warframe (modular organic UI), Sword Art Online (AR menus)
**Why it works**: Organic curves and flowing animations feel responsive and alive. The interface appears to react to the user rather than just executing commands. Creates intimacy between user and system.
**Extractable principles**:
- Rounded containers with flowing transitions (not snapping)
- Elements that slightly breathe (subtle scale oscillation, 0.5-1% over 3-4 seconds)
- Connection lines between related elements (bezier curves, not straight lines)
- Radial menus and circular navigation patterns
- Particle effects at interaction points (click ripples, hover auras)
**Web/App translation**: Radial menus for power-user shortcuts|breathing indicators for active/live elements|bezier connections in node graphs|ripple effects on interaction
6. Minimal AI Interface
**Source**: Her (OS1 interface), Blade Runner 2049 (Joi), Steins;Gate (future gadgets)
**Why it works**: When the AI is the interface, chrome disappears. Conversation becomes the UI. Visual elements serve the dialogue, not the reverse. Maximum content, minimum decoration.
**Extractable principles**:
- Large typography as primary interface element
- Generous whitespace (the anti-density approach)
- Single focal point per screen state
- Transitions are content-driven (new text appears, old fades) not chrome-driven (panels slide
Other skills on nwave.
More skills from other plugins.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
ask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
Questions about nw-sci-fi-design-patterns.
- Which coding agents can use nw-sci-fi-design-patterns?
- nw-sci-fi-design-patterns installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.

