skills.rest
thegeronimo
thegeronimoCOMMUNITY
Explore all skills by this author →
𝕏@RyskyGeronimoGitHub

ui-flow

Coordinate UI changes across views and styles with browser QA evidence.

44|8|Updated Jul 14, 2025
Search Tags:#frontend#execution-plan#design-validation#ui-flow#ui-governance#browser-qa
One-click install
npx skills add https://github.com/thegeronimo/hyperopen --skill ui-flow
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ui-flow
Source: https://github.com/thegeronimo/hyperopen/tree/main/.agents/skills/ui-flow
Command: npx skills add https://github.com/thegeronimo/hyperopen --skill ui-flow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

UI teams often struggle to coordinate UI changes with browser QA, design validation, and implementation review, causing misaligned visuals and delayed delivery.

Core Features & Use Cases

  • Govern UI changes across views and styles with explicit QA and design governance.
  • Evidence-driven workflow that captures browser QA results, exec plans, and review signoffs.
  • Cross-module coordination for frontend components under /hyperopen/src/hyperopen/views/** and /hyperopen/src/styles/**.

Quick Start

Invoke ui-flow to coordinate a UI change with browser QA evidence and design validation.

Frequently Asked Questions about ui-flow

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

FAQPage Schema
How do I coordinate frontend UI changes with browser QA and design validation?▼

Coordinate frontend UI changes by applying governance workflows to views and styles directories, requiring explicit browser QA evidence and an active ExecPlan before implementation review sign-off.

What is the best way to govern UI changes across views and styles to ensure design fidelity?▼

Govern UI changes by enforcing deterministic guidance and strict guardrails across frontend interaction flows, capturing browser QA results and exec plans to validate design fidelity before delivery.

How does evidence-driven UI review work for frontend interaction flows?▼

Evidence-driven UI review works by requiring explicit browser QA evidence and an active ExecPlan before sign-off, ensuring deterministic guidance and strict guardrails are satisfied for all UI changes.

Can I use this workflow to validate UI changes in specific frontend directories?▼

You can validate UI changes in specific frontend directories, specifically targeting interaction flows under /hyperopen/src/hyperopen/views/** and /hyperopen/src/styles/** for cross-module coordination and governance.

Do I need an active ExecPlan to get sign-off on UI changes?▼

You need an active ExecPlan to get sign-off on UI changes, as the workflow requires explicit browser QA evidence and an active ExecPlan before allowing implementation review sign-off.

Why does UI delivery get delayed when coordinating design validation and browser QA?▼

UI delivery gets delayed when teams lack coordinated governance across views and styles, causing misaligned visuals and unverified browser QA coverage that an evidence-driven workflow with strict guardrails prevents.

Related Skills

Explore More Design & Creative Skills→
thegeronimothegeronimo
44

feature-flow

Coordinates Hyperopen feature changes via ExecPlan generation, test scaffolding, and reviewer handoffs.

Community
Advanced
balajivisbalajivis
2

browse

Automate browser navigation and interaction workflows to test web applications.

Community
Advanced
asadbek21coderasadbek21coder

frontend-guidelines

Enforce Vue 3 frontend conventions across components, routing, and state management.

Community
Intermediate
jamesrochabrunjamesrochabrun
194

qa-test-planner

Generate QA test plans, manual cases, regression suites, and bug reports.

Community
Advanced