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 で公開
field-notes
Structured taste breakdowns of real products. The format for making taste observations legible and shareable. Use when analyzing products, writing case studies, documenting design observations, or teaching through example.
含まれるファイル（1）
- SKILL.md1.6 KB
SKILL.md（原文）
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Field Notes
The format for making taste observations legible.
How to use
/field-notesWrite a structured taste breakdown of a product in this conversation./field-notes <product>Analyze the specified product using the field notes format.
Constraints
Field Note Structure
- Product name, URL, date, category
- What it's trying to be (2-3 sentences. Not what it does. What experience it's trying to create.)
- Three things that work (specific decisions with principles behind them)
- One thing that doesn't (specific decision with reasoning and impact)
- The taste principle (one sentence: "This product demonstrates that...")
- Tags (principle-based tags for the reference library)
Writing Rules
- MUST be specific. Reference actual elements, sizes, and interactions.
- MUST connect every observation to a principle.
- MUST include at least one thing that doesn't work. No product is perfect.
- SHOULD be under 500 words. Concise analysis is harder and more useful than exhaustive analysis.
- NEVER write a field note about a product you haven't actually used.
Anti-Patterns
- Writing only about famous products everyone has already analyzed
- Describing what the product does instead of how it feels to use
- Listing features instead of evaluating decisions
- Being uniformly positive (honest analysis includes what falls short)
レビュー
まだレビューはありません。使ってみた感想をお寄せください。
同じリポジトリのスキル
概要と使いどころ
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日 更新