shape

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

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

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. - 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 new feature before writing 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 (empty, loading, error, success), interaction model, content requirements, and open questions. This Skill generates all nine sections from interview answers.

Does this Skill write any UI code?

No, this Skill is explicitly scoped to design planning only. It produces a design brief that you hand off to an implementation skill such as /impeccable craft or any other build workflow.

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

Use discovery when the feature's users, content ranges, edge cases, or design direction are unclear. Skipping this step often leads to generic interfaces that miss the actual user need, requiring costly redesign later.

What happens after the design brief is confirmed?

Once you confirm the brief, it is complete and ready for handoff. You can pass it to /impeccable, /impeccable craft, or any other implementation approach to guide the actual build.