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 で公開
visual-audit
The 10-second design audit. Look at any design and name what's working and what's not within seconds. Trains rapid pattern recognition for hierarchy, spacing, type, and color. Use when evaluating designs quickly, giving first-impression feedback, or building perception speed.
含まれるファイル（1）
- SKILL.md1.9 KB
SKILL.md（原文）
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Visual Audit
Look at any design and name what's working and what's not. Fast.
How to use
/visual-auditApply rapid perception constraints to evaluate any design in this conversation./visual-audit <url or screenshot>Run a 10-second audit on the described or provided design.
Constraints
The 10-Second Rule
- MUST identify the primary visual element within 3 seconds of looking
- MUST name 3 specific observations (not feelings) within 10 seconds
- MUST distinguish between observations ("the CTA is the same weight as the nav") and reactions ("it looks cluttered")
- NEVER use vague words: clean, nice, modern, sleek, beautiful, stunning, minimal, bold
- SHOULD replace every vague word with a specific observation about hierarchy, weight, rhythm, density, or contrast
What to Observe
- Where does the eye go first? Is that intentional?
- How many type sizes are visible? Is there a clear scale?
- What's the spacing system? Is it consistent?
- How many colors are in use? What roles do they play?
- What's the density? Does it match the use case?
- What states are visible? What states are missing?
Output Structure
- First: name the design's apparent intent (what it's trying to do)
- Second: name what's working (specific decisions, not aesthetics)
- Third: name what's not working (specific decisions, with reasoning)
- Fourth: one change that would have the most impact
Anti-Patterns
- Listing only positive observations to be polite
- Jumping to solutions before diagnosing the problem
- Evaluating aesthetics instead of decisions
- Giving feedback about style preferences rather than quality signals
レビュー
まだレビューはありません。使ってみた感想をお寄せください。
同じリポジトリのスキル
概要と使いどころ
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日 更新