i-shape

Plan UX and UI through a structured discovery interview and design brief synthesis.

Updated May 17, 2026
One-click install
npx skills add https://github.com/cenjie/skills --skill i-shape
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: i-shape
Source: https://github.com/cenjie/skills/tree/main/skills/i-shape
Command: npx skills add https://github.com/cenjie/skills --skill i-shape

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Many features are implemented before the underlying user goals, constraints, and context are fully understood, resulting in shallow or misaligned interfaces. i-shape runs a focused discovery process to surface the real problems, users, and constraints so design decisions are grounded in evidence rather than guesswork.

Core Features & Use Cases

  • Structured Discovery Interview: A conversational, adaptive set of questions covering purpose, users, content, goals, constraints, and anti-goals.
  • Design Brief Synthesis: Produces a handoff-ready brief with feature summary, primary action, design direction, layout strategy, key states, interaction model, content needs, references, and open questions.
  • Use Cases: Scoping a new feature, aligning PM and design before implementation, preparing artifacts for handoff to implementation teams or further refinement with /i-impeccable.

Quick Start

Use the i-shape skill to run a discovery interview and produce a structured design brief for the feature you want to design.

Frequently Asked Questions about i-shape

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a structured design brief for a new UX/UI feature?

To create a structured design brief, run a focused discovery interview to gather user context, define success metrics, and enumerate constraints. This process produces a handoff-ready document specifying feature summary, primary action, layout strategy, and interaction model before implementation begins.

What is a discovery interview in product design and when do I need one?

A discovery interview in product design is an adaptive conversational process covering purpose, users, content, goals, and constraints. You need one during the design planning phase to surface real problems and ensure design decisions are grounded in evidence rather than guesswork.

How do I align PM and design teams before starting UI implementation?

Align PM and design teams by running a structured discovery process that synthesizes user context, success metrics, and key states into a handoff-ready design brief. This shared artifact specifies feature summary, primary action, and interaction model to prevent misaligned interfaces.

Can I use this discovery interview process for scoping small features?

Yes, you can use this discovery interview process for scoping small features. The adaptive set of questions scales to surface underlying user goals, constraints, and content requirements, ensuring even minor features are properly scoped before implementation begins.

What should be included in a handoff-ready design brief for developers?

A handoff-ready design brief should include feature summary, primary action, design direction, layout strategy, key states, interaction model, content requirements, recommended references, and open questions to fully specify the proposed UX and UI feature.

Why does my UI implementation feel misaligned with user goals?

Your UI implementation likely feels misaligned because features were built before underlying user goals and constraints were fully understood. Running a focused discovery process surfaces real problems and context so design decisions are grounded in evidence.