react-native-architecture
Build production React Native apps with Expo, navigation, native modules, offline sync, and cross-platform patterns. Use when developing mobile apps, implementing native integrations, or architecting React Native projects.
79
71%
Does it follow best practices?
Impact
91%
1.13xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/frontend-mobile-development/skills/react-native-architecture/SKILL.mdQuality
Discovery
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.
This is a strong skill description that clearly communicates its scope (React Native/Expo mobile development), lists specific capabilities (navigation, native modules, offline sync, cross-platform patterns), and includes an explicit 'Use when...' clause with natural trigger terms. It is concise, uses third-person voice, and is distinctive enough to avoid conflicts with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete capabilities: 'Build production React Native apps with Expo, navigation, native modules, offline sync, and cross-platform patterns.' These are distinct, concrete technical areas rather than vague abstractions. | 3 / 3 |
Completeness | Clearly answers both 'what' (build production React Native apps with Expo, navigation, native modules, offline sync, cross-platform patterns) and 'when' (Use when developing mobile apps, implementing native integrations, or architecting React Native projects) with an explicit 'Use when...' clause. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'React Native', 'Expo', 'mobile apps', 'native integrations', 'navigation', 'offline sync', 'cross-platform'. These cover the primary terms a developer would use when seeking help with mobile development in this stack. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to React Native/Expo mobile development, which is a distinct niche. The combination of 'React Native', 'Expo', 'native modules', and 'mobile apps' makes it unlikely to conflict with web development, backend, or other frontend skills. | 3 / 3 |
Total | 12 / 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 code examples covering a broad range of React Native/Expo patterns, which is its primary strength. However, it is far too verbose and monolithic — it reads like a comprehensive tutorial rather than a concise skill reference, explaining many patterns Claude already knows well. The lack of progressive disclosure (no external file references) and missing validation checkpoints in workflows significantly reduce its effectiveness as a SKILL.md file.
Suggestions
Split the six detailed patterns into separate referenced files (e.g., NAVIGATION.md, AUTH.md, OFFLINE.md, NATIVE_MODULES.md) and keep only a brief summary with links in SKILL.md
Remove or drastically condense patterns that cover well-known React Native concepts (auth context, React Query setup, haptics wrappers) — focus only on project-specific conventions or non-obvious configurations
Add validation checkpoints to the Quick Start and EAS Build workflows (e.g., 'Run npx expo start to verify setup before proceeding', 'Verify build succeeded with eas build:list')
Remove the 'When to Use This Skill' and comparison table sections — Claude can infer when to apply React Native patterns without being told
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~400+ lines, with extensive code examples that cover well-known patterns (React Query setup, auth context, haptics wrappers) that Claude already knows. The comparison table, 'When to Use This Skill' section, and many patterns are standard React Native knowledge that don't need this level of detail. Much of this could be condensed or split into referenced files. | 1 / 3 |
Actionability | The skill provides fully executable, copy-paste ready code examples throughout — from project setup commands to complete component implementations, EAS build configurations, and specific library usage patterns. Every pattern includes concrete, runnable TypeScript code. | 3 / 3 |
Workflow Clarity | The EAS Build section has a clear sequence of commands, and the Quick Start provides ordered setup steps. However, there are no validation checkpoints — no steps to verify the project builds successfully after setup, no error recovery guidance for failed builds, and no verification steps between the various configuration stages. | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of content with no references to external files. All six patterns, build configuration, and best practices are inlined in a single massive document. Content like the auth flow, offline-first setup, native module integration, and performance patterns should each be in separate referenced files with a concise overview here. | 1 / 3 |
Total | 7 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (667 lines); consider splitting into references/ and linking | Warning |
Total | 10 / 11 Passed | |
- Repository
- wshobson/agents
- Commit
27a7ed9
- 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.