react-native-patterns

React Native and Expo app patterns — Expo Router navigation, state separation (server/client/route/form), TanStack Query data fetching with Zod, performant lists, NativeWind/StyleSheet styling, native APIs, and secure storage. Use when building or editing React Native / Expo screens, components, navigation, or data layers.

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

82%Weight 40%Scale 1-5

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

A well-structured, highly actionable patterns skill with executable examples and clear organization. The main opportunities are trimming the meta-disclaimer prose and optionally splitting detailed full-screen/form examples into reference files for stronger progressive disclosure.

Suggestions

Trim the meta-disclaimer paragraphs (the 'Libraries named below… shown for illustration' and 'do NOT assume the browser DOM' lines) to tighten conciseness without losing the disambiguation value.

Consider moving the full OrdersScreen and RHF+Zod form examples into a reference file under references/ and linking from SKILL.md to deepen progressive disclosure and keep the overview leaner.

Add an explicit validate→fix→retry note for the route-param and data-fetching patterns to push workflow clarity toward a full feedback-loop structure.

Dimension	Reasoning	Score
Conciseness	Lean and assumes Claude's competence — it does not explain what React Native or the libraries are — but the meta-disclaimer paragraphs ('Libraries named below… shown for illustration', 'do NOT assume the browser DOM') could be trimmed slightly.	4 / 5
Actionability	Provides multiple complete, copy-paste-ready examples (route param validation with Zod, useQuery/useMutation, FlatList, a useCurrentLocation hook, SecureStore, a full OrdersScreen, and an RHF+Zod form) that cover the common RN cases.	5 / 5
Workflow Clarity	The full-screen example sequences route validation → query → loading/error/empty rendering with embedded validation checkpoints, and sections are well organized, but there is no explicit validate→fix→retry feedback loop.	4 / 5
Progressive Disclosure	Well-organized with clear section headers and only one-level-deep, clearly signaled references (ruleset, Related Skills) with no nested refs, though all ~320 lines live inline in SKILL.md with no bundle files to externalize detailed examples.	4 / 5
	Total	17 / 20 Passed

Description

92%Weight 40%Scale 1-5

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

A strong, specific description that clearly states both capabilities and activation triggers with minimal conflict risk. The only gap is trigger-term breadth — adding synonyms like 'mobile app' and relevant file extensions would round it out.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities — 'Expo Router navigation, state separation (server/client/route/form), TanStack Query data fetching with Zod, performant lists, NativeWind/StyleSheet styling, native APIs, and secure storage' — giving comprehensive coverage of concrete actions rather than vague language.	5 / 5
Completeness	Explicitly answers both 'what' (the enumerated pattern list) and 'when' ('Use when building or editing React Native / Expo screens, components, navigation, or data layers') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural terms a user would say are present ('React Native', 'Expo', 'screens', 'components', 'navigation', 'data layers'), but synonyms like 'mobile app' and file extensions are missing, so it falls just short of comprehensive coverage.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear React Native/Expo mobile niche distinct from web/frontend skills, and the body explicitly excludes DOM patterns, yielding minimal conflict risk with other skills.	5 / 5
	Total	19 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: affaan-m/ECC
Path: skills/react-native-patterns/SKILL.md
Commit: d8409a4

Reviewed: 1 day 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.