SkillsAdd

smithery/joseph-vj

ux-simplicity

Ensure UI/UX stays simple and mobile-first for non-technical users. Use when creating or modifying any UI components, layouts, forms, navigation, or user-facing text. Prevents complex designs and enforces permission-based changes.

Installation

$ npx skills add smithery/joseph-vj --skill ux-simplicity
View on skills.sh ↗ Website ↗

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

vercel-react-native-skills Shared topics
vercel-labs/agent-skills 205.5K installs
More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,576 B
  • docs SUMMARY.md 251 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

UX Simplicity Guardian

Purpose

Ensure UI/UX remains simple and user-friendly for non-technical users

Reference Documentation

  • docs/business/FREEFORBUYERS.md - UX philosophy & buyer experience
  • docs/testing/AITESTINGRESULTS.md - User testing feedback
  • docs/testing/QUICKTESTGUIDE.md - Testing procedures
  • src/components/ - UI component library

AI Responsibilities

  • 👥 Keep UI Simple - No complex, technical, or confusing designs
  • 📱 Mobile-First - All features must work perfectly on mobile
  • 🎯 User-Friendly - Anyone should understand without instructions
  • 🚀 Prevent Complexity - Stop overly technical UI from being added
  • 💬 Clear Language - No jargon, simple words only

STRICT RULES (NEVER VIOLATE)

🔴 RULE 0: UNDERSTAND USER INTENT BEFORE ANY UX CHANGE

  • What is user asking to change? - Be specific
  • Why do they want this change? - Understand the problem they're solving
  • Is this a design change or content change? - Content (text) is safer than design (layout)
  • Will this confuse users? - Consider mobile users and non-technical users
  • Ask permission for design changes - Always confirm before modifying layouts
  1. ❌ NEVER change existing design without explicit permission
  2. ⚠️ ALWAYS ask before modifying:

- Layout/structure - Color schemes - Navigation flow - Button placements - Form designs - Component library choices

What AI Can Do

  • ✅ Suggest simpler alternatives to complex UI
  • ✅ Point out confusing user flows
  • ✅ Recommend mobile-friendly improvements
  • ✅ Alert if design might push users away
  • ✅ Suggest better wording/labels

Validation Checklist

  • Is this simple enough for a non-technical user?
  • Works on mobile (320px width)?
  • No technical jargon in UI text?
  • Clear call-to-action buttons?
  • Forms are easy to fill?
  • Error messages are helpful, not technical?
  • Loading states are clear?
  • Success/failure feedback is obvious?

Mobile-First Standards

  • ✅ Touch-friendly buttons (min 44x44px)
  • ✅ Readable text (min 16px font size)
  • ✅ No tiny links or buttons
  • ✅ Forms work with mobile keyboards
  • ✅ Images load fast on 3G/4G
  • ✅ No horizontal scrolling