ui-mobile
Mobile UI patterns - React Native, iOS/Android, touch targets
35
32%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/ui-mobile/SKILL.mdQuality
Discovery
22%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is essentially a comma-separated list of keywords with no verbs, no concrete actions, and no 'Use when...' guidance. While the domain (mobile UI) is identifiable, the lack of specificity about what the skill does and when to invoke it makes it poorly suited for skill selection among a large set of options.
Suggestions
Add concrete action verbs describing what the skill does, e.g., 'Generates mobile UI components, implements touch-friendly navigation patterns, and adapts layouts for iOS and Android platforms.'
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about mobile app UI design, React Native components, touch target sizing, or platform-specific mobile patterns.'
Expand trigger terms to include common user phrases like 'mobile app design', 'mobile navigation', 'responsive mobile layout', 'swipe gestures', 'bottom sheet', 'tab bar', etc.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description lists technology names and a concept ('touch targets') but does not describe any concrete actions. There are no verbs indicating what the skill actually does — it reads more like a tag list than a capability description. | 1 / 3 |
Completeness | The description partially hints at 'what' (mobile UI patterns) but is extremely vague, and there is no 'when' clause or explicit trigger guidance at all. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and the 'what' is also weak, so this scores a 1. | 1 / 3 |
Trigger Term Quality | It includes some relevant keywords users might say ('React Native', 'iOS', 'Android', 'touch targets', 'Mobile UI'), but misses common variations like 'mobile app design', 'responsive layout', 'navigation patterns', 'mobile components', or 'swipe gestures'. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'Mobile UI patterns' and 'React Native' provides some niche specificity, but the vagueness could cause overlap with general UI/UX skills, React skills, or iOS/Android development skills. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides highly actionable, executable React Native code patterns with good coverage of accessibility, platform differences, and common components. However, it is severely bloated with significant content repetition (touch targets, accessibility labels, colors all appear twice), explains concepts Claude already knows, and dumps everything into a single monolithic file that would benefit greatly from progressive disclosure via separate reference files.
Suggestions
Eliminate duplicate content: touch targets, accessibility labels, and color definitions each appear in both the MANDATORY section and later sections — consolidate to a single location each.
Split into multiple files: move detailed component patterns (Cards, Buttons, Inputs, Lists, Navigation) into a COMPONENTS.md, animation patterns into ANIMATIONS.md, and keep SKILL.md as a concise overview with the mandatory rules and links to detailed references.
Remove explanations of concepts Claude already knows, such as what semantic colors are, how Platform.select works, or that mobile has no hover states — focus only on the specific values and patterns to use.
Add a brief workflow section describing the recommended order of applying these patterns when building a new screen (e.g., safe areas → layout → components → accessibility audit) with a validation checklist.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~600+ lines with massive repetition. Touch target rules are defined in the MANDATORY section and then repeated nearly identically in the 'Touch Targets' section. Accessibility labels appear twice. Color definitions overlap between the MANDATORY section and the Color System section. Much of this (semantic colors, typography scales, platform differences) is knowledge Claude already has. | 1 / 3 |
Actionability | The skill provides fully executable, copy-paste-ready TypeScript/TSX code throughout. Every pattern includes complete StyleSheet definitions, proper imports, and concrete component implementations with specific values rather than pseudocode. | 3 / 3 |
Workflow Clarity | This is primarily a reference/pattern skill rather than a multi-step workflow, so explicit sequencing is less critical. However, the MANDATORY section at the top establishes a clear checklist of requirements, and the 'Premium Feel Checklist' at the end provides a verification step. But there's no clear workflow for how to apply these patterns (e.g., 'start with safe areas, then layout, then components') and no validation/testing guidance. | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of content with no references to external files. At 600+ lines, much of the content (full component patterns, animation examples, loading states) should be split into separate reference files. There's no layered structure — everything is dumped into a single file with no navigation aids beyond section headers. | 1 / 3 |
Total | 7 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (955 lines); consider splitting into references/ and linking | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Repository
- alinaqi/claude-bootstrap
- Commit
65efb33
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.