Product Design Discovery
Establishes user tasks and business meaning for new surfaces and vague product requests.
Install
npx skills add lobehub/lobehub --skill product-design -g -a claude-code -y- Repository
- lobehub/lobehub83.7k
- Category
- Design
- Updated
- 3d ago
- License
- See repository
- Context cost
- Mediumabout 2,510 tokens
- Runs scripts
- No, instructions only
What it does
Use for new surfaces, redesigns and vague product asks: establish user tasks and business meaning. Built-screen audits and visual polish have separate skills.
Product Design
Decide what to build and why before arguing about spacing.
Two rules are non-negotiable:
Never design from the surface. Establish what the business actually models first.
Never turn the business model into the information architecture. The domain constrains what the surface may claim; the user's retrieval and decision task determines how the surface is organized. (
P-14)
This skill handles product meaning first. It may hand a grounded frame to ux or
design-prototype, but discovery does not require implementation or a prototype.
Strip out every framework, table and component name: if no product insight remains,
the finding belongs in an engineering skill.
Relationship to other skills
| Skill | Question | When |
|---|---|---|
| product-design | What should this surface be, and why? | Before or during framing |
| ux | How should the interaction behave and feel? | While designing or building |
| ux-audit | Does the built surface honor those rules? | After it exists |
| design-prototype | How can a materialized interaction be tested? | When a prototype is useful |
