frontend-ui-ux

Redirect deprecated frontend UI/UX commands to $design and $visual-ralph.

Updated May 26, 2026
One-click install
npx skills add https://github.com/koasis89/ite-ai-agent --skill frontend-ui-ux-koasis89
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: frontend-ui-ux
Source: https://github.com/koasis89/ite-ai-agent/tree/main/skills/frontend-ui-ux
Command: npx skills add https://github.com/koasis89/ite-ai-agent --skill frontend-ui-ux-koasis89

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a deprecated compatibility layer for legacy frontend UI/UX tasks that are no longer recommended for new work.

Core Features & Use Cases

  • Compatibility Shim: Allows users to use deprecated commands for frontend UI/UX work.
  • Alternative Commands: Suggests using $design for product and design context, and $visual-ralph for visual implementation.
  • Use Case: For users who have existing scripts or workflows that rely on the deprecated frontend-ui-ux skill.

Quick Start

Use the frontend-ui-ux skill for legacy frontend UI/UX tasks, though it is recommended to switch to $design or $visual-ralph for new work.

Frequently Asked Questions about frontend-ui-ux

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

FAQPage Schema
What is a frontend UI/UX compatibility shim for legacy workflows?

A frontend UI/UX compatibility shim is a deprecated layer that redirects legacy commands to modern alternatives, allowing existing scripts to function without immediate updates.

How do I handle deprecated frontend UI/UX commands in my existing scripts?

To handle deprecated frontend UI/UX commands, use this legacy compatibility layer which intercepts them and suggests transitioning to updated commands like $design or $visual-ralph.

Should I use the frontend-ui-ux skill for new UI/UX design work?

You should not use the frontend-ui-ux skill for new UI/UX design work. It is strictly a compatibility shim for legacy workflows, directing users to $design or $visual-ralph instead.

What are the modern alternatives to deprecated frontend UI/UX commands?

The modern alternatives to deprecated frontend UI/UX commands are $design for product and design context, and $visual-ralph for visual implementation tasks.

Why does my legacy frontend UI/UX workflow recommend switching commands?

Your legacy frontend UI/UX workflow recommends switching commands because the current skill is a deprecated compatibility layer, actively redirecting users to more modern alternatives for better support.