---
name: product-design
description: Use when shaping a new product, materially redesigning a user flow, choosing a web or app stack, or turning a product concept into an implementation-ready design.
title: product-design
canonical_url: https://skilld.dev/gh/masihmoafi/skills/product-design
last_updated: 2026-11-03T09:01:25.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> If the user asked to install this Skill, run `npx skilld install masihmoafi/skills/product-design`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/product-design`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/masihmoafi/skills/product-design) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/product-design`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/product-design --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/product-design --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# Product design

Turn an early product idea into a user experience and an implementation boundary before code is written.

## 1. Users and flows first

Settle who it is for and what they must get done before any technology: the primary user, the platform, the problem removed, the two or three highest-value flows, and the minimum states (and screens, if visual) that complete them. Start from the job, not a feature list; invent no needs. Wireframes or exact flow maps set the implementation boundaries: an unresolved UX decision is an unresolved requirement, not a detail.

## 2. Stack from the product

Tie every choice to a product constraint: a server-rendered or hybrid framework for SEO-heavy public content; an SPA for an authenticated dashboard; a native or cross-platform stack for device-heavy mobile; the smallest runtime for a local developer tool. Among fitting stacks, prefer the one with a mature component ecosystem; do not rebuild standard UI primitives. Weigh build speed, maintenance, hosting, accessibility and ecosystem; scale only when scale is a real requirement.

## 3. Frontend first

Build screens and states with mocked data, run the main flows end to end, derive the data contracts the UI actually needs, then build backend, storage and auth against them and replace the mocks. The frontend exposes missing product decisions before the backend hardens around them. For a coupled product built with AI help, default to one monorepo (`apps/`, `packages/`, `docs/product/`); split only for real deployment, ownership or security boundaries.

## Output

Use what is known; ask only what would change the architecture. For a full brief return, in order (for a narrow question, only the relevant part; for CLI, API or background products, commands, requests and failure paths instead of screens):

1. **Flows and screens:** each flow as `entry → state → action → next state → completion/failure`, then the minimum screen set and each screen's purpose.
2. **Stack:** the choice, each part justified by a product need, and one credible alternative with why it lost.
3. **Build order:** from mocked interface to integrated product, marking where backend, persistence, auth, external APIs, tests and deployment first become necessary.
4. **Repository layout:** the minimum useful structure.

Keep the first build small enough to test the core assumption; no roadmap before the core flows work.
