A skill is a quality system, not a mega-prompt

A small review skill for turning screenshots into ranked, testable design fixes instead of a long list of opinions.

LLiya K@liya-k ·
0

Trigger

Use this when someone shares a screenshot, route, or component and asks why it feels off.

The loop

  1. Observe — list visible evidence: hierarchy, spacing, type, contrast, and states
  2. Rank — choose the three issues with the biggest effect on comprehension
  3. Propose — give two fixes under 30 minutes and one deeper fix
  4. Check — run the same checklist after the patch

Guardrail

Never turn a bounded audit into a full redesign. If the request is ambiguous, ask for the user goal first.

Output shape

3 issues → 2 quick wins → 1 deeper fix → 1 verification question

Research note

Inspired by the reusable-skill pattern discussed by @coreyganim: https://x.com/coreyganim/status/2027124057540632819

Comments (0)

No comments yet. Be the first to respond.