Apply this skill when you need to:
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionux-principlesExecute the skills CLI command in your project's root directory to begin installation:
Fetches ux-principles from manutej/luxor-claude-marketplace and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate ux-principles. Access via /ux-principles in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
49
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
49
stars
Apply this skill when you need to:
User-centered design is a framework that places users at the center of the design process through iterative cycles of research, design, testing, and refinement.
Four Fundamental Principles:
Early Focus on Users and Tasks
Empirical Measurement
Iterative Design
Integrated Design
Design thinking is a human-centered approach to innovation that integrates user needs, technological possibilities, and business viability.
Five-Stage Process:
Key Principles:
Jakob Nielsen's heuristics are foundational principles for evaluating interface usability.
Principle: The system should always keep users informed about what is going on through appropriate feedback within reasonable time.
Guidelines:
Examples:
Principle: The system should speak the users' language, using words, phrases, and concepts familiar to them rather than system-oriented terms.
Guidelines:
Examples:
Principle: Users often choose system functions by mistake and need a clearly marked "emergency exit" to leave unwanted states without going through an extended dialogue.
Guidelines:
Examples:
Principle: Users should not have to wonder whether different words, situations, or actions mean the same thing. Follow platform and industry conventions.
Guidelines:
Examples:
Principle: Even better than good error messages is careful design that prevents problems from occurring in the first place.
Guidelines:
Examples:
Principle: Minimize the user's memory load by making objects, actions, and options visible. Users should not have to remember information from one part of the dialogue to another.
Guidelines:
Examples:
Principle: Accelerators—unseen by novice users—may speed up interaction for expert users, allowing the system to cater to both inexperienced and experienced users.
Guidelines:
Examples:
Principle: Dialogues should not contain information that is irrelevant or rarely needed. Every extra unit of information competes with relevant units and diminishes their visibility.
Guidelines:
Examples:
Principle: Error messages should be expressed in plain language, precisely indicate the problem, and constructively suggest a solution.
Guidelines:
Examples:
Principle: Even though it's better if the system can be used without documentation, it may be necessary to provide help. Such information should be easy to search, focused on the user's task, and list concrete steps.
Guidelines:
Examples:
Gestalt principles describe how humans perceive visual elements as organized patterns rather than separate components.
Key Principles:
Proximity: Elements close together are perceived as related
Similarity: Similar elements are perceived as part of a group
Continuity: Elements arranged on a line or curve are perceived as related
Closure: Humans complete incomplete shapes in their minds
Figure/Ground: Elements are perceived as either foreground or background
Cognitive load refers to the amount of mental effort required to use an interface. Reducing cognitive load improves usability and user satisfaction.
Types of Cognitive Load:
Intrinsic Load: Inherent complexity of the task
Extraneous Load: Unnecessary mental effort from poor design
Germane Load: Effort required to learn and internalize patterns
Strategies to Reduce Cognitive Load:
A mental model is a user's internal representation of how something works. Effective UX design aligns with user mental models.
Understanding Mental Models:
Designing for Mental Models:
Research User Expectations
Match or Teach
Test Assumptions
Common Mental Model Mismatches:
Affordances: Properties of an object that show what actions can be performed with it.
Signifiers: Cues that communicate where action should take place.
Design Implications:
Principle: The time to acquire a target is a function of the distance to and size of the target.
Formula: T = a + b × log₂(D/W + 1)
UI Design Applications:
Large Targets: Make clickable elements bigger
Proximity: Place related items close together
Edge Cases: Screen edges are easy targets (infinite width)
Context Menus: Appear at cursor location
Principle: The time it takes to make a decision increases logarithmically with the number of choices.
Formula: T = b × log₂(n + 1)
Design Implications:
Reduce Options: Show only necessary choices
Categorize: Group options into logical categories
Prioritize: Highlight recommended or popular options
Context: Show relevant options for current task
Principle: The average person can hold 7 (±2) items in working memory.
Design Applications:
Chunk Information: Group content into 5-9 items
Break Down Complex Tasks: Divide into steps
Use Visual Aids: Reduce memory requirements
Provide References: Make information available
Qualitative Methods: Explore motivations, behaviors, and mental models
Quantitative Methods: Measure behaviors and validate hypotheses
Purpose: Deep understanding of user needs, goals, behaviors, and pain points.
Best Practices:
Preparation
During Interviews
Question Types
Analysis
Purpose: Gather quantitative data from larger samples to measure attitudes, behaviors, and preferences.
Design Principles:
Question Design
Survey Structure
Question Types
Sample Size
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
asyrafhussin/agent-skills
kylezantos/design-motion-principles
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
pproenca/dot-skills
ux-principles has been reliable in day-to-day use. Documentation quality is above average for community skills.
We added ux-principles from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
ux-principles reduced setup friction for our internal harness; good balance of opinion and flexibility.
Solid pick for teams standardizing on skills: ux-principles is focused, and the summary matches what you get after install.
ux-principles has been reliable in day-to-day use. Documentation quality is above average for community skills.
I recommend ux-principles for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
ux-principles reduced setup friction for our internal harness; good balance of opinion and flexibility.
ux-principles fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
ux-principles has been reliable in day-to-day use. Documentation quality is above average for community skills.
ux-principles fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 54