Add expo-examples skill#84
Merged
Merged
Conversation
Skill for finding, inspecting, and scaffolding from the expo/examples repo (~70 single-concern with-* integration demos). Two modes: study an example for inspiration (read-only, non-destructive) and scaffold a new project via `npx create-expo --example`. Includes a categorized catalog reference; discovery and meta.json alias/deprecation checks are done with plain gh commands (no helper script). Bumps the Claude/Codex/Cursor plugin manifests to 1.3.0 (required by the plugin version-bump check for changes under plugins/expo/skills/). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Dogfooding with-stripe showed the integration spread across server routes, client provider, and config — leading to many per-file API calls. Steer to pulling the example locally (degit/sparse) once it's more than a couple of files. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
- Description: collapse 4 synonym triggers into the 2 real branches
(adapt-into-existing-app, scaffold-new) — 599->394 chars, less context load
- Step 3: add an exhaustive completion criterion (every dep/plugin/
permission/env var accounted for) to drive legwork over "looks wired up"
- Cut a no-op ("adapt imports rather than paste verbatim" is the default)
- Single source of truth: dedup the "never scaffold on top" warning and the
meta.json/deprecated rule to one home each
- Move the full-stack/showcase/starter enumeration out of SKILL.md into
catalog.md (progressive disclosure + co-location)
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
zvadaadam
pushed a commit
that referenced
this pull request
Jun 18, 2026
…simplify, proactive footer - Rename the skill `skill-feedback` → `expo-skill-feedback` (dir, frontmatter name, hooks.json path, all 15 footer pointers, README/AGENTS refs). Script filenames (skill-feedback.js/.sh) and the userAgent label stay. Clearer leading word that matches the "Expo Skill Feedback" footer heading. - Feedback can now target **Expo itself**, not just the skill: skill-feedback.js gains `--about skill|expo` (default skill) -> `properties.about`, so the team can separate framework issues from skill-guidance issues. Surfaced in the footer nudge, the skill's Submitting-feedback section, and the description. - Simplify references/telemetry.md (95 -> 50 lines): keep the event shape (the privacy receipt) + add `about`, condense the rest, and point to the scripts' own comments for the detach/Windows how (single source of truth). - Bump plugin manifests 1.3.0 -> 1.4.0 (main reached 1.3.0 via #84). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
zvadaadam
pushed a commit
that referenced
this pull request
Jun 18, 2026
- Resolved the plugin.json version conflict to 1.4.0 (main reached 1.3.0 via #84; this branch needs strictly-greater). - Gave the new expo-examples skill the same proactive Expo Skill Feedback footer (pointing to expo-skill-feedback) so every skill is consistent. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a new
expo-examplesskill so agents can leverage the officialexpo/examplesrepo — Expo's library ofwith-*integration demos — as version-matched references. Two modes: study an example for inspiration (read-only, non-destructive into an existing app) and scaffold a new project vianpx create-expo --example.What's actually in
expo/examples(verified by cloning + analyzing all 70)These are integrations, not apps — the framing the skill is built around:
ios//android/(all managed projects)App.js/tsx; only 11 use a multi-routeapp/dirwith-<library>, each built around one headline dependencyNuances the skill calls out: 8 are full-stack (Expo Router
+apiroutes — auth/payments/AI), a few are larger showcases (with-shadcn,with-router-tv,with-react-navigation), andblank/stickersmashare starters, not integrations.Design decisions
ghcommands (live list +meta.jsonfor aliases/deprecations); intent→example matching is left to the model rather than a brittle hardcoded synonym table.npx expo install, add only missing config plugins, never overwriteapp.json.app/api/routes) isn't missed.meta.jsonas source of truth for renamed (alias) and dead (deprecated) examples.Files
plugins/expo/skills/expo-examples/SKILL.mdplugins/expo/skills/expo-examples/references/catalog.md— categorized snapshot1.2.0 → 1.3.0(required by the version-bump check)Validation
claude plugin validate .and./plugins/expopassFuture
Name reserved as
expo-examples(mirrors the repo +--example); a futureexpo-templatesskill can cover larger UI app starters (create-expo-app --template), disambiguated via descriptions + cross-links.🤖 Generated with Claude Code