ui-mobile

Mobile UI patterns - React Native, iOS/Android, touch targets

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

65%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill is highly actionable with extensive executable React Native code, but it is a long, redundant, monolithic reference that would benefit from de-duplication and splitting detail into separate reference files.

Suggestions

De-duplicate the body: touch targets and accessibility labels are each covered twice — consolidate into a single canonical section.

Move the detailed reference material (component patterns, typography/color systems, navigation) into separate files under references/ with clearly signaled links, leaving SKILL.md as a concise overview to improve progressive_disclosure and conciseness.

Add an explicit build/review workflow with verification checkpoints (e.g., 'apply pattern -> verify 44pt target & 4.5:1 contrast -> check off Premium Feel Checklist') to lift workflow_clarity.

Dimension	Reasoning	Score
Conciseness	The ~940-line body is mostly concrete code rather than prose, but it is heavily redundant — touch targets appear in 'MANDATORY: Mobile Accessibility Standards' and again in 'Touch Targets', and accessibility labels appear in both sections — so it could be tightened substantially rather than reaching the 'lean, every token earns its place' anchor.	2 / 3
Actionability	It provides fully executable, copy-paste-ready React Native code throughout (StyleSheet definitions, Pressable patterns, Platform.select, Animated/Reanimated usage) with specific values, matching the 'fully executable, copy-paste ready' anchor.	3 / 3
Workflow Clarity	Content is well-organized by topic and includes a 'Premium Feel Checklist', but it is a patterns catalog rather than a sequenced multi-step workflow with explicit validation checkpoints, so it sits at the 'steps present but checkpoints missing/implicit' level rather than a full feedback-loop workflow.	2 / 3
Progressive Disclosure	The body is well-sectioned but monolithic — no bundle files exist and all reference material (component patterns, color/typography systems, navigation) is inline rather than split into clearly signaled one-level-deep references, matching the 'content that should be separate is inline' anchor.	2 / 3
	Total	9 / 12 Passed

Description

72%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific and distinctive with strong natural trigger terms, but it omits an explicit 'Use when...' clause in the description field and lists topics rather than concrete actions.

Suggestions

Add an explicit 'Use when...' clause to the description (e.g., 'Use when building or reviewing React Native, iOS, or Android UI components') so completeness reaches 3.

Reframe the topic list as concrete actions (e.g., 'Build and style mobile UI components, enforce 44pt touch targets, and apply platform-specific patterns') to lift specificity.

Keep the third-person, concise phrasing — it already avoids fluff and voice penalties.

Dimension	Reasoning	Score
Specificity	The description names the domain and concrete sub-areas ('React Native, iOS/Android, touch targets') but uses noun phrases rather than listing concrete actions/verbs, so it does not reach the 'multiple specific concrete actions' anchor.	2 / 3
Completeness	It clearly states what the skill covers, but the description field itself has no 'Use when...' trigger clause (the trigger lives in a separate when-to-use field), so completeness is capped at 2 per the rubric guideline.	2 / 3
Trigger Term Quality	Terms like 'Mobile UI', 'React Native', 'iOS/Android', and 'touch targets' are natural keywords a user would say when they need this skill, giving good coverage.	3 / 3
Distinctiveness Conflict Risk	'Mobile UI patterns - React Native, iOS/Android, touch targets' carves a clear niche with distinct triggers that are unlikely to fire for non-mobile skills.	3 / 3
	Total	10 / 12 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 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	14 / 16 Passed

Repository: alinaqi/claude-bootstrap
Commit: 9dacc46

Reviewed: about 5 hours ago

Table of Contents

Discovery Implementation Validation

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.