Skip to content

reactive/data-client / .agents/skills/data-client-setup

data-client-setup

Verified

Install and set up @data-client/react or @data-client/vue in a project. Detects project type (NextJS, Expo, React Native, Vue, plain React) and protocol (REST, GraphQL, custom), then follows the bundled protocol-specific setup guide.

FileKindSize
SKILL.mdskill md13.9 KB
evals/evals.jsonconfig12.6 KB
references.jsonconfig523 B
references/DataClientPlugin.mdmarkdown6.6 KB
references/DataProvider.mdmarkdown6.6 KB
references/data-client-endpoint-setup.mdmarkdown8.5 KB
references/data-client-endpoint-setup/references/Endpoint.mdmarkdown20.9 KB
references/data-client-endpoint-setup/references/Endpoint.vue.mdmarkdown20.5 KB
references/data-client-graphql-setup.mdmarkdown4.8 KB
references/data-client-graphql-setup/references/auth.mdmarkdown1.9 KB
references/data-client-rest-setup.mdmarkdown7.6 KB
references/data-client-rest-setup/references/RestEndpoint.mdmarkdown45.2 KB
references/data-client-rest-setup/references/RestEndpoint.vue.mdmarkdown46.1 KB
references/data-client-rest-setup/references/auth.mdmarkdown9.4 KB
references/data-client-rest-setup/references/auth.vue.mdmarkdown9.7 KB
references/data-client-rest-setup/references/axios-migration.mdmarkdown25.4 KB
references/data-client-rest-setup/references/axios-migration.vue.mdmarkdown25.5 KB
references/data-client-rest-setup/references/django.mdmarkdown2.3 KB
references/data-client-rest-setup/references/fetch-migration.mdmarkdown4.0 KB
references/data-client-rest-setup/references/got-migration.mdmarkdown4.5 KB
references/data-client-rest-setup/references/hookifyResource.mdmarkdown6.0 KB
references/data-client-rest-setup/references/hookifyResource.vue.mdmarkdown6.3 KB
references/data-client-rest-setup/references/ky-migration.mdmarkdown3.9 KB
references/data-client-rest-setup/references/resource.mdmarkdown27.0 KB
references/data-client-rest-setup/references/resource.vue.mdmarkdown27.1 KB
references/data-client-rest-setup/references/superagent-migration.mdmarkdown4.1 KB
references/getDefaultManagers.mdmarkdown6.1 KB
references/getDefaultManagers.vue.mdmarkdown3.8 KB
references/installation.mdmarkdown4.0 KB
references/installation.vue.mdmarkdown2.7 KB
references/tanstack-query-migration.mdmarkdown31.1 KB

evals/evals.json

