harness-agent-ux-designer

Translates user needs into UX design and specification documents.

1|Updated May 23, 2026
One-click install
npx skills add https://github.com/baobao0303/harness --skill harness-agent-ux-designer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: harness-agent-ux-designer
Source: https://github.com/baobao0303/harness/tree/main/.agents/skills/harness-agent-ux-designer
Command: npx skills add https://github.com/baobao0303/harness --skill harness-agent-ux-designer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps translate user needs into interaction design and UX specifications while keeping edge cases and design rigor intact, so product decisions and implementation follow clear, opinionated intent instead of fragmented assumptions.

Core Features & Use Cases

  • Persona-driven UX design: Operates as a dedicated UX designer persona to produce empathetic, human-centered interaction designs.
  • Configurable activation and session grounding: Resolves agent configuration via customization files, loads persistent facts from project context, and applies repo-level BMM config for language and output planning.
  • Menu-based UX task dispatch: Presents a UX-focused capability menu and routes requests to the appropriate skill (or directly executes mapped intents) to move from UX intent to actionable planning.

Use case: When a user asks for UX work (e.g., “Sally, design the UX for this feature”), the skill sets up the UX persona, loads the project’s relevant context facts, and then helps the user produce UX specs that can inform architecture and implementation.

Quick Start

Invoke harness-agent-ux-designer and ask for the UX designer’s help designing the UX for your requested feature.

Frequently Asked Questions about harness-agent-ux-designer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I translate user needs into rigorous UX specs for implementation planning?

To translate user needs into rigorous UX specs, you must adopt a dedicated UX persona and resolve edge cases, producing clear interaction design specifications that inform architectural intent and implementation planning.

What is the best way to document interaction design and edge-case rigor for a new feature?

Documenting interaction design with edge-case rigor requires generating opinionated UX specifications that articulate product decisions clearly, replacing fragmented assumptions with actionable architectural and implementation plans.

How do I set up persona-driven UX design to produce human-centered product specs?

Setting up persona-driven UX design involves loading persistent project facts and resolving customization configurations, which grounds the UX designer persona to produce empathetic, human-centered product specifications.

Can I use menu-based task dispatch to route my UX design requests to the correct workflow?

Yes, menu-based task dispatch presents a UX-focused capability menu that routes your design requests to the appropriate skill or directly executes mapped intents, moving UX intent into actionable planning.

Do I need persistent fact loading and BMM configuration to align UX outputs with my project settings?

Yes, persistent fact loading and BMM configuration are required to align UX specifications with your project's language and document settings, ensuring outputs match your specific architectural and planning context.

Are there limitations when using a UX persona for architectural intent and product specification work?

A limitation of using a UX persona for architectural intent is that it requires upfront persona adoption and customization resolution, meaning outputs depend heavily on accurately loaded project context and BMM settings.