dragoon0x/optik

critique

UX-focused design review examining visual hierarchy, information architecture, emotional resonance, and user flow. Goes beyond code quality into design effectiveness.

First seen May 9, 2026

Installation

$ npx skills add dragoon0x/optik --skill critique

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from dragoon0x/optik · top by installs.

npx skills add dragoon0x/optik

Browse all from dragoon0x/optik

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 1
License LICENSE
Default branch main
Open issues 0
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,223 B
  • docs SUMMARY.md 182 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 5 installs

SKILL.md

/critique — UX Design Review

Evaluate the interface from a user experience perspective, beyond code quality.

What /critique Examines

Visual Hierarchy: Is it clear where to look first, second, third? Is there a single focal point? Do size, weight, color, and position work together or fight each other?

Information Architecture: Is content organized logically? Can users find what they need? Is the navigation clear? Are related items grouped?

Emotional Resonance: Does the design feel intentional? Does it match the brand's personality? Would a user trust this interface? Is there anything memorable?

User Flow: Are CTAs clear and prominent? Is the path from entry to action obvious? Are there dead ends? Is there cognitive overload?

Output

Provide specific, actionable feedback organized by category. Reference specific elements. Suggest concrete improvements. Do not give vague praise — every statement must be either a specific problem or a specific strength.