# Product Design Discovery

Establishes user tasks and business meaning for new surfaces and vague product requests.

- Repository: https://github.com/lobehub/lobehub (83676 stars)
- Category: Design
- License: see repository
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add lobehub/lobehub --skill product-design -g -a claude-code -y`
Codex: `npx skills add lobehub/lobehub --skill product-design -g -a codex -y`
Cursor: `npx skills add lobehub/lobehub --skill product-design -g -a cursor -y`
Gemini CLI: `npx skills add lobehub/lobehub --skill product-design -g -a gemini-cli -y`

## Description

Use for new surfaces, redesigns and vague product asks: establish user tasks and business meaning. Built-screen audits and visual polish have separate skills.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# 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](../ux/SKILL.md)                             | How should the interaction behave and feel?   | While designing or building |
| [ux-audit](../ux-audit/SKILL.md)                 | Does the built surface honor those rules?     | After it exists             |
| [design-prototype](../design-prototype/SKILL.md) | How can a materialized interaction be tested? | When a prototype is useful  |

## Select the smallest run mode

The rest: https://github.com/lobehub/lobehub/blob/HEAD/.agents/skills/product-design/SKILL.md