mobile-ux-optimizer 1.0.0 Immutable snapshotLatest
Pinned to commit 5bd4f168edf7c18a8303cbfde20708ff62aabc4d, captured .
Download 1.0.0 source archive Choose something to compare with View commit on GitHub
More actions and subscriptions
Current package description (not historical)
Use this agent when you need to optimize UI/UX components or interfaces for mobile-first experiences, analyze existing design themes, or ensure mobile usability standards are met. Examples: <example>Context: User has created a desktop-focused component and needs it optimized for mobile. user: 'I've built this navigation component but it's not working well on mobile devices' assistant: 'Let me use the mobile-ux-optimizer agent to analyze and improve this component for mobile-first experience' <commentary>The user needs mobile optimization expertise, so use the mobile-ux-optimizer agent to provide specific mobile UX improvements.</commentary></example> <example>Context: User is implementing a new feature and wants to ensure it follows the existing design theme. user: 'I'm adding a new form component to the app, can you help make sure it matches our design system?' assistant: 'I'll use the mobile-ux-optimizer agent to ensure this form component aligns with your existing theme and mobile-…
Install
This version is listed in the verified marketplace awesome-claude-code-plugins (repository ccplugins/awesome-claude-code-plugins). Run these in Claude Code, in order:
- Add the marketplace
/plugin marketplace add ccplugins/awesome-claude-code-plugins - Install the plugin
/plugin install mobile-ux-optimizer@awesome-claude-code-plugins
These commands install the marketplace's current upstream state, not the pinned commit snapshot on this page; the two can differ.
Contents 1
Agent1
-
mobile-ux-optimizer
plugins/mobile-ux-optimizer/agents/mobile-ux-optimizer.mdPermalink
Nothing matches.
Dependencies, compatibility and skill declarations
Recorded dependencies 0
No dependency requirements were recorded from plugin.json or marketplace entries. Only manifest fields saved with the snapshot are shown here; dependency declarations in other files are outside the current collection scope.
Recorded compatibility
No compatibility requirement was recorded for this snapshot from plugin.json or a marketplace entry. Only manifest fields saved with the snapshot are shown here. Declarations in a skill's SKILL.md header are collected separately and, when present, shown on their own under “Skill file declarations”; they never overwrite or fill in this value.