shape

Plan UX/UI by interviewing stakeholders and generating a structured design brief.

Updated Apr 19, 2026
One-click install
npx skills add https://github.com/42team-ru/mpit-final --skill shape-42team-ru
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shape
Source: https://github.com/42team-ru/mpit-final/tree/main/frontend/.claude/skills/shape
Command: npx skills add https://github.com/42team-ru/mpit-final --skill shape-42team-ru

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan the UX and UI for a feature by running a structured discovery interview and producing a design brief that guides implementation.

Core Features & Use Cases

  • Phase 1: Discovery Interview to capture goals, constraints, context, and success criteria.
  • Phase 2: Design Brief synthesis detailing feature summary, design direction, layout strategy, states, interactions, and content requirements.
  • Use Case: Before coding, generate a design brief to align teams and reduce risk.

Quick Start

Provide a structured discovery interview for a feature and generate a design brief that guides implementation.

Frequently Asked Questions about shape

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

FAQPage Schema
What is a UX design brief and when do I need one?

A UX design brief is a structured document capturing feature goals, design direction, layout, states, and interactions. You need a design brief before implementation to align stakeholders and reduce project risk.

How do I plan UX and UI for a feature before coding?

Plan UX and UI by running a structured discovery interview to capture goals and constraints, then synthesizing the findings into a formal design brief that guides implementation and stakeholder handoff.

What should a design brief include for stakeholder handoff?

A design brief for stakeholder handoff should include a feature summary, design direction, layout strategy, states, interactions, and content requirements synthesized from discovery interview findings.

Can I use a design brief to support handoff to implementation skills?

Yes, a structured design brief supports handoff to implementation skills by documenting feature summary, design direction, states, and interactions, providing clear guidance without writing code directly.

Does generating a design brief require writing code?

No, generating a design brief does not require writing code. It focuses on discovery questions and synthesis into documented sections for design direction, layout, states, and content requirements.

What questions are asked during a UX discovery interview?

A UX discovery interview asks structured questions to capture project goals, constraints, context, and success criteria, which are then synthesized into a formal design brief for implementation guidance.