Content
75%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body is an efficient, highly actionable reference of Expo Router rules and navigation code with a clear Expo-Go-first workflow. Its main weakness is progressive disclosure: the listed reference files do not exist on disk, so the well-organized pointers lead nowhere.
Suggestions
Provide the referenced files under references/ (animations.md, route-structure.md, tabs.md, etc.) so the signaled navigation actually resolves.
Add an explicit feedback loop to the run workflow (e.g. 'if Expo Go errors on a missing native module, switch to a custom build').
Move the full context-menu and route-layout code examples into their referenced files to keep SKILL.md a tighter overview.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly lean imperative bullet rules that assume Claude's competence ('expo-audio not expo-av', 'process.env.EXPO_OS not Platform.OS'), with minor over-explanation in the 'Running the App' prose that could be trimmed. | 4 / 5 |
Actionability | Concrete, mostly copy-paste-ready code for Link, context menus, modal/sheet presentation, and route layouts plus exact package names, with minor gaps (undefined handlers like handleSharePress, no full styling code example). | 4 / 5 |
Workflow Clarity | The 'Running the App' sequence is clearly ordered with a test checkpoint (try Expo Go, check features, custom build only when required), though it lacks an explicit validate-fix-retry feedback loop. | 4 / 5 |
Progressive Disclosure | A dedicated, well-signaled References section lists one-level-deep bundle files with descriptions and the body points to ./references/route-structure.md, but the references/ directory does not actually exist so navigation is broken and some inline navigation code could be split out. | 4 / 5 |
Total | 16 / 20 Passed |