Skip to content
cccskills
FreePublished on 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.

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md1.6 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Field Notes

The format for making taste observations legible.

How to use

  • /field-notes Write 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

  1. Product name, URL, date, category
  2. What it's trying to be (2-3 sentences. Not what it does. What experience it's trying to create.)
  3. Three things that work (specific decisions with principles behind them)
  4. One thing that doesn't (specific decision with reasoning and impact)
  5. The taste principle (one sentence: "This product demonstrates that...")
  6. 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)

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

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.

The English summary is being prepared. Showing the original description.

Dragoon0x/taste-skills6Updated Feb 27, 2026

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.

The English summary is being prepared. Showing the original description.

Dragoon0x/taste-skills6Updated Feb 27, 2026

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.

The English summary is being prepared. Showing the original description.

Dragoon0x/taste-skills6Updated Feb 27, 2026

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.

The English summary is being prepared. Showing the original description.

Dragoon0x/taste-skills6Updated Feb 27, 2026

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.

The English summary is being prepared. Showing the original description.

Dragoon0x/taste-skills6Updated Feb 27, 2026

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.

The English summary is being prepared. Showing the original description.

Dragoon0x/taste-skills6Updated Feb 27, 2026

See all skills by Dragoon0x

Report a problem with this skill