Notice what's deliberately missing from a design. Restraint is a taste signal. Use when studying minimalist products, evaluating design maturity, or understanding the power of removal.
日本語の概要は準備中です。原文の説明を表示しています。
Dragoon0x/taste-skills62026年2月27日 更新
無料GitHub で公開
quality-checklist
Systematic design quality evaluation. Hierarchy, type, color, space, craft, system. Use when evaluating whether a design is ready to ship, running quality audits, or setting quality standards.
含まれるファイル（1）
- SKILL.md2.0 KB
SKILL.md（原文）
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Quality Checklist
A systematic pass through every dimension of design quality.
How to use
/quality-checklistRun a quality evaluation on any design in this conversation.
Constraints
Hierarchy
- Clear primary element on every screen
- Visual weight matches content priority
- No unintentional competing elements at the same hierarchy level
- Eye path follows the intended reading order
Typography
- Type scale uses a consistent ratio
- Weight usage is systematic with named purposes
- Line height varies appropriately (tighter headlines, looser body)
- No more than 4-6 sizes per screen with clear justification
- Typeface matches product voice
Color
- Every color has a clear, non-overlapping role
- Semantic colors are consistent everywhere
- Neutrals do 80-90% of the heavy lifting
- Sufficient contrast for accessibility (WCAG AA minimum)
Space
- Spacing follows a consistent scale
- Proximity signals correct relationships
- Density matches the use case
- Margins create appropriate breathing room
Craft
- Border radii consistent across element types
- Alignment pixel-perfect where intended
- All states covered: loading, empty, error, success, overflow
- Transitions purposeful and consistently timed
System
- Design could scale to 10 more screens without breaking
- Another designer could extend this without asking questions
- Components are reusable, not one-offs
- System breaks are intentional, not accidental
Anti-Patterns
- Checking only visual polish and ignoring information architecture
- Treating the checklist as pass/fail instead of diagnostic
- Running the checklist once and never revisiting
レビュー
まだレビューはありません。使ってみた感想をお寄せください。
同じリポジトリのスキル
概要と使いどころ
Explain the same design observation to a designer, a developer, and a non-technical stakeholder. Same insight, three languages. Use when working cross-functionally or presenting design decisions to mixed audiences.
日本語の概要は準備中です。原文の説明を表示しています。
Dragoon0x/taste-skills62026年2月27日 更新
Palette roles, restraint, semantic consistency, and when fewer colors means better design. Use when building color palettes, evaluating color usage, or diagnosing color-related design problems.
日本語の概要は準備中です。原文の説明を表示しています。
Dragoon0x/taste-skills62026年2月27日 更新
Understand the constraints a design was built under and evaluate quality within that context. Use when reviewing work that had limited time, budget, or team size, or when assessing whether constraints were handled well.
日本語の概要は準備中です。原文の説明を表示しています。
Dragoon0x/taste-skills62026年2月27日 更新
Structured exposure habits for building taste through relentless, intentional consumption. Not passive scrolling. Active intake across design, architecture, film, music, food, and culture. Use when building a taste practice, advising on professional development, or diagnosing why someone's design range feels narrow.
日本語の概要は準備中です。原文の説明を表示しています。
Dragoon0x/taste-skills62026年2月27日 更新
Consistent radii, pixel-perfect alignment, state coverage, and the details that signal design quality. Use when polishing designs, auditing quality, or evaluating whether a design is ready to ship.
日本語の概要は準備中です。原文の説明を表示しています。
Dragoon0x/taste-skills62026年2月27日 更新