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.
A well-structured guidelines skill: terse, opinionated rules with executable code examples and a genuinely useful Expo Go vs. custom-build decision workflow. The main improvements are de-duplicating safe-area rules scattered across sections, tightening a few vague bullets, and cross-linking the relevant reference file from each topical section.
Suggestions
Consolidate the repeated `contentInsetAdjustmentBehavior="automatic"` / safe-area rules (currently in Responsiveness, Behavior, and General Styling) into one place.
Link each topical section to its matching reference file in place (e.g. Navigation → tabs.md, toolbar-and-headers.md, form-sheet.md; Styling → gradients.md, visual-effects.md) so references are surfaced where needed, not only in the top-level tree.
Replace vague directives ("Follow Apple Human Interface Guidelines", "Test your app thoroughly", "Be cautious of unterminated strings") with concrete, checkable instructions or a short example.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is terse directive bullets with essentially no explanation of concepts Claude already knows ("`expo-audio` not `expo-av`", "`process.env.EXPO_OS` not `Platform.OS`"). However, rules repeat across sections — `contentInsetAdjustmentBehavior="automatic"` appears in Responsiveness, Behavior, and General Styling — so it is not the lean every-token-earns-its-place level. | 4 / 5 |
Actionability | Mostly executable guidance: complete snippets for boxShadow, Link/context menus, formSheet options, and full `_layout.tsx` tab/stack layouts, plus concrete library substitutions. Minor gaps keep it below fully copy-paste-ready coverage: bullets like "Follow Apple Human Interface Guidelines" and "Be cautious of unterminated strings" are abstract, and Code Style/Behavior sections have no examples. | 4 / 5 |
Workflow Clarity | The single real workflow (Running the App) is a clearly ordered triage: start with Expo Go → test features thoroughly → create custom builds only when required, with an explicit list of when custom builds are needed. It lacks an explicit validation/retry checkpoint ("Test your app thoroughly" is vague), so it matches the clear-sequence-with-minor-validation-gaps anchor rather than the validate→fix→retry level. | 4 / 5 |
Progressive Disclosure | Scored against the actual bundle: all 15 listed reference files exist, are one level deep (no nested references), and the annotated file tree at the top makes them easy to discover, while the body stays overview-level. The gap is that sections rarely link their own references in place — e.g. Navigation never points to tabs.md, toolbar-and-headers.md, or form-sheet.md; only Routes links route-structure.md — so references are mostly, not fully, signaled. | 4 / 5 |
Total | 16 / 20 Passed |