quality-speed
Decides when quality matters vs move fast, based on Dylan Field (Figma) craft philosophy and Brian Chesky (Airbnb) details obsession. Use when balancing shipping speed with excellence, deciding if refactoring is needed, or determining which details create moats vs which to skip.
Packaged view
This page reorganizes the original catalog entry around fit, installability, and workflow context first. The original raw source lives below.
Install command
npx @skill-hub/cli install menkesu-awesome-pm-skills-quality-speed
Repository
Skill path: quality-speed
Decides when quality matters vs move fast, based on Dylan Field (Figma) craft philosophy and Brian Chesky (Airbnb) details obsession. Use when balancing shipping speed with excellence, deciding if refactoring is needed, or determining which details create moats vs which to skip.
Open repositoryBest for
Primary workflow: Design Product.
Technical facets: Full Stack, Designer.
Target audience: everyone.
License: Unknown.
Original source
Catalog source: SkillHub Club.
Repository owner: menkesu.
This is still a mirrored public skill entry. Review the repository before installing into production workflows.
What it helps with
- Install quality-speed into Claude Code, Codex CLI, Gemini CLI, or OpenCode workflows
- Review https://github.com/menkesu/awesome-pm-skills before adding quality-speed to shared team environments
- Use quality-speed for development workflows
Works across
Favorites: 0.
Sub-skills: 0.
Aggregator: No.
Original source / Raw SKILL.md
---
name: quality-speed
description: Decides when quality matters vs move fast, based on Dylan Field (Figma) craft philosophy and Brian Chesky (Airbnb) details obsession. Use when balancing shipping speed with excellence, deciding if refactoring is needed, or determining which details create moats vs which to skip.
---
# Quality vs Speed Framework
## When This Skill Activates
Claude uses this skill when:
- Deciding "should I refactor this before shipping?"
- Balancing craft quality vs speed
- Evaluating if details matter for this feature
- Choosing between polish and iteration
## Core Frameworks
### 1. Craft Creates Moats (Source: Dylan Field, Figma)
**When Quality Matters:**
- Core product experience
- Competitive differentiators
- Brand touchpoints
- High-frequency use
**When Speed Matters:**
- Internal tools
- Experiments
- Non-core features
### 2. The Details Decision Matrix
```
│ USER-FACING │ INTERNAL
────────────────────┼─────────────┼──────────
CORE PRODUCT │ HIGH CRAFT │ MEDIUM
NON-CORE FEATURE │ MEDIUM │ LOW
EXPERIMENT │ LOW │ LOW
```
---
## Action Templates
### Template: Quality Assessment
```markdown
# Feature: [Name]
## Context
- User-facing: [yes/no]
- Core product loop: [yes/no]
- Frequency of use: [daily/weekly/monthly]
- Competitive advantage: [yes/no]
## Quality Level Decision
**HIGH CRAFT:**
- Time investment: [X days]
- Polish areas: [list]
**MOVE FAST:**
- Ship threshold: [works, looks okay]
- Time budget: [X days]
## Decision: [HIGH/MEDIUM/LOW craft]
```
---
## Quick Reference
### ⚡ Quality-Speed Checklist
**High Craft Signals:**
- [ ] Core product loop
- [ ] User-facing and frequent
- [ ] Competitive differentiator
- [ ] Brand moment
**Move Fast Signals:**
- [ ] Internal tool
- [ ] One-time use
- [ ] Experiment
- [ ] Behind the scenes
---
## Key Quotes
**Dylan Field:**
> "AI makes design, craft, and quality the new moat for startups."
**Brian Chesky:**
> "Leaders are in the details, but only the details that matter."