agentsclimarketplace

Ux strategy

Skill nevitonsantana/adaptive-skills/skills/ux-strategy

38 portable Agent Skills for disciplined, reviewable AI-assisted work across Codex, Claude Code, GitHub Copilot, and compatible agents.

Install
npx -y skills add nevitonsantana/adaptive-skills --skill ux-strategy

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

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 1 stars1 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

Compare plausible UX directions, surface trade-offs, and take a position when the interaction approach is still open.

SKILL.md

1.8 KB, 345 tokens by cl100k_base, as published. Nobody here has run it

Overview

Use this skill when the real problem is choosing a direction, not polishing an already-set interface.

When to Use

  • new flows
  • major interaction choices
  • ambiguous UX direction

When NOT to Use

  • local visual polish
  • auditing a screen that already exists

Core Moves

  1. Reframe the problem.
  2. Map 2–3 plausible directions.
  3. Name gains, costs, and success conditions.
  4. Take a position with a visible trade-off.

Optional Modules

  • Constraint lens — Bring in business, technical, or operational constraints when the direction cannot be judged on UX alone.
  • Counter-argument — Capture the strongest reason your recommendation could be wrong.
  • Experiment lens — Translate the strategic choice into a next validation step.

Activation Triggers

  • Use the constraint lens when other functions can block the direction.
  • Use counter-argument when the team is converging too quickly.
  • Use experiment lens when you need evidence before committing.

Expected Output

  • better-framed problem
  • compared directions
  • recommended path

Verification

  • At least two real alternatives were considered.
  • The trade-off is explicit.
  • The recommendation is actionable, not vague preference.

Handoff Signals

  • The next step is visual design or UX writing work.
  • The choice affects product or technical planning beyond design.

Pairs Well With

  • heuristic-audit
  • triad-check
  • feature-planning

Anti-patterns

  • Calling a preference a strategy.
  • Comparing a real option with a strawman.
  • Ending with “it depends” when a decision is possible.

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.