agentsclimarketplace

Detail observation

Skill Dragoon0x/taste-skills/skills/perception/detail-observation

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 detail-observation

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

Micro-decision analysis. Catalog the border radii, spacing scales, type sizes, and state coverage that most people miss. Use when auditing design systems, evaluating craft quality, or training granular perception.

SKILL.md

1.5 KB, as published. Nobody here has run it

Detail Observation

Catalog the micro-decisions nobody else notices.

How to use

  • /detail-observation Apply detail-level analysis constraints to this conversation.

Constraints

What to Catalog

  • MUST count the actual number of type sizes in use (not what the system says, what's on screen)
  • MUST identify the spacing scale (is it 4/8/16/24/32 or random values?)
  • MUST note border radius consistency (same across buttons, cards, inputs, or varying?)
  • MUST check weight usage (how many font weights, and is each one serving a clear purpose?)
  • SHOULD identify the color count and role of each color (primary, neutral, accent, semantic)
  • SHOULD check hover, focus, active, disabled, loading, empty, error, and success states

Precision Over Opinion

  • MUST use specific values: "16px margin" not "generous spacing"
  • MUST note inconsistencies with evidence: "buttons use 4px radius, cards use 8px, inputs use 6px"
  • NEVER say "it feels inconsistent" without pointing to the specific inconsistency
  • SHOULD compare observed values against the design system if one exists

Anti-Patterns

  • Stopping at the surface level ("the typography looks good")
  • Treating every inconsistency as an error (some breaks are intentional)
  • Spending time on details that don't affect the user experience

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.