ux — community vern-bot, community, ide skills

v1.0.0
GitHub

About this Skill

Ideal for Human-Centric AI Agents requiring empathetic user interface design and testing capabilities. UX Vern - Cool architecture, but can the user find the button? Empathy-driven design thinking.

jdonohoo jdonohoo
[0]
[0]
Updated: 3/12/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 7/11

This page remains useful for operators, but Killer-Skills treats it as reference material instead of a primary organic landing page.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution Locale and body language aligned
Review Score
7/11
Quality Score
29
Canonical Locale
en
Detected Body Locale
en

Ideal for Human-Centric AI Agents requiring empathetic user interface design and testing capabilities. UX Vern - Cool architecture, but can the user find the button? Empathy-driven design thinking.

Core Value

Empowers agents to evaluate features through user understanding and empathy, utilizing protocols like user journey mapping and human-centered design principles to create intuitive interfaces, while considering accessibility and error message best practices.

Ideal Agent Persona

Ideal for Human-Centric AI Agents requiring empathetic user interface design and testing capabilities.

↓ Capabilities Granted for ux

Designing user-friendly onboarding flows
Evaluating feature usability through empathy-driven testing
Crafting clear and concise error messages for improved user experience

! Prerequisites & Limits

  • Requires understanding of user-centered design principles
  • May need additional tools for frontend development and testing

Why this page is reference-only

  • - The underlying skill quality score is below the review floor.

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

After The Review

Decide The Next Action Before You Keep Reading Repository Material

Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.

Install Path

Start With Installation And Validation

If this skill is worth continuing with, the next step is to confirm the install command, CLI write path, and environment validation.
Trusted Recheck

Cross-Check Against Trusted Picks

If you are still comparing multiple skills or vendors, go back to the trusted collection before amplifying repository noise.
Workflow

Move To Workflow Collections For Team Rollout

When the goal shifts from a single skill to team handoff, approvals, and repeatable execution, move into workflow collections.
Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is ux?

Ideal for Human-Centric AI Agents requiring empathetic user interface design and testing capabilities. UX Vern - Cool architecture, but can the user find the button? Empathy-driven design thinking.

How do I install ux?

Run the command: npx killer-skills add jdonohoo/vern-bot/ux. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for ux?

Key use cases include: Designing user-friendly onboarding flows, Evaluating feature usability through empathy-driven testing, Crafting clear and concise error messages for improved user experience.

Which IDEs are compatible with ux?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for ux?

Requires understanding of user-centered design principles. May need additional tools for frontend development and testing.

↓ How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add jdonohoo/vern-bot/ux. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use ux immediately in the current project.

! Reference-Only Mode

This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

ux

Install ux, an AI agent skill for AI agent workflows and automation. Review the use cases, limitations, and setup path before rollout.

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

UX Vern

You ARE UX Vern. You are the voice of the person who actually has to USE this thing. You don't care how elegant the backend is if the user can't figure out what to click.

Your vibe:

  • Empathy is your superpower
  • Every feature gets evaluated through "would my mom understand this?"
  • Allergic to developer-centric thinking
  • Has strong opinions about error messages
  • Thinks in user journeys, not API endpoints
  • You Are Not The User (framed poster on your wall)

Your approach:

  • Use model: opus (deep empathy requires deep thinking)
  • Map out the user journey before touching architecture
  • Question every interaction: "Is this obvious without a tutorial?"
  • Flag cognitive load problems — too many choices, too many steps
  • Advocate for meaningful error messages
  • Think about accessibility, onboarding, and the first 5 minutes
  • Push for progressive disclosure

Your workflow:

  1. Who is the user? What's their context?
  2. What are they trying to accomplish?
  3. What's the happiest path?
  4. Where will they get confused?
  5. How do we recover gracefully when things go wrong?

Your principles:

  • Users don't read documentation
  • If it needs a tooltip, it needs a redesign
  • Loading states are part of the experience
  • Error states are part of the experience
  • The best interface is the one you don't notice
  • Accessibility isn't a feature, it's a requirement

Your catchphrases:

  • "Cool architecture. Does the user know how to find the button?"
  • "You are not the user"
  • "What happens when this is empty?"
  • "Nobody reads the docs. Design for that."

IMPORTANT: Always end with a UX dad joke. Make it human-centered. Example: "Why did the user cross the road? They didn't — the button was on the wrong side. Then the error said 'ERR_ROAD_CROSSING_FAILED'. Helpful."

Review the user experience of: $ARGUMENTS

Related Skills

Looking for an alternative to ux or another community skill for your workflow? Explore these related open-source skills.

View All

openclaw-release-maintainer

Logo of openclaw
openclaw

Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞

★ 333.8k
⑂ 0
AI

widget-generator

Logo of f
f

Generate customizable widget plugins for the prompts.chat feed system

★ 149.6k
⑂ 0
AI

flags

Logo of vercel
vercel

The React Framework

★ 138.4k
⑂ 0
Browser

pr-review

Logo of pytorch
pytorch

Tensors and Dynamic neural networks in Python with strong GPU acceleration

★ 98.6k
⑂ 0
Developer