shape

Conduct discovery interviews and produce a structured design brief.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/ZainEldeen-Ashraf-Ibrahim-Ibrahim-Samak/SCCT --skill shape-zaineldeen-ashraf-ibrahim-ibrahim-samak
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shape
Source: https://github.com/ZainEldeen-Ashraf-Ibrahim-Ibrahim-Samak/SCCT/tree/main/.cursor/skills/shape
Command: npx skills add https://github.com/ZainEldeen-Ashraf-Ibrahim-Ibrahim-Samak/SCCT --skill shape-zaineldeen-ashraf-ibrahim-ibrahim-samak

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Many teams start building interfaces without first understanding the user, context, and constraints, which leads to poor UX, rework, and misaligned engineering effort. Shape prevents premature design decisions by running a structured discovery interview and producing a handoff-ready design brief that guides implementation.

Core Features & Use Cases

  • Guided Discovery Interview: Ask targeted questions about purpose, users, content, goals, constraints, and edge cases to gather the design context needed for thoughtful decisions.
  • Structured Design Brief: Synthesize interview responses into a clear brief covering feature summary, primary user action, design direction, layout strategy, key states, interaction model, content needs, references, and open questions.
  • Handoff Ready Output: Create an artifact suitable for handoff to designers, engineers, or the impeccable craft workflow for implementation.
  • Use Case: Product managers preparing a new dashboard feature can use Shape to clarify success metrics, data ranges, mobile constraints, and accessibility needs before any UI is sketched.

Quick Start

Run the shape skill and provide the feature purpose, target users, content examples, technical constraints, and desired success metrics so it can perform a discovery interview and produce a design brief.

Frequently Asked Questions about shape

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

FAQPage Schema
How do I create a UX design brief before writing any code?

Create a UX design brief by running a structured discovery interview to gather feature context, user goals, and constraints. This skill synthesizes your responses into a handoff-ready document covering layout strategy, interaction models, and key states.

What is the best way to plan UI design for a new product feature?

The best way to plan UI design is to define the primary user action, content requirements, and edge cases beforehand. This skill guides cross-functional teams through targeted discovery questions to prevent premature design decisions.

How do I run a UX discovery interview for product design?

Run a UX discovery interview by asking targeted questions about purpose, target users, technical constraints, and desired success metrics. The skill facilitates this process to gather the exact context needed for thoughtful UI decisions.

Can I use a design brief to hand off UX requirements to engineers?

Yes, you can use a design brief to hand off UX requirements to engineers. The skill produces a concise artifact covering feature summaries, recommended references, and open questions suitable for direct implementation handoff.

What should I include in a UI planning document for cross-functional teams?

A UI planning document should include feature summaries, layout strategies, interaction models, and open questions. The skill automatically structures these elements along with content needs and key states into a comprehensive design brief.

Why do I need a structured discovery process before sketching UI?

You need a structured discovery process to avoid poor UX, rework, and misaligned engineering effort. Starting interfaces without understanding user context and constraints leads to premature design decisions that this skill prevents.