Content
65%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, actionable Expo UI guide with concrete code and clear rules, but its single workflow lacks explicit validation checkpoints and its otherwise well-structured references point to bundle files that are not actually present.
Suggestions
Ship the referenced bundle files (animations.md, controls.md, route-structure.md, etc.) so the progressive-disclosure navigation actually resolves, or remove references to files that are not provided.
Add an explicit validation/feedback step to the "Running the App" workflow (e.g. "If a required feature is unsupported in Expo Go, then create a custom build"), making the checkpoint and error-recovery path explicit.
Pair the styling and library-preference rules with a short inline code example so every actionable rule is concrete rather than declarative-only.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly lean directive bullets ("Never use…", "Always use…", "Prefer…") with short code examples and assumes Claude's competence; the "Running the App" decision guidance earns its place, with only minor trim opportunities. | 4 / 5 |
Actionability | Provides concrete copy-paste code for Link, Stack.Screen, context menus, link previews, modals, sheets, and tab layouts plus specific commands ("npx expo start") and exact library/prop names; minor gaps exist where styling rules lack accompanying example code. | 4 / 5 |
Workflow Clarity | The "Running the App" section gives a clear decision sequence (Expo Go → test → custom build only if needed) with an implicit checkpoint ("Check if features work"), but there is no explicit validation or error-recovery feedback loop, and most of the document is reference rules rather than a workflow. | 3 / 5 |
Progressive Disclosure | The structural design is good — an overview with a well-signaled one-level-deep References block (per-file descriptions) and an inline pointer to "./references/route-structure.md" — but the references/ directory does not exist in the bundle, so the signaled references are not real files and navigation breaks. | 3 / 5 |
Total | 14 / 20 Passed |