react-native-best-practices

Provides React Native performance optimization guidelines for FPS, TTI, bundle size, memory leaks, re-renders, and animations. Applies to tasks involving Hermes optimization, JS thread blocking, bridge overhead, FlashList, native modules, or debugging jank and frame drops.

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

The canonical home for this skill is react-native-best-practices in callstackincubator/agent-skills

Quality

Content

87%

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

The body is a well-organized, token-efficient overview that routes to a real, well-structured reference bundle with strong actionability. Its main gap is the absence of explicit validation/feedback checkpoints in the optimization workflow.

Suggestions

Add an explicit measure→fix→re-measure feedback loop (e.g., capture baseline FPS/TTI, apply a fix, then re-run the measurement to confirm improvement) so the workflow includes validation checkpoints.

For the destructive/risky entries (e.g., R8 shrinking, Hermes mmap config changes, 16KB alignment fixes), note a verification step (build/run the app, check for regressions) to elevate workflow_clarity.

Surface a one-line 'how to verify a fix worked' note near the Problem→Skill Mapping so reviewers can confirm a change actually resolved the reported jank or size issue.

Dimension	Reasoning	Score
Conciseness	Lean, table-driven overview that assumes Claude's competence — no padding about what React Native or a FlatList is, and every section (Quick Reference, Problem→Skill Mapping) earns its tokens.	3 / 3
Actionability	Provides copy-paste-ready executable commands (the `npx react-native bundle` and `source-map-explorer` snippets) and specific library recommendations (FlashList, Jotai/Zustand, react-native-screens), matching the 'fully executable' anchor.	3 / 3
Workflow Clarity	The priority-ordered table and Problem→Skill mapping give a clear routing sequence, but there is no explicit measure→fix→re-measure validation checkpoint to confirm an optimization actually improved FPS/TTI, so it sits at the 'sequence present but checkpoints missing' anchor.	2 / 3
Progressive Disclosure	Clear overview pointing to 28 real one-level-deep reference files, organized by category with impact ratings and a Problem→Skill map for navigation; images correctly stored under references/images/ — well-signaled and easy to discover.	3 / 3
	Total	11 / 12 Passed

Description

100%

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 concise, specific, and clearly distinguishes the skill's niche with explicit 'what' and 'when' guidance. It uses natural trigger terms and third-person voice without padding or over-claims.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete optimization areas ("FPS, TTI, bundle size, memory leaks, re-renders, and animations") plus specific tools/concepts (Hermes, FlashList, native modules), matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	Explicitly answers both 'what' ("Provides React Native performance optimization guidelines for...") and 'when' ("Applies to tasks involving..."), the latter being an explicit trigger clause rather than an implication.	3 / 3
Trigger Term Quality	Includes natural terms users actually say — "jank and frame drops", "re-renders", "bundle size", "memory leaks" — with good coverage of common phrasings rather than only technical jargon.	3 / 3
Distinctiveness Conflict Risk	Clear niche (React Native performance) with distinctive triggers (Hermes optimization, JS thread blocking, FlashList) unlikely to fire for unrelated skills; uses third person ("Provides", "Applies") with no voice penalty.	3 / 3
	Total	12 / 12 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
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: freekmurze/dotfiles
Path: config/claude/skills/react-native-best-practices/SKILL.md
Commit: d0073bc

Reviewed: about 10 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.