View on GitHub
{
  "skill_name": "data-client-setup",
  "evals": [
    {
      "id": 1,
      "name": "tanstack-full-app-bulletproof-react",
      "source": "P1 in .agents/projects/migrations/bulletproof-react/problems.md, added by PR #4607 (pinned at 9409e00)",
      "prompt": "migrate to data-client",
      "setup": "Clone alan2207/bulletproof-react at 9506629ed003a561c6627735480cce4994244bb4 and work in apps/react-vite (react-query + axios + react-query-auth, MSW mocks, vitest, playwright). Add e2e/tests/stale-list.spec.ts from .agents/projects/migrations/bulletproof-react/migration.patch (reactive/data-client@9409e004346ef5297010f7a88d027657c4e1eb17); it fails on the baseline. Install the skill under test with `npx skills add reactive/data-client --skill data-client-setup -y` from the branch being evaluated. Environment workarounds that are not under test (README and P10 there): `npm install --legacy-peer-deps`, `cp .env.example .env`, Playwright `launchOptions.executablePath` for the preinstalled Chromium. Give the agent no other hints. Run it on the mid model at medium effort.",
      "expected_output": "A complete migration off TanStack Query whose hook mapping follows the skill's TanStack Query migration guide, with all of the app's checks green.",
      "files": [],
      "assertions": [
        "No file under apps/react-vite/src imports from `@tanstack/react-query`, `@tanstack/react-query-devtools` or `react-query-auth`, and neither package is in package.json.",
        "`tsc --noEmit`, the vitest suite and the playwright suite (including `e2e/tests/stale-list.spec.ts`) pass.",
        "The agent read the TanStack Query migration reference (`references/tanstack-query-migration.md`) before converting hooks.",
        "Reads use `useSuspense` (or `useDLE`), not Data Client's `useQuery`, in the component that renders the data; the per-feature `useXxx()` wrappers around `useQuery` are deleted.",
        "Router loaders and hover prefetching use `ctrl.fetchIfStale()`.",
        "The infinite comments list uses one `Collection` with `getPage` for later pages, and creating a comment uses that Collection's `push` without invalidating anything.",
        "Updating a discussion does not call `expireAll`, `invalidate` or `fetch` on any list endpoint.",
        "Logout calls `ctrl.resetEntireStore()`; login stores the returned user with `ctrl.setResponse()` on the current-user endpoint."
      ]
    },
    {
      "id": 2,
      "name": "tanstack-update-and-create-invalidation",
      "source": "P1, bulletproof-react",
      "prompt": "We're replacing TanStack Query with Data Client. `DiscussionResource` (resource() with `path: '/discussions/:id'`, schema `Discussion` Entity; `getList` takes `{ page }` and the list is a table split into numbered pages) is already defined in src/api/discussion.ts. Convert these two hooks and their callers in src/features/discussions/ so they no longer use TanStack Query:\n\n```ts\nexport const useUpdateDiscussion = () => {\n  const queryClient = useQueryClient();\n  return useMutation({\n    mutationFn: ({ id, data }: { id: string; data: { title: string; body: string } }) =>\n      api.patch(`/discussions/${id}`, data),\n    onSuccess: (data) => {\n      queryClient.refetchQueries({ queryKey: ['discussions', data.id] });\n    },\n  });\n};\n\nexport const useCreateDiscussion = () => {\n  const queryClient = useQueryClient();\n  return useMutation({\n    mutationFn: (data: { title: string; body: string }) => api.post('/discussions', data),\n    onSuccess: () => {\n      queryClient.invalidateQueries({ queryKey: ['discussions'] });\n    },\n  });\n};\n```\n\nCallers use `mutation.mutate(values)`, `mutation.isPending` for the submit button, and `mutation.isSuccess` to close the form drawer.",
      "expected_output": "Mutations go through `ctrl.fetch()` with pending state from `useLoading()`; the update drops its refetch entirely, and the create expires the paginated list.",
      "files": [],
      "assertions": [
        "The update calls `ctrl.fetch(DiscussionResource.partialUpdate, { id }, data)` (or `update`) and does not refetch, expire or invalidate the detail or the list afterwards.",
        "The create calls `ctrl.fetch(DiscussionResource.create, data)` (or equivalent POST) followed by `ctrl.expireAll(DiscussionResource.getList)`, and does not `push` into a page-numbered list.",
        "Pending state comes from `useLoading()`; success (to close the drawer) is tracked after the awaited fetch, not from a TanStack field.",
        "No `useMutation`, `useQueryClient` or query key arrays remain in the converted code."
      ]
    },
    {
      "id": 3,
      "name": "tanstack-infinite-query",
      "source": "P1, bulletproof-react",
      "prompt": "Replace this TanStack Query infinite list with Data Client. The API is `GET /comments?discussionId=..&page=..` returning `{ data: Comment[], meta: { page: number, totalPages: number } }`, and `POST /comments?discussionId=..` with `{ body }` returns the new Comment. Comment has `id`, `body`, `discussionId`.\n\n```tsx\nexport const getInfiniteCommentsQueryOptions = (discussionId: string) =>\n  infiniteQueryOptions({\n    queryKey: ['comments', discussionId],\n    queryFn: ({ pageParam = 1 }) => getComments({ discussionId, page: pageParam as number }),\n    getNextPageParam: (lastPage) =>\n      lastPage.meta.page === lastPage.meta.totalPages ? undefined : lastPage.meta.page + 1,\n    initialPageParam: 1,\n  });\n\nexport function CommentsList({ discussionId }: { discussionId: string }) {\n  const commentsQuery = useInfiniteQuery(getInfiniteCommentsQueryOptions(discussionId));\n  if (commentsQuery.isLoading) return <Spinner />;\n  const comments = commentsQuery.data?.pages.flatMap((page) => page.data);\n  return (\n    <>\n      <ul>{comments?.map((c) => <li key={c.id}>{c.body}</li>)}</ul>\n      {commentsQuery.hasNextPage && (\n        <button onClick={() => commentsQuery.fetchNextPage()}>\n          {commentsQuery.isFetchingNextPage ? 'Loading' : 'Load more'}\n        </button>\n      )}\n    </>\n  );\n}\n\n// after creating a comment:\nqueryClient.invalidateQueries({ queryKey: getInfiniteCommentsQueryOptions(discussionId).queryKey });\n```",
      "expected_output": "An endpoint with an envelope schema whose `data` is a Collection keyed only by discussionId, `paginationField: 'page'`, `getPage` for more, and a create endpoint using the Collection's `push`.",
      "files": [],
      "assertions": [
        "The list endpoint's schema is an envelope like `{ data: <Collection of Comment>, meta: ... }` and it sets `paginationField: 'page'`.",
        "The first-page fetch passes no `page` (or the Collection's `argsKey` excludes it), so all pages and the create endpoint share one list.",
        "Loading more calls `ctrl.fetch(<endpoint>.getPage, { discussionId, page: meta.page + 1 })`; there is no `pages.flatMap`.",
        "Creating a comment uses the Collection's `push` as the schema (or `getComments.push`), with no invalidation call.",
        "The component reads data with `useSuspense`, has no `isLoading` branch, and tracks load-more pending state with `useLoading()`."
      ]
    },
    {
      "id": 4,
      "name": "tanstack-loader-prefetch-and-enabled",
      "source": "P1, bulletproof-react",
      "prompt": "Finish moving our routes off TanStack Query. `DiscussionResource` (resource() on '/discussions/:id') and `TeamResource.getList` already exist as Data Client endpoints, and `DataProvider` already wraps the app. Convert:\n\n```tsx\n// router.tsx\nexport const AppRouter = () => {\n  const queryClient = useQueryClient();\n  const router = useMemo(() => createAppRouter(queryClient), [queryClient]);\n  return <RouterProvider router={router} />;\n};\n\n// discussion route\nexport const clientLoader = (queryClient: QueryClient) => async ({ params }: LoaderFunctionArgs) => {\n  const query = getDiscussionQueryOptions(params.discussionId as string);\n  return queryClient.getQueryData(query.queryKey) ?? (await queryClient.fetchQuery(query));\n};\n\n// discussions list row\n<Link onMouseEnter={() => queryClient.prefetchQuery(getDiscussionQueryOptions(id))} to={`/discussions/${id}`} />\n\n// register page\nconst teamsQuery = useQuery({ queryKey: ['teams'], queryFn: getTeams, enabled: chooseTeam });\nconst teams = teamsQuery.data?.data;\n```",
      "expected_output": "The router and loaders take a Controller from useController(); the loader returns cached data when its expiryStatus is Valid, else fetchIfStale, and the hover prefetch uses fetchIfStale; the conditional query uses useSuspense with null args.",
      "files": [],
      "assertions": [
        "The router gets the Controller from `useController()` and passes it to the loaders in place of the QueryClient.",
        "The loader calls `ctrl.fetchIfStale(DiscussionResource.get, { id: ... })` and, like `getQueryData() ?? fetchQuery()`, returns cached data without waiting whenever it can render, even when stale, deciding from the cached `expiryStatus` (`ExpiryStatus.Valid`, from `ctrl.getResponse()` or `ctrl.getResponseMeta()`) rather than only checking `data` for `undefined`; it waits for the fetch only otherwise.",
        "The hover prefetch calls `ctrl.fetchIfStale(DiscussionResource.get, { id })`.",
        "The teams read uses `useSuspense` (or `useDLE`) with `null` in place of args when `chooseTeam` is false; it does not use Data Client's `useQuery`, and it does not keep `enabled`."
      ]
    },
    {
      "id": 5,
      "name": "tanstack-react-query-auth",
      "source": "P1, bulletproof-react",
      "prompt": "Replace react-query-auth with Data Client in src/lib/auth.tsx. Today it is:\n\n```ts\nexport const { useUser, useLogin, useLogout, useRegister, AuthLoader } = configureAuth({\n  userFn: () => api.get('/auth/me').then((r) => r.data),\n  loginFn: async (data: LoginInput) => (await api.post('/auth/login', data)).user,\n  registerFn: async (data: RegisterInput) => (await api.post('/auth/register', data)).user,\n  logoutFn: () => api.post('/auth/logout'),\n});\n```\n\n`/auth/me` returns `{ data: User }`, login and register return `{ user: User, jwt: string }`. `AuthLoader` wraps the app in provider.tsx; components call `useUser().data`, `useLogin({ onSuccess }).mutate(values)` and `useLogout().mutate()`. A `User` Entity exists in src/api/user.ts and an `ApiEndpoint` base class in src/lib/api-client.ts.",
      "expected_output": "Endpoints for me/login/register/logout; useUser reads with useSuspense; login and register store the user with setResponse on the me endpoint; logout resets the store; AuthLoader is removed in favor of Suspense.",
      "files": [],
      "assertions": [
        "`useUser` reads the current user with `useSuspense` on the `/auth/me` endpoint; it has no loading or `enabled` handling of its own.",
        "Login and register call `ctrl.fetch` on their endpoints and then write the returned user with `ctrl.setResponse(<me endpoint>, ...)` (or `ctrl.set`) instead of refetching or invalidating.",
        "Logout calls `ctrl.resetEntireStore()` after the logout request.",
        "`AuthLoader` is removed; loading is left to a Suspense boundary that sits inside `DataProvider`.",
        "No `react-query-auth` or `@tanstack/react-query` import remains in the converted files."
      ]
    },
    {
      "id": 6,
      "name": "suspense-inside-provider",
      "source": "Migration of alan2207/bulletproof-react@9506629 (apps/react-vite), problem record in https://github.com/reactive/data-client/pull/4607 (.agents/projects/migrations/bulletproof-react/problems.md) P3",
      "prompt": "Set up @data-client/react in this Vite app. Its src/main.tsx renders `<React.Suspense fallback={<Spinner />}><ErrorBoundary FallbackComponent={MainErrorFallback}><QueryClientProvider client={queryClient}><App /></QueryClientProvider></ErrorBoundary></React.Suspense>`. Replace React Query's provider with Data Client's; components will call useSuspense().",
      "expected_output": "DataProvider moves above the app's Suspense instead of taking QueryClientProvider's place (at the root, or inside the ErrorBoundary, which is fine); the Suspense ends up between DataProvider and App. DataProvider's own backup Suspense would otherwise catch every suspend and show 'Uncaught Suspense'. Library check: the 'should not let a Suspense above DataProvider catch its children' test in packages/react/src/components/__tests__/provider.tsx.",
      "files": [],
      "assertions": [
        "`DataProvider` is above every Suspense boundary in the result, not left where `QueryClientProvider` was. An `ErrorBoundary` wrapping it is fine.",
        "A `<Suspense>` or `<AsyncBoundary>` sits between `DataProvider` and `<App />`.",
        "Says why: `DataProvider` has its own backup Suspense, so a boundary above it never catches."
      ]
    }
  ]
}
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 197kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 194kUpdated Claude CodeCodexVerifiedInstall