Index of every page on this site: llms.txt
All skills
masihmoafi avatar

/product-design

@c0a5d13
by Masih Moafimasihmoafi/skills10 stars
Run it yourself

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.

Use this Skill: https://skilld.dev/gh/masihmoafi/skills/product-design

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈45 tokens for metadata: the name and description. ≈606 when used: this file.

Description uses 2.2% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈179 characters, or 2.2%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts3mo3 checks · Risk SAFE
  • Gen Agent Trust Hub3mo

    This skill provides a structured framework for product design and architecture. It contains only textual instructions and no executable code, remote dependencies, or security risks.

  • Socket3mo

    No alerts

  • Snyk3mo

    Risk: LOW · No issues

Signed by skilld at c0a5d13. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last week.

Activeupdated 3 weeks ago

README badge

README badge for masihmoafi/skills/product-design