ux-engineer

Coordinate UX design tasks across planning, generation, and evaluation.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/asfbay-bit/opchain --skill ux-engineer-asfbay-bit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ux-engineer
Source: https://github.com/asfbay-bit/opchain/tree/main/skills/ux-engineer
Command: npx skills add https://github.com/asfbay-bit/opchain --skill ux-engineer-asfbay-bit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Tri-agent UX design harness accelerates rigorous planning, generation, and evaluation of UI work to improve quality and reduce bias across design sprints.

Core Features & Use Cases

  • Tri-design workflow: Planner → Generator → Evaluator for UI assets and flows.
  • Cross-screen flow auditing and a living component library to ensure fidelity.
  • Token-driven design system with accessibility checks and dash-forge routing.

Quick Start

Describe your project brief and target users to start the design planning.

Frequently Asked Questions about ux-engineer

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

FAQPage Schema
How do I structure a UX design sprint to reduce bias and improve interface quality?

A tri-agent UX design harness accelerates rigorous planning, generation, and evaluation of UI work for product sprints. It enforces a Planner, Generator, and Evaluator contract alongside accessibility checks to improve quality and reduce bias across design iterations.

What is the best way to generate UI component libraries and cross-screen flows?

The best way to generate cross-screen flows and component libraries is using a token-driven design system within a tri-agent workflow. This approach maintains a living component library and applies cross-screen flow auditing to ensure high fidelity across all product screens.

How do I start UX design planning for a specific product brief?

To start UX design planning, describe your project brief and target users to initiate the planning phase. The system uses this input to generate structured design briefs, component libraries, and cross-screen flows tailored to your product sprint requirements.

Can I resume a UX design workflow from a specific checkpoint if iteration is interrupted?

Yes, you can resume the UX design workflow from a specific checkpoint. The system supports checkpoint-based resume functionality, allowing you to continue the planning, generation, and evaluation contract exactly where the design sprint was paused.

Does this UX workflow support accessibility checks and tokenized design systems?

Yes, the UX workflow supports both accessibility checks and tokenized design systems. It applies token-driven design rules to evaluate generated UI assets, ensuring components meet accessibility standards before they are added to the living library.