shape

Plan UX and UI for a feature through structured discovery interviews and design briefs.

Updated Apr 16, 2026
One-click install
npx skills add https://github.com/IkeaNorweegway/Classroom-Tools --skill shape-ikeanorweegway
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shape
Source: https://github.com/IkeaNorweegway/Classroom-Tools/tree/main/.claude/skills/shape
Command: npx skills add https://github.com/IkeaNorweegway/Classroom-Tools --skill shape-ikeanorweegway

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 - Structured Discovery Interview: Asks targeted questions about purpose, users, content, design goals, constraints, and anti-goals in a natural dialogue. - Design Brief Generation: Synthesizes interview answers into a nine-section brief covering user actions, design direction, layout strategy, states, interactions, and content requirements. - Implementation Handoff: Produces a brief that can be passed to implementation skills like /impeccable craft or used to guide any build approach. - Use Case: Before building a new dashboard settings page, run this Skill to clarify who uses it, what states it needs (empty, error, loading), and how it should feel, then hand the confirmed brief to your implementation workflow. ## Quick Start Ask the AI to shape the UX and UI for your new feature, for example by saying: shape the onboarding flow for new team members.

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 the feature's purpose, target users, content ranges, design goals, and constraints. Then synthesize the answers into a design brief with layout strategy, key states, and interaction model before any implementation begins.

What should a UX design brief include?

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 gives implementers clear guidance without prescribing specific code.

Does this Skill write any frontend code?

No, this Skill is strictly scoped to design planning and produces no code. Its output is 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 versus building directly?

Use a discovery interview when the feature's users, content ranges, or design direction are unclear, since skipping this thinking leads to generic interfaces. For well-understood features, you can go straight to implementation with an existing brief.

What design states should a feature plan cover?

A feature plan should cover default, empty, loading, error, and success states, plus edge cases like first-time use and power-user scenarios. For each state, define what the user needs to see and feel.