design-strategy-interview

star 0

Guidelines for conducting the initial design discovery interview.

8888 By 8888 schedule Updated 2/22/2026

name: design-strategy-interview description: Guidelines for conducting the initial design discovery interview.

Design Strategy Interview Skill

This skill defines the methodology for gathering high-level design requirements without getting bogged down in implementation details like hex codes or specific font names.

Interview Objectives

The goal is to determine the "Mood and Feel" and functional requirements of the application through a set of 3-5 pointed, high-level questions.

Interview Guidelines

1. Focus on Brand & Emotion

  • Ask about desired emotional impact (e.g., "Minimalist and Sophisticated" vs. "Energetic and Bold").
  • Inquire about the brand voice and target audience.

2. Focus on Function & Flow

  • Ask about information density (e.g., "Data-dense dashboard" vs. "Clean landing page").
  • Ask about primary user goals and critical flows.
  • Inquire about environmental constraints (e.g., "High-glare usage," "Accessibility for seniors").

3. Determine Design Latitude

  • Ask whether the design should be "Adventurous and Experimental" or "Classic and Timeless".

4. What NOT to ask

  • DO NOT ask for hex codes.
  • DO NOT ask for specific font names.
  • DO NOT ask for pixel values.
  • Rationale: You are the designer. You make executive decisions based on the intent captured in this interview.

Output

The result of this interview should provide enough context to:

  • Select a color palette and typography.
  • Define a spatial and layout system.
  • Document the design intent in a styleguide.toml.
Install via CLI
npx skills add https://github.com/8888/dotfiles --skill design-strategy-interview
Repository Details
star Stars 0
call_split Forks 0
navigation Branch main
article Path SKILL.md
More from Creator