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.
76
71%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./tests/ext_conformance/artifacts/agents-wshobson/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 main 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, production-quality code examples covering a broad range of React Native/Expo patterns, which is its primary strength. However, it is excessively verbose — dumping hundreds of lines of boilerplate code that Claude can generate from brief instructions — and lacks any progressive disclosure structure, making it a monolithic reference that wastes context window. Workflow clarity is adequate but missing validation checkpoints for build and deployment steps.
Suggestions
Drastically reduce inline code to key patterns and non-obvious configurations only (e.g., the offline-first React Query setup with NetInfo is valuable, but the full Button component with StyleSheet is standard knowledge). Aim for <150 lines.
Split detailed patterns into separate referenced files (e.g., NAVIGATION.md, OFFLINE.md, NATIVE_MODULES.md) and keep SKILL.md as a concise overview with links.
Add validation checkpoints to workflows: verify project builds after setup (`npx expo start`), verify EAS build succeeds before submitting, include common error troubleshooting.
Remove the 'When to Use This Skill' section, the Expo vs Bare RN comparison table, and the Do's/Don'ts list — these explain concepts Claude already knows well.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~500+ lines. Includes extensive boilerplate code that Claude already knows (React context patterns, basic StyleSheet usage, standard React Query setup). The comparison table, 'When to Use This Skill' section, and Do's/Don'ts list explain concepts Claude is well-versed in. Much of this could be condensed to key patterns and project-specific conventions. | 1 / 3 |
Actionability | Provides fully executable, copy-paste ready code examples throughout — from project setup commands to complete component implementations, EAS build configuration, and authentication flows. Code is TypeScript with proper imports and realistic patterns. | 3 / 3 |
Workflow Clarity | The EAS Build section has clear sequential commands, and the Quick Start provides a logical setup sequence. However, there are no validation checkpoints — no steps to verify the project builds successfully after setup, no testing/verification steps after EAS builds, and no error recovery guidance for common build failures. | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of text with all content inline. Six full pattern implementations, each with extensive code, are all in one file. The external links at the bottom are just general documentation references, not structured companion files. Content like the auth flow, offline-first setup, and native modules should be split into separate referenced files. | 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 (674 lines); consider splitting into references/ and linking | Warning |
Total | 10 / 11 Passed | |
- Repository
- Dicklesworthstone/pi_agent_rust
- Commit
47823e3
- 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.