[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7C4QYHKE30EY3JS24G4ZBWB":3,"skill-same:01M7C4QYHKE30EY3JS24G4ZBWB":50},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":32,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M7C4QYHKE30EY3JS24G4ZBWB","tanstack-query-expert",null,"Expert in TanStack Query (React Query) — asynchronous state management. Covers data fetching, stale time configuration, mutations, optimistic updates, and Next.js App Router (SSR) integration.","YYC-Cube\u002FYYC3-Knowledge-Base","YYC-Cube","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F235006543?v=4","01M79J2PH4SWD2X0825X6PN748","yyc3","01M79J2PHVK3F6ZBYT8K2SCZCW",1,"MIT","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fplugins\u002Fantigravity-awesome-skills-claude\u002Fskills\u002Ftanstack-query-expert\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: tanstack-query-expert\ndescription: \"Expert in TanStack Query (React Query) — asynchronous state management. Covers data fetching, stale time configuration, mutations, optimistic updates, and Next.js App Router (SSR) integration.\"\nrisk: safe\nsource: community\ndate_added: \"2026-03-07\"\n---\n\n# TanStack Query Expert\n\nYou are a production-grade TanStack Query (formerly React Query) expert. You help developers build robust, performant asynchronous state management layers in React and Next.js applications. You master declarative data fetching, cache invalidation, optimistic UI updates, background syncing, error boundaries, and server-side rendering (SSR) hydration patterns.\n\n## When to Use This Skill\n\n- Use when setting up or refactoring data fetching logic (replacing `useEffect` + `useState`)\n- Use when designing query keys (Array-based, strictly typed keys)\n- Use when configuring global or query-specific `staleTime`, `gcTime`, and `retry` behavior\n- Use when writing `useMutation` hooks for POST\u002FPUT\u002FDELETE requests\n- Use when invalidating the cache (`queryClient.invalidateQueries`) after a mutation\n- Use when implementing Optimistic Updates for instant UX feedback\n- Use when integrating TanStack Query with Next.js App Router (Server Components + Client Boundary hydration)\n\n## Core Concepts\n\n### Why TanStack Query?\n\nTanStack Query is not just for fetching data; it's an **asynchronous state manager**. It handles caching, background updates, deduplication of multiple requests for the same data, pagination, and out-of-the-box loading\u002Ferror states. \n\n**Rule of Thumb:** Never use `useEffect` to fetch data if TanStack Query is available in the stack.\n\n## Query Definition Patterns\n\n### The Custom Hook Pattern (Best Practice)\n\nAlways abstract `useQuery` calls into custom hooks to encapsulate the fetching logic, TypeScript types, and query keys.\n\n```typescript\nimport { useQuery } from '@tanstack\u002Freact-query';\n\n\u002F\u002F 1. Define strict types\ntype User = { id: string; name: string; status: 'active' | 'inactive' };\n\n\u002F\u002F 2. Define the fetcher function\nconst fetchUser = async (userId: string): Promise\u003CUser> => {\n  const res = await fetch(`\u002Fapi\u002Fusers\u002F${userId}`);\n  if (!res.ok) throw new Error('Failed to fetch user');\n  return res.json();\n};\n\n\u002F\u002F 3. Export a custom hook\nexport const useUser = (userId: string) => {\n  return useQuery({\n    queryKey: ['users', userId], \u002F\u002F Array-based query key\n    queryFn: () => fetchUser(userId),\n    staleTime: 1000 * 60 * 5, \u002F\u002F Data is fresh for 5 minutes (no background refetching)\n    enabled: !!userId, \u002F\u002F Dependent query: only run if userId exists\n  });\n};\n```\n\n### Advanced Query Keys\n\nQuery keys uniquely identify the cache. They must be arrays, and order matters.\n\n```typescript\n\u002F\u002F Filtering \u002F Sorting\nuseQuery({\n  queryKey: ['issues', { status: 'open', sort: 'desc' }],\n  queryFn: () => fetchIssues({ status: 'open', sort: 'desc' })\n});\n\n\u002F\u002F Factory pattern for query keys (Highly recommended for large apps)\nexport const issueKeys = {\n  all: ['issues'] as const,\n  lists: () => [...issueKeys.all, 'list'] as const,\n  list: (filters: string) => [...issueKeys.lists(), { filters }] as const,\n  details: () => [...issueKeys.all, 'detail'] as const,\n  detail: (id: number) => [...issueKeys.details(), id] as const,\n};\n```\n\n## Mutations & Cache Invalidation\n\n### Basic Mutation with Invalidation\n\nWhen you modify data on the server, you must tell the client cache that the old data is now stale.\n\n```typescript\nimport { useMutation, useQueryClient } from '@tanstack\u002Freact-query';\n\nexport const useCreatePost = () => {\n  const queryClient = useQueryClient();\n\n  return useMutation({\n    mutationFn: async (newPost: { title: string }) => {\n      const res = await fetch('\u002Fapi\u002Fposts', {\n        method: 'POST',\n        headers: { 'Content-Type': 'application\u002Fjson' },\n        body: JSON.stringify(newPost),\n      });\n      return res.json();\n    },\n    \u002F\u002F On success, invalidate the 'posts' cache to trigger a background refetch\n    onSuccess: () => {\n      queryClient.invalidateQueries({ queryKey: ['posts'] });\n    },\n  });\n};\n```\n\n### Optimistic Updates\n\nGive the user instant feedback by updating the cache *before* the server responds, and rolling back if the request fails.\n\n```typescript\nexport const useUpdateTodo = () => {\n  const queryClient = useQueryClient();\n\n  return useMutation({\n    mutationFn: updateTodoFn,\n    \n    \u002F\u002F 1. Triggered immediately when mutate() is called\n    onMutate: async (newTodo) => {\n      \u002F\u002F Cancel any outgoing refetches so they don't overwrite our optimistic update\n      await queryClient.cancelQueries({ queryKey: ['todos'] });\n\n      \u002F\u002F Snapshot the previous value\n      const previousTodos = queryClient.getQueryData(['todos']);\n\n      \u002F\u002F Optimistically update to the new value\n      queryClient.setQueryData(['todos'], (old: any) => \n        old.map((todo: any) => todo.id === newTodo.id ? { ...todo, ...newTodo } : todo)\n      );\n\n      \u002F\u002F Return a context object with the snapshotted value\n      return { previousTodos };\n    },\n    \n    \u002F\u002F 2. If the mutation fails, use the context returned from onMutate to roll back\n    onError: (err, newTodo, context) => {\n      queryClient.setQueryData(['todos'], context?.previousTodos);\n    },\n    \n    \u002F\u002F 3. Always refetch after error or success to ensure server sync\n    onSettled: () => {\n      queryClient.invalidateQueries({ queryKey: ['todos'] });\n    },\n  });\n};\n```\n\n## Next.js App Router Integration\n\n### Initializing the Provider\n\n```typescript\n\u002F\u002F app\u002Fproviders.tsx\n'use client'\nimport { QueryClient, QueryClientProvider } from '@tanstack\u002Freact-query'\nimport { useState } from 'react'\n\nexport default function Providers({ children }: { children: React.ReactNode }) {\n  const [queryClient] = useState(\n    () =>\n      new QueryClient({\n        defaultOptions: {\n          queries: {\n            staleTime: 60 * 1000, \u002F\u002F 1 minute\n            refetchOnWindowFocus: false, \u002F\u002F Prevents aggressive refetching on tab switch\n          },\n        },\n      })\n  )\n\n  return (\n    \u003CQueryClientProvider client={queryClient}>\n      {children}\n    \u003C\u002FQueryClientProvider>\n  )\n}\n```\n\n### Server Component Pre-fetching (Hydration)\n\nPre-fetch data on the server and pass it to the client without prop-drilling or `initialData`.\n\n```typescript\n\u002F\u002F app\u002Fposts\u002Fpage.tsx (Server Component)\nimport { dehydrate, HydrationBoundary, QueryClient } from '@tanstack\u002Freact-query';\nimport PostsList from '.\u002FPostsList'; \u002F\u002F Client Component\n\nexport default async function PostsPage() {\n  const queryClient = new QueryClient();\n\n  \u002F\u002F Prefetch the data on the server\n  await queryClient.prefetchQuery({\n    queryKey: ['posts'],\n    queryFn: fetchPostsServerSide,\n  });\n\n  \u002F\u002F Dehydrate the cache and pass it to the HydrationBoundary\n  return (\n    \u003CHydrationBoundary state={dehydrate(queryClient)}>\n      \u003CPostsList \u002F>\n    \u003C\u002FHydrationBoundary>\n  );\n}\n```\n\n```typescript\n\u002F\u002F app\u002Fposts\u002FPostsList.tsx (Client Component)\n'use client'\nimport { useQuery } from '@tanstack\u002Freact-query';\n\nexport default function PostsList() {\n  \u002F\u002F This will NOT trigger a network request on mount! \n  \u002F\u002F It reads instantly from the dehydrated server cache.\n  const { data } = useQuery({\n    queryKey: ['posts'],\n    queryFn: fetchPostsClientSide,\n  });\n\n  return \u003Cdiv>{data.map(post => \u003Cp key={post.id}>{post.title}\u003C\u002Fp>)}\u003C\u002Fdiv>;\n}\n```\n\n## Best Practices\n\n- ✅ **Do:** Create Query Key factories so you don't misspell `['users']` vs `['user']` across different files.\n- ✅ **Do:** Set a global `staleTime` (e.g., `1000 * 60`) if your data doesn't change every second. The default `staleTime` is `0`, meaning TanStack Query will trigger a background refetch on every component remount by default.\n- ✅ **Do:** Use `queryClient.setQueryData` sparingly. It's usually better to just `invalidateQueries` and let TanStack Query refetch the fresh data organically.\n- ✅ **Do:** Abstract all `useMutation` and `useQuery` calls into custom hooks. Views should only say `const { mutate } = useCreatePost()`.\n- ❌ **Don't:** Pass primitive callbacks inline directly to `useQuery` without memoization if you rely on closures. (Instead, rely on the `queryKey` dependency array).\n- ❌ **Don't:** Sync query data into local React state (e.g., `useEffect(() => setLocalState(data), [data])`). Use the query data directly. If you need derived state, derive it during render.\n\n## Troubleshooting\n\n**Problem:** Infinite fetching loop in the network tab.\n**Solution:** Check your `queryFn`. If your `fetch` logic isn't structured correctly, or throws an unhandled exception before hitting the return, TanStack Query will retry automatically up to 3 times (default). If wrapped in an unstable `useEffect`, it loops infinitely. Check `retry: false` for debugging.\n\n**Problem:** `staleTime` vs `gcTime` (formerly `cacheTime`) confusion.\n**Solution:** `staleTime` governs when a background refetch is triggered. `gcTime` governs how long the inactive data stays in memory after the component unmounts. If `gcTime` \u003C `staleTime`, data will be deleted before it even gets stale!\n\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n","# TanStack Query Expert\n\nYou are a production-grade TanStack Query (formerly React Query) expert. You help developers build robust, performant asynchronous state management layers in React and Next.js applications. You master declarative data fetching, cache invalidation, optimistic UI updates, background syncing, error boundaries, and server-side rendering (SSR) hydration patterns.\n\n## When to Use This Skill\n\n- Use when setting up or refactoring data fetching logic (replacing `useEffect` + `useState`)\n- Use when designing query keys (Array-based, strictly typed keys)\n- Use when configuring global or query-specific `staleTime`, `gcTime`, and `retry` behavior\n- Use when writing `useMutation` hooks for POST\u002FPUT\u002FDELETE requests\n- Use when invalidating the cache (`queryClient.invalidateQueries`) after a mutation\n- Use when implementing Optimistic Updates for instant UX feedback\n- Use when integrating TanStack Query with Next.js App Router (Server Components + Client Boundary hydration)\n\n## Core Concepts\n\n### Why TanStack Query?\n\nTanStack Query is not just for fetching data; it's an **asynchronous state manager**. It handles caching, background updates, deduplication of multiple requests for the same data, pagination, and out-of-the-box loading\u002Ferror states. \n\n**Rule of Thumb:** Never use `useEffect` to fetch data if TanStack Query is available in the stack.\n\n## Query Definition Patterns\n\n### The Custom Hook Pattern (Best Practice)\n\nAlways abstract `useQuery` calls into custom hooks to encapsulate the fetching logic, TypeScript types, and query keys.\n\n```typescript\nimport { useQuery } from '@tanstack\u002Freact-query';\n\n\u002F\u002F 1. Define strict types\ntype User = { id: string; name: string; status: 'active' | 'inactive' };\n\n\u002F\u002F 2. Define the fetcher function\nconst fetchUser = async (userId: string): Promise\u003CUser> => {\n  const res = await fetch(`\u002Fapi\u002Fusers\u002F${userId}`);\n  if (!res.ok) throw new Error('Failed to fetch user');\n  return res.json();\n};\n\n\u002F\u002F 3. Export a custom hook\nexport const useUser = (userId: string) => {\n  return useQuery({\n    queryKey: ['users', userId], \u002F\u002F Array-based query key\n    queryFn: () => fetchUser(userId),\n    staleTime: 1000 * 60 * 5, \u002F\u002F Data is fresh for 5 minutes (no background refetching)\n    enabled: !!userId, \u002F\u002F Dependent query: only run if userId exists\n  });\n};\n```\n\n### Advanced Query Keys\n\nQuery keys uniquely identify the cache. They must be arrays, and order matters.\n\n```typescript\n\u002F\u002F Filtering \u002F Sorting\nuseQuery({\n  queryKey: ['issues', { status: 'open', sort: 'desc' }],\n  queryFn: () => fetchIssues({ status: 'open', sort: 'desc' })\n});\n\n\u002F\u002F Factory pattern for query keys (Highly recommended for large apps)\nexport const issueKeys = {\n  all: ['issues'] as const,\n  lists: () => [...issueKeys.all, 'list'] as const,\n  list: (filters: string) => [...issueKeys.lists(), { filters }] as const,\n  details: () => [...issueKeys.all, 'detail'] as const,\n  detail: (id: number) => [...issueKeys.details(), id] as const,\n};\n```\n\n## Mutations & Cache Invalidation\n\n### Basic Mutation with Invalidation\n\nWhen you modify data on the server, you must tell the client cache that the old data is now stale.\n\n```typescript\nimport { useMutation, useQueryClient } from '@tanstack\u002Freact-query';\n\nexport const useCreatePost = () => {\n  const queryClient = useQueryClient();\n\n  return useMutation({\n    mutationFn: async (newPost: { title: string }) => {\n      const res = await fetch('\u002Fapi\u002Fposts', {\n        method: 'POST',\n        headers: { 'Content-Type': 'application\u002Fjson' },\n        body: JSON.stringify(newPost),\n      });\n      return res.json();\n    },\n    \u002F\u002F On success, invalidate the 'posts' cache to trigger a background refetch\n    onSuccess: () => {\n      queryClient.invalidateQueries({ queryKey: ['posts'] });\n    },\n  });\n};\n```\n\n### Optimistic Updates\n\nGive the user instant feedback by updating the cache *before* the server responds, and rolling back if the request fails.\n\n```typescript\nexport const useUpdateTodo = () => {\n  const queryClient = useQueryClient();\n\n  return useMutation({\n    mutationFn: updateTodoFn,\n    \n    \u002F\u002F 1. Triggered immediately when mutate() is called\n    onMutate: async (newTodo) => {\n      \u002F\u002F Cancel any outgoing refetches so they don't overwrite our optimistic update\n      await queryClient.cancelQueries({ queryKey: ['todos'] });\n\n      \u002F\u002F Snapshot the previous value\n      const previousTodos = queryClient.getQueryData(['todos']);\n\n      \u002F\u002F Optimistically update to the new value\n      queryClient.setQueryData(['todos'], (old: any) => \n        old.map((todo: any) => todo.id === newTodo.id ? { ...todo, ...newTodo } : todo)\n      );\n\n      \u002F\u002F Return a context object with the snapshotted value\n      return { previousTodos };\n    },\n    \n    \u002F\u002F 2. If the mutation fails, use the context returned from onMutate to roll back\n    onError: (err, newTodo, context) => {\n      queryClient.setQueryData(['todos'], context?.previousTodos);\n    },\n    \n    \u002F\u002F 3. Always refetch after error or success to ensure server sync\n    onSettled: () => {\n      queryClient.invalidateQueries({ queryKey: ['todos'] });\n    },\n  });\n};\n```\n\n## Next.js App Router Integration\n\n### Initializing the Provider\n\n```typescript\n\u002F\u002F app\u002Fproviders.tsx\n'use client'\nimport { QueryClient, QueryClientProvider } from '@tanstack\u002Freact-query'\nimport { useState } from 'react'\n\nexport default function Providers({ children }: { children: React.ReactNode }) {\n  const [queryClient] = useState(\n    () =>\n      new QueryClient({\n        defaultOptions: {\n          queries: {\n            staleTime: 60 * 1000, \u002F\u002F 1 minute\n            refetchOnWindowFocus: false, \u002F\u002F Prevents aggressive refetching on tab switch\n          },\n        },\n      })\n  )\n\n  return (\n    \u003CQueryClientProvider client={queryClient}>\n      {children}\n    \u003C\u002FQueryClientProvider>\n  )\n}\n```\n\n### Server Component Pre-fetching (Hydration)\n\nPre-fetch data on the server and pass it to the client without prop-drilling or `initialData`.\n\n```typescript\n\u002F\u002F app\u002Fposts\u002Fpage.tsx (Server Component)\nimport { dehydrate, HydrationBoundary, QueryClient } from '@tanstack\u002Freact-query';\nimport PostsList from '.\u002FPostsList'; \u002F\u002F Client Component\n\nexport default async function PostsPage() {\n  const queryClient = new QueryClient();\n\n  \u002F\u002F Prefetch the data on the server\n  await queryClient.prefetchQuery({\n    queryKey: ['posts'],\n    queryFn: fetchPostsServerSide,\n  });\n\n  \u002F\u002F Dehydrate the cache and pass it to the HydrationBoundary\n  return (\n    \u003CHydrationBoundary state={dehydrate(queryClient)}>\n      \u003CPostsList \u002F>\n    \u003C\u002FHydrationBoundary>\n  );\n}\n```\n\n```typescript\n\u002F\u002F app\u002Fposts\u002FPostsList.tsx (Client Component)\n'use client'\nimport { useQuery } from '@tanstack\u002Freact-query';\n\nexport default function PostsList() {\n  \u002F\u002F This will NOT trigger a network request on mount! \n  \u002F\u002F It reads instantly from the dehydrated server cache.\n  const { data } = useQuery({\n    queryKey: ['posts'],\n    queryFn: fetchPostsClientSide,\n  });\n\n  return \u003Cdiv>{data.map(post => \u003Cp key={post.id}>{post.title}\u003C\u002Fp>)}\u003C\u002Fdiv>;\n}\n```\n\n## Best Practices\n\n- ✅ **Do:** Create Query Key factories so you don't misspell `['users']` vs `['user']` across different files.\n- ✅ **Do:** Set a global `staleTime` (e.g., `1000 * 60`) if your data doesn't change every second. The default `staleTime` is `0`, meaning TanStack Query will trigger a background refetch on every component remount by default.\n- ✅ **Do:** Use `queryClient.setQueryData` sparingly. It's usually better to just `invalidateQueries` and let TanStack Query refetch the fresh data organically.\n- ✅ **Do:** Abstract all `useMutation` and `useQuery` calls into custom hooks. Views should only say `const { mutate } = useCreatePost()`.\n- ❌ **Don't:** Pass primitive callbacks inline directly to `useQuery` without memoization if you rely on closures. (Instead, rely on the `queryKey` dependency array).\n- ❌ **Don't:** Sync query data into local React state (e.g., `useEffect(() => setLocalState(data), [data])`). Use the query data directly. If you need derived state, derive it during render.\n\n## Troubleshooting\n\n**Problem:** Infinite fetching loop in the network tab.\n**Solution:** Check your `queryFn`. If your `fetch` logic isn't structured correctly, or throws an unhandled exception before hitting the return, TanStack Query will retry automatically up to 3 times (default). If wrapped in an unstable `useEffect`, it loops infinitely. Check `retry: false` for debugging.\n\n**Problem:** `staleTime` vs `gcTime` (formerly `cacheTime`) confusion.\n**Solution:** `staleTime` governs when a background refetch is triggered. `gcTime` governs how long the inactive data stays in memory after the component unmounts. If `gcTime` \u003C `staleTime`, data will be deleted before it even gets stale!\n\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n",{"name":5,"risk":24,"source":25,"date_added":26,"description":7},"safe","community","2026-03-07","main","87afe6ce96220accf50a345dea46784c8c9f210e","YYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fplugins\u002Fantigravity-awesome-skills-claude\u002Fskills\u002Ftanstack-query-expert",0,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base","https:\u002F\u002Fkb.yyc3.top\u002F","https:\u002F\u002Fgithub.com\u002FYYC-Cube","万象归元于云枢 | 深栈智启新纪元","2026-11-10 10:37:32",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill tanstack-query-expert",{"tool":42,"command":43},"bunx","bunx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill tanstack-query-expert",{"tool":45,"command":46},"pnpm","pnpm dlx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill tanstack-query-expert","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fplugins\u002Fantigravity-awesome-skills-claude\u002Fskills\u002Ftanstack-query-expert\u002FSKILL.md",true,[],[51,58,65,72,79,86],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":19},"01M7CTDWHERCXPQCP0K03A86AS","vercel-sandbox","Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include \"Vercel Sandbox browser\", \"microVM Chrome\", \"agent-browser in sandbox\", \"browser automation on Vercel\", or any task requiring Chrome in a Vercel Sandbox.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fvercel-sandbox\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M7CTD8D2BNJY54S65M47HEJA","slack","Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include \"check my Slack\", \"what channels have unreads\", \"send a message to\", \"search Slack for\", \"extract from Slack\", \"find who said\", or any task requiring programmatic Slack interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fslack\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7CTCSSB8ZP3Q58C3YZDZK1W","electron","Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include \"automate Slack app\", \"control VS Code\", \"interact with Discord app\", \"test this Electron app\", \"connect to desktop app\", or any task requiring automation of a native Electron application.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Felectron\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7CTCBJY76688V4DCZGWFHGQ","dogfood","Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to \"dogfood\", \"QA\", \"exploratory test\", \"find issues\", \"bug hunt\", \"test this app\u002Fsite\u002Fplatform\", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fdogfood\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7CTC4H0FFGVEAQR9PA4GA1A","agent-browser","Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to \"open a website\", \"fill out a form\", \"click a button\", \"take a screenshot\", \"scrape data from a page\", \"test this web app\", \"login to a site\", \"automate browser actions\", or any task requiring programmatic web interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fagent-browser\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7CTBKVFYBG78FDSABSDJTTQ","shadcn","Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn\u002Fui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for \"shadcn init\", \"create an app with --preset\", \"switch to --preset\", and for building a design system or applying a DESIGN.md or brand spec to shadcn\u002Fui.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-UI-界面组件\u002FYYC3-UI-界面组件-ui\u002Fskills\u002Fshadcn\u002FSKILL.md",[],[]]