owf-role-ui-ux-design-steward

Drive UI/UX stewardship tasks for OWFINANCE frontend premium journeys.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/oteroweb/OWFINANCE2026 --skill owf-role-ui-ux-design-steward
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: owf-role-ui-ux-design-steward
Source: https://github.com/oteroweb/OWFINANCE2026/tree/main/.agents/skills/owf-role-ui-ux-design-steward
Command: npx skills add https://github.com/oteroweb/OWFINANCE2026 --skill owf-role-ui-ux-design-steward

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures design consistency, accessibility, and high-quality frontend experiences across OWFINANCE2026 journeys, reducing design debt and guiding implementation.

Core Features & Use Cases

  • Preserve OWFINANCE's premium visual language (glassmorphism, Outfit, Deep Ocean palette, rounded panels, and smooth charts) across web and mobile.
  • Guard mobile-first behavior, Lite vs Pro differences, and clarity in high-trust fintech flows.
  • Maintain canonical design rules, flow audits, handoff notes, and UX decision logs in the Drive hub OWFINANCE.

Quick Start

Review current frontend screens and reference the canonical OWFINANCE design rules to produce a design brief and handoff notes.

Frequently Asked Questions about owf-role-ui-ux-design-steward

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

FAQPage Schema
How do I maintain UI consistency across mobile and web fintech journeys?

Guard mobile-first behavior by auditing cross-platform flows, checking Lite vs Pro differences, and verifying accessibility in high-trust fintech screens. This generates interaction notes and UX decision logs stored in the Drive hub.

What is the best way to document UX decisions for a premium frontend design system?

Document UX decisions by capturing flow audits, handoff notes, and canonical design rules in the Drive hub. This preserves the premium visual language, including glassmorphism and the Deep Ocean palette, across web and mobile implementations.

Do I need existing frontend screens to run a design review for OWFINANCE?

Yes, you need current frontend screens to review against canonical OWFINANCE design rules. Comparing screens against these guidelines produces a design brief and handoff notes for implementation.

Can I use this approach to check style consistency for glassmorphism and custom fonts?

Yes, you can check style consistency for glassmorphism, Outfit fonts, rounded panels, and the Deep Ocean palette. The design review process preserves this premium visual language across web and mobile cross-platform flows.

Why does my fintech UI design review fail to capture mobile-first responsiveness?

Design reviews fail when they lack canonical rules and cross-platform flow audits. Driving UI stewardship tasks ensures mobile-first responsiveness, accessibility, and clarity in high-trust fintech flows are properly evaluated.