design-first-dev

Standardize design-led development and craft-quality practices across product teams.

389|121|Updated Jan 28, 2026
One-click install
npx skills add https://github.com/menkesu/awesome-pm-skills --skill design-first-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-first-dev
Source: https://github.com/menkesu/awesome-pm-skills/tree/main/design-first-dev
Command: npx skills add https://github.com/menkesu/awesome-pm-skills --skill design-first-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams apply design-led development and craft-quality standards to UI/UX decisions, ensuring that details matter and that product narratives stay coherent across releases.

Core Features & Use Cases

  • Prototype complete flows before coding.
  • Design all states (loading, error, empty, success) to reduce surprises in production.
  • Foster cross-functional collaboration from day one to align design, engineering, and product storytelling.
  • Apply design-system thinking to ensure consistency and scalable quality across features.

Quick Start

Prototype the full user flow in a design sandbox before any code is written.

Frequently Asked Questions about design-first-dev

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is design-led development and how does it improve UI/UX decisions?

Design-led development standardizes craft-quality practices across product teams to ensure UI/UX details matter and product narratives stay coherent. It enforces a design-system mindset and captures cross-functional input throughout the product lifecycle to maintain scalable quality.

How do I prototype complete user flows before coding begins?

Prototype the full user flow in a design sandbox before any code is written. This design-led approach ensures all UI/UX states are reviewed early, capturing cross-functional input from engineering and product to align storytelling and reduce surprises in production.

Why should I design all states like loading, error, and empty before production?

Designing all states—loading, error, empty, and success—reduces surprises in production by ensuring complete UI/UX coverage. This craft-quality practice enforces a design-system mindset, capturing edge cases early in the planning phase to maintain coherent product narratives across releases.

Can I apply design-system thinking to cross-functional feature design reviews?

Yes, you can apply design-system thinking to feature design reviews to ensure consistency and scalable quality across product teams. This approach captures cross-functional input from day one, aligning design, engineering, and product management throughout the entire product lifecycle.

Does this approach require a dedicated design sandbox to prototype UI/UX flows?

A design sandbox is recommended to prototype complete flows before coding, but the core requirement is adopting a craft-quality checklist for early planning. This ensures cross-functional collaboration and design-system consistency are applied to UI/UX decisions regardless of the specific prototyping environment.

When should I not use design-led development for product management?

Design-led development is ideal for standardizing UI/UX decisions and cross-functional prototyping, but it may not suit rapid, single-feature patches requiring immediate deployment. The craft-quality checklist and design-system mindset add planning overhead that benefits complete user flows rather than isolated updates.