Plan UX and UI through structured discovery interviews and design briefs.
npx skills add https://github.com/DanialHaseeb/dotfiles --skill shape-danialhaseeb
Please help me install this Agent Skill. Skill: shape Source: https://github.com/DanialHaseeb/dotfiles/tree/main/codex/skills/shape Command: npx skills add https://github.com/DanialHaseeb/dotfiles --skill shape-danialhaseeb
Many teams jump to UI implementations without fully understanding the user need, context, constraints, or success criteria, producing shallow interfaces that fail in real-world use. This Skill structures discovery so design decisions are based on clarified goals and constraints rather than guesswork.
Ask the assistant to run a discovery interview for the new onboarding feature and produce a structured design brief.
High-intent search queries and answers about installing and using this skill.
To create a UX design brief before coding, run a structured discovery interview with stakeholders to capture purpose, constraints, and design direction, synthesizing findings into a handoff-ready document for implementation.
A discovery interview in product planning is a structured conversational process that uncovers user needs, success metrics, data requirements, constraints, anti-goals, and accessibility requirements to inform UI and UX design decisions.
You align product, design, and engineering teams by running a structured discovery interview that clarifies goals, captures key states, defines interaction models, and documents open questions in a comprehensive design brief.
Yes, you can use this structured design planning process for both web and mobile features during early product discovery to establish layout strategy, content requirements, and interaction models prior to UI implementation.
A handoff-ready design brief should include feature summary, primary user action, design direction, layout strategy, key states, interaction model, content requirements, recommended references, and open questions for developers.
UI implementations fail in real-world use without design-driven planning because teams jump to coding without fully understanding user needs, context, constraints, or success criteria, resulting in shallow interfaces based on guesswork.
cano721Generate cross-functional feature ideas for new product discovery.
buiphucminhtamTranslate BRD inputs into design briefs, tokens, and wireframes for frontend teams.
clawpod-appPlan, execute, and synthesize user research studies to inform product decisions.
martinffxConduct discovery interviews to define feature scope and requirements.
