ux-guidelines

Enforce semantic UX primitives in shell outputs and help functions.

Updated May 31, 2025

Search Tags:#refactoring #zsh #bash #shell #user-experience #ux-guidelines #ux_lib

Ready to run

npx skills add https://github.com/dEitY719/dotfiles --skill ux-guidelines

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ux-guidelines
Source: https://github.com/dEitY719/dotfiles/tree/main/claude/skills/ux-guidelines
Command: npx skills add https://github.com/dEitY719/dotfiles --skill ux-guidelines

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enforce consistent UX across shell functions and help text by applying semantic UX primitives and safe loading of the UX library.

Core Features & Use Cases

Standardize output with ux_header, ux_section, ux_bullet, and other UX primitives.
Ensure cross-shell compatibility by using a safe conditional loader for ux_lib and adhering to UX foundation principles.
Support both individual function refactoring and bulk UX compliance reviews across shell-common components.

Quick Start

Refactor a target function to use the semantic UX helpers and ensure ux_lib is loaded when needed.

Frequently Asked Questions about ux-guidelines

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

FAQPage Schema

How do I enforce semantic UX in shell outputs across bash and zsh functions?▼

To enforce semantic UX in shell outputs, refactor target functions to use UX primitives like ux_header and ux_bullet, and load ux_lib conditionally to validate outputs against UX Foundation rules.

What are semantic UX primitives for shell script formatting?▼

Semantic UX primitives are standardized output helpers like ux_header, ux_section, and ux_bullet that enforce consistent user experience formatting across shell-common components and help text.

Can I conduct a bulk UX compliance review across shell-common components?▼

Yes, you can conduct bulk UX compliance reviews across shell-common components by applying UX_GUIDELINES and validating outputs against the UX Foundation rules to ensure cross-shell compatibility.

Do I need to load ux_lib conditionally when refactoring shell functions?▼

Yes, you need to use a safe conditional loader for ux_lib when refactoring shell functions to ensure the library is loaded only when needed and adheres to UX foundation principles.

What is the best way to standardize help text formatting in shell scripts?▼

The best way to standardize help text formatting is to refactor individual functions using semantic UX primitives and ensure cross-shell compatibility by adhering to UX foundation principles with a safe conditional loader.

Why does my shell function output lack cross-shell compatibility?▼

Shell function output lacks cross-shell compatibility when it does not use a safe conditional loader for ux_lib or fails to adhere to UX foundation principles during refactoring.