shape

Plan UX and UI design through structured discovery interviews and design briefs.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/ivaylo91/Shopping-Mobile-App --skill shape-ivaylo91
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shape
Source: https://github.com/ivaylo91/Shopping-Mobile-App/tree/main/.agents/skills/shape
Command: npx skills add https://github.com/ivaylo91/Shopping-Mobile-App --skill shape-ivaylo91

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI-generated interfaces often fail because design decisions are made without understanding the feature's purpose, users, and constraints. This Skill prevents that by running a structured discovery interview before any code is written, producing a design brief that guides implementation. ## Core Features & Use Cases - Discovery Interview: Asks targeted questions about purpose, users, content, data ranges, edge cases, design goals, constraints, and anti-goals through natural dialogue. - Design Brief Generation: Synthesizes interview answers into a nine-section brief covering feature summary, primary user action, design direction, layout strategy, key states, interaction model, content requirements, recommended references, and open questions. - Use Case: Before building a new dashboard settings page, run this Skill to clarify who uses it, what states it needs (empty, loading, error), and how it should feel, then hand the confirmed brief to an implementation skill. ## Quick Start Ask the AI to shape the UX and UI for your feature, for example: "Shape the onboarding flow for new team members before we write any code."

Frequently Asked Questions about shape

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

FAQPage Schema
How do I plan UI design before writing code?

Run a structured discovery interview covering purpose, users, content, constraints, and anti-goals, then synthesize the answers into a design brief. This Skill guides that dialogue and produces the brief for implementation handoff.

What should a design brief include for a new feature?

A design brief should include a feature summary, primary user action, design direction, layout strategy, key states, interaction model, content requirements, recommended references, and open questions. This structure ensures implementers have clear guidance.

Does this Skill write any UI code?

No, this Skill is scoped to design planning only and explicitly does not write code. It produces a design brief that you hand off to an implementation skill such as /impeccable craft.

When should I use a discovery interview instead of building directly?

Use discovery when the feature's users, edge cases, or design direction are unclear, since skipping this thinking leads to generic interfaces. If you want discovery and build in one step, use /impeccable craft instead.

What happens after the design brief is confirmed?

Once you confirm the brief, it is handed off to an implementation skill like /impeccable or /impeccable craft. The brief's recommended references section points implementers to the most relevant design guidance files.