facebook relay
OFFICIALLABSCO SUMMARY
relay-best-practices covers idiomatic use of useFragment, useLazyLoadQuery, usePreloadedQuery, useMutation, and usePaginationFragment, plus the anti-patterns around them, and is written to trigger whenever an agent sees those hooks or a graphql template literal in a diff. relay-performance is its companion for speed — query placement, @defer, fetch policies, cache garbage collection, fragment granularity — while relay-e2e-test covers a separate, markdown-driven end-to-end test format specific to this repository, with its own fixture syntax and interaction DSL.
All three assume an existing Relay and GraphQL codebase; none of them explain what Relay is or help set it up from nothing, and for that the README points at relay.dev's own introduction docs instead. If your stack does not already import react-relay, none of the three will have reason to trigger.
READ THE FULL ANALYSIS
One of the three is unverified. Our dependency check could not confirm what one of these skills needs to run — its own material does not state a required account, tool, or install step the way the other two do, so read it closely before relying on it.
Checked 19 September 2026 against what is currently live for this repository.
WHAT'S INSIDE
3 showing · 3 totalNothing else to set up — install it and go.
relay-best-practices
Relay is opinionated, and getting it wrong shows up as stale or duplicated data on the screen; these are the rules that keep that from happening.
relay-e2e-test
A whole end-to-end test fits inside one document — the fake server, the component and the clicks — which the harness then runs and compares against a saved snapshot.
relay-performance
When a Relay screen feels slow, the cause is usually the shape of its data requests — too many of them, or too much asked for at once.
HOW TO GET IT
npx skills add facebook/relaynpx skills add facebook/relay --skill <name> --full-depthPick the skill name from the Skills tab — each entry there installs independently.