agentsclimarketplace

Field notes

Skill Dragoon0x/taste-skills/skills/evaluation/field-notes

Agent skills for design taste and visual judgment. Hierarchy, typography, color, spacing, interaction quality, and the invisible decisions that separate good design from great design

Install
npx -y skills add Dragoon0x/taste-skills --skill field-notes

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

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.

SKILL.md

1.6 KB, as published. Nobody here has run it

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)

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.