[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M758TNEGSHC07TYVBEEYKYZW":3,"skill-same:01M758TNEGSHC07TYVBEEYKYZW":46},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":28,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M758TNEGSHC07TYVBEEYKYZW","react-components",null,"Use when writing, refactoring, or reviewing React components inside a TanStack Start application. Focuses on SOLID component design, composition, and correct use of loaders, server functions, and React Query for client-side state.","CliqRelay\u002Fcliqrelay","CliqRelay","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F290753656?v=4","01M758RPDEB11FEYA2XK17DSHA","01M758RPEKP0NKH6P43GD2FBDG",41,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FCliqRelay\u002Fcliqrelay\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ffrontend\u002Freact-components\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: react-components\ndescription: Use when writing, refactoring, or reviewing React components inside a TanStack Start application. Focuses on SOLID component design, composition, and correct use of loaders, server functions, and React Query for client-side state.\n---\n\n# React Components\n\n## When to use this skill\n\nUse this skill ONLY when:\n\n* Writing React components inside an app\n* Refactoring React UI code\n* Reviewing React components\n* Building UI features using TanStack Start\n\nDo NOT use for:\n\n* Backend architecture design\n* API design\n* Build tooling or infra\n* Non-UI server logic\n\n---\n\n# Core Rules\n\n1. Components must follow SOLID principles\n2. Components must stay small and focused\n3. Data fetching must follow TanStack Start patterns (loaders + server functions) for the web app, or `@repo\u002Fapi-client` auto-generated hooks for the extension app\n4. Never use `useEffect` for data fetching\n5. Business logic must be extracted into hooks\n6. Composition is preferred over configuration\n7. Components must be easy to read and test\n8. Always use Shadcn UI primitives for UI consistency and accessibility\n\n---\n\n# Data Fetching Architecture (IMPORTANT)\n\nTanStack Start uses a hybrid data model, combined with `@repo\u002Fapi-client`:\n\n## 1. Route Loaders (Server-first, initial data)\n\nUse loaders for:\n\n* Initial page data\n* SEO-critical content\n* Data required before render\n* Avoiding loading states on first paint\n\nRoute loaders call either **server functions** (preferred) or **`@repo\u002Fapi-client` directly**:\n\n```typescript\n\u002F\u002F routes\u002Fguides\u002Findex.tsx\nimport { createFileRoute } from \"@tanstack\u002Freact-router\";\nimport { getAllGuides } from \"@\u002Fserver-fns\u002Fguides\";\n\u002F\u002F OR: import { api } from \"@repo\u002Fapi-client\";\n\nexport const Route = createFileRoute(\"\u002Fguides\u002F\")({\n  loader: async () => {\n    \u002F\u002F ✅ DO — Call server function (preferred)\n    const guides = await getAllGuides();\n    \u002F\u002F OR call api-client directly for simple cases:\n    \u002F\u002F const guides = await api.guides.getAllGuides();\n    return { guides };\n  },\n  component: GuidesPage,\n});\n```\n\n### Consuming loader data\n\n```typescript\nfunction GuidesPage() {\n  const { guides } = Route.useLoaderData();\n\n  return (\n    \u003Cdiv>\n      {guides.map(guide => (\n        \u003CGuideCard key={guide.id} guide={guide} \u002F>\n      ))}\n    \u003C\u002Fdiv>\n  );\n}\n```\n\n---\n\n## 2. Server Functions (TanStack Start `createServerFn`)\n\nServer functions wrap `@repo\u002Fapi-client` calls and are the primary data access pattern:\n\n```typescript\n\u002F\u002F server-fns\u002Fguides.ts\nimport { createServerFn } from \"@tanstack\u002Freact-start\";\nimport { api } from \"@repo\u002Fapi-client\";\n\nexport const getAllGuides = createServerFn({ method: \"GET\" })\n  .handler(async () => {\n    const { data, status } = await api.guides.getAllGuides();\n    if (status !== 200) {\n      throw new Error(\"Failed to fetch guides\");\n    }\n    return data.guides;\n  });\n\nexport const createGuide = createServerFn({ method: \"POST\" })\n  .inputValidator((input: { title: string; description?: string }) => input)\n  .handler(async ({ data }) => {\n    const response = await api.guides.createGuide({\n      title: data.title,\n      description: data.description ?? null,\n    });\n    if (response.status !== 201 || !response.data?.guide) {\n      return null;\n    }\n    return response.data.guide;\n  });\n```\n\nServer functions:\n- Run on the server (not exposed to the client bundle)\n- Accept typed inputs via `.inputValidator()`\n- Return typed data (types come from `@repo\u002Fapi-client`)\n- Are called from route loaders or from client components\n\n---\n\n## 3. Client-side Mutations (Web App)\n\nFor mutations triggered by user actions, call server functions directly in event handlers:\n\n```typescript\nfunction CreateGuideForm() {\n  const navigate = Route.useNavigate();\n\n  const handleSubmit = async (data: { title: string; description?: string }) => {\n    try {\n      const guide = await createGuide({ data });\n      if (guide) {\n        navigate({ to: `\u002Fguides\u002F${guide.id}` });\n        showToastSuccess(\"Guide created\");\n      }\n    } catch (error: any) {\n      showToastError(\"Error\", error.message ?? \"Failed to create guide\");\n    }\n  };\n\n  return \u003CForm onSubmit={handleSubmit} \u002F>;\n}\n```\n\nFor TanStack Query-based mutations (with cache invalidation), use `useMutation`:\n\n```typescript\nimport { useMutation, useQueryClient } from \"@tanstack\u002Freact-query\";\nimport { createGuide } from \"@\u002Fserver-fns\u002Fguides\";\n\nfunction useCreateGuideMutation() {\n  const queryClient = useQueryClient();\n  const navigate = Route.useNavigate();\n\n  return useMutation({\n    mutationFn: (data: { title: string; description?: string }) =>\n      createGuide({ data }),\n    onSuccess: (guide) => {\n      queryClient.invalidateQueries({ queryKey: [\"guides\"] });\n      navigate({ to: `\u002Fguides\u002F${guide.id}` });\n    },\n  });\n}\n```\n\n---\n\n## 4. Extension App: `@repo\u002Fapi-client` Directly\n\nThe extension app uses `@repo\u002Fapi-client` directly. Use `api.*` for programmatic calls (background scripts, services) and auto-generated hooks for React components:\n\n```typescript\n\u002F\u002F ✅ DO — Programmatic calls (background scripts, etc.)\nimport { api } from \"@repo\u002Fapi-client\";\n\nasync function archiveGuide(guideId: string) {\n  const response = await api.guides.archiveGuide(guideId);\n  if (response.status !== 200 || !response.data?.guide) {\n    return null;\n  }\n  return response.data.guide;\n}\n\n\u002F\u002F ✅ DO — Auto-generated hooks for React components\nimport { useGetAllGuides, useCreateGuide } from \"@repo\u002Fapi-client\";\n\nfunction GuideList() {\n  const { data, isLoading, error } = useGetAllGuides();\n  const createMutation = useCreateGuide({\n    mutation: {\n      onSuccess: () => {\n        showToastSuccess(\"Guide created\");\n      },\n    },\n  });\n\n  if (isLoading) return \u003CSpinner \u002F>;\n  if (error) return \u003CErrorDisplay error={error} \u002F>;\n\n  return (\n    \u003Cdiv>\n      {data?.guides?.map(guide => (\n        \u003CGuideCard key={guide.id} guide={guide} \u002F>\n      ))}\n      \u003Cbutton onClick={() => createMutation.mutate({ data: { title: \"New\" } })}>\n        Create Guide\n      \u003C\u002Fbutton>\n    \u003C\u002Fdiv>\n  );\n}\n```\n\n---\n\n# Data Flow Diagram\n\n```\nWeb App (TanStack Start):\n  Route Loader → Server Function (createServerFn) → api-client (api.guides.*) → API Server\n  Component UI → Route.useLoaderData()              ← typed data\n\nExtension App (WXT \u002F SPA):\n  Background\u002FScript → api.* from @repo\u002Fapi-client → API Server\n  Component → use*() Hook from @repo\u002Fapi-client   → API Server\n```\n\n---\n\n# Generic Component\n\nUse a simple, flat structure for generic components:\n\n```typescript\n\u002F\u002F Generic Component\ntype Props = {\n  title: string;\n  description: string;\n  disabled?: boolean;\n  onClick: () => void;\n};\n\nfunction ActionButton({ title, description, disabled, onClick }: Props) {\n  return (\n    \u003Cbutton disabled={disabled} onClick={onClick}>\n      \u003Cspan>{title}\u003C\u002Fspan>\n      \u003Cp>{description}\u003C\u002Fp>\n    \u003C\u002Fbutton>\n  );\n}\n```\n\n---\n\n# Generic Hook\n\nAlways co-locate hooks with the feature they serve:\n\n```typescript\n\u002F\u002F hooks\u002Fuse-guide-mutations.ts\nimport { useMutation, useQueryClient } from \"@tanstack\u002Freact-query\";\n\nimport { api } from \"@repo\u002Fapi-client\";\n\nexport function usePublishGuide() {\n  const queryClient = useQueryClient();\n\n  return useMutation({\n    mutationFn: (guideId: string) => api.guides.publishGuide(guideId),\n    onSuccess: () => {\n      queryClient.invalidateQueries({ queryKey: [\"guides\"] });\n      showToastSuccess(\"Guide published\");\n    },\n    onError: (error: any) => {\n      showToastError(\"Error\", error.message);\n    },\n  });\n}\n```\n\n---\n\n# Using TanStack Start Forms\n\nForms use TanStack Form with Zod:\n\n```typescript\nimport { useForm } from \"@tanstack\u002Freact-form\";\nimport { z } from \"zod\";\n\nconst formSchema = z.object({\n  title: z.string().min(1, \"Title is required\"),\n  description: z.string().optional(),\n});\n\nfunction CreateGuideForm() {\n  const form = useForm({\n    validators: { onChange: formSchema },\n    defaultValues: { title: \"\", description: \"\" },\n    onSubmit: async ({ value }) => {\n      try {\n        await createGuide({ data: value });\n        form.reset();\n      } catch (error: any) {\n        showToastError(\"Error\", error.message);\n      }\n    },\n  });\n\n  return (\n    \u003Cform onSubmit={(e) => { e.preventDefault(); form.handleSubmit(); }}>\n      {\u002F* fields *\u002F}\n    \u003C\u002Fform>\n  );\n}\n```\n\n---\n\n# Rules Summary\n\n### ✅ DO\n- Use route loaders for initial data (web app)\n- Use `createServerFn` to wrap `@repo\u002Fapi-client` calls (web app)\n- Use `@repo\u002Fapi-client` directly (`api.*` and hooks) for the extension app\n- Import types from `@repo\u002Fapi-client`\n- Use `try\u002Fcatch` with toast for error handling\n- Use TanStack Form with Zod for form validation\n- Use Shadcn UI primitives\n- Co-locate hooks with features\n\n### ❌ DON'T\n- Don't use `useEffect` for data fetching\n- Don't import from `@repo\u002Fapi-client` directly in web app client components — use server functions\n- Don't create manual `http-{domain}.service.ts` files for endpoints covered by api-client\n- Don't bypass route loaders for initial data\n- Don't manually type what `z.infer` or `@repo\u002Fapi-client` types already provide\n- Don't put API calls directly in components\n","# React Components\n\n## When to use this skill\n\nUse this skill ONLY when:\n\n* Writing React components inside an app\n* Refactoring React UI code\n* Reviewing React components\n* Building UI features using TanStack Start\n\nDo NOT use for:\n\n* Backend architecture design\n* API design\n* Build tooling or infra\n* Non-UI server logic\n\n---\n\n# Core Rules\n\n1. Components must follow SOLID principles\n2. Components must stay small and focused\n3. Data fetching must follow TanStack Start patterns (loaders + server functions) for the web app, or `@repo\u002Fapi-client` auto-generated hooks for the extension app\n4. Never use `useEffect` for data fetching\n5. Business logic must be extracted into hooks\n6. Composition is preferred over configuration\n7. Components must be easy to read and test\n8. Always use Shadcn UI primitives for UI consistency and accessibility\n\n---\n\n# Data Fetching Architecture (IMPORTANT)\n\nTanStack Start uses a hybrid data model, combined with `@repo\u002Fapi-client`:\n\n## 1. Route Loaders (Server-first, initial data)\n\nUse loaders for:\n\n* Initial page data\n* SEO-critical content\n* Data required before render\n* Avoiding loading states on first paint\n\nRoute loaders call either **server functions** (preferred) or **`@repo\u002Fapi-client` directly**:\n\n```typescript\n\u002F\u002F routes\u002Fguides\u002Findex.tsx\nimport { createFileRoute } from \"@tanstack\u002Freact-router\";\nimport { getAllGuides } from \"@\u002Fserver-fns\u002Fguides\";\n\u002F\u002F OR: import { api } from \"@repo\u002Fapi-client\";\n\nexport const Route = createFileRoute(\"\u002Fguides\u002F\")({\n  loader: async () => {\n    \u002F\u002F ✅ DO — Call server function (preferred)\n    const guides = await getAllGuides();\n    \u002F\u002F OR call api-client directly for simple cases:\n    \u002F\u002F const guides = await api.guides.getAllGuides();\n    return { guides };\n  },\n  component: GuidesPage,\n});\n```\n\n### Consuming loader data\n\n```typescript\nfunction GuidesPage() {\n  const { guides } = Route.useLoaderData();\n\n  return (\n    \u003Cdiv>\n      {guides.map(guide => (\n        \u003CGuideCard key={guide.id} guide={guide} \u002F>\n      ))}\n    \u003C\u002Fdiv>\n  );\n}\n```\n\n---\n\n## 2. Server Functions (TanStack Start `createServerFn`)\n\nServer functions wrap `@repo\u002Fapi-client` calls and are the primary data access pattern:\n\n```typescript\n\u002F\u002F server-fns\u002Fguides.ts\nimport { createServerFn } from \"@tanstack\u002Freact-start\";\nimport { api } from \"@repo\u002Fapi-client\";\n\nexport const getAllGuides = createServerFn({ method: \"GET\" })\n  .handler(async () => {\n    const { data, status } = await api.guides.getAllGuides();\n    if (status !== 200) {\n      throw new Error(\"Failed to fetch guides\");\n    }\n    return data.guides;\n  });\n\nexport const createGuide = createServerFn({ method: \"POST\" })\n  .inputValidator((input: { title: string; description?: string }) => input)\n  .handler(async ({ data }) => {\n    const response = await api.guides.createGuide({\n      title: data.title,\n      description: data.description ?? null,\n    });\n    if (response.status !== 201 || !response.data?.guide) {\n      return null;\n    }\n    return response.data.guide;\n  });\n```\n\nServer functions:\n- Run on the server (not exposed to the client bundle)\n- Accept typed inputs via `.inputValidator()`\n- Return typed data (types come from `@repo\u002Fapi-client`)\n- Are called from route loaders or from client components\n\n---\n\n## 3. Client-side Mutations (Web App)\n\nFor mutations triggered by user actions, call server functions directly in event handlers:\n\n```typescript\nfunction CreateGuideForm() {\n  const navigate = Route.useNavigate();\n\n  const handleSubmit = async (data: { title: string; description?: string }) => {\n    try {\n      const guide = await createGuide({ data });\n      if (guide) {\n        navigate({ to: `\u002Fguides\u002F${guide.id}` });\n        showToastSuccess(\"Guide created\");\n      }\n    } catch (error: any) {\n      showToastError(\"Error\", error.message ?? \"Failed to create guide\");\n    }\n  };\n\n  return \u003CForm onSubmit={handleSubmit} \u002F>;\n}\n```\n\nFor TanStack Query-based mutations (with cache invalidation), use `useMutation`:\n\n```typescript\nimport { useMutation, useQueryClient } from \"@tanstack\u002Freact-query\";\nimport { createGuide } from \"@\u002Fserver-fns\u002Fguides\";\n\nfunction useCreateGuideMutation() {\n  const queryClient = useQueryClient();\n  const navigate = Route.useNavigate();\n\n  return useMutation({\n    mutationFn: (data: { title: string; description?: string }) =>\n      createGuide({ data }),\n    onSuccess: (guide) => {\n      queryClient.invalidateQueries({ queryKey: [\"guides\"] });\n      navigate({ to: `\u002Fguides\u002F${guide.id}` });\n    },\n  });\n}\n```\n\n---\n\n## 4. Extension App: `@repo\u002Fapi-client` Directly\n\nThe extension app uses `@repo\u002Fapi-client` directly. Use `api.*` for programmatic calls (background scripts, services) and auto-generated hooks for React components:\n\n```typescript\n\u002F\u002F ✅ DO — Programmatic calls (background scripts, etc.)\nimport { api } from \"@repo\u002Fapi-client\";\n\nasync function archiveGuide(guideId: string) {\n  const response = await api.guides.archiveGuide(guideId);\n  if (response.status !== 200 || !response.data?.guide) {\n    return null;\n  }\n  return response.data.guide;\n}\n\n\u002F\u002F ✅ DO — Auto-generated hooks for React components\nimport { useGetAllGuides, useCreateGuide } from \"@repo\u002Fapi-client\";\n\nfunction GuideList() {\n  const { data, isLoading, error } = useGetAllGuides();\n  const createMutation = useCreateGuide({\n    mutation: {\n      onSuccess: () => {\n        showToastSuccess(\"Guide created\");\n      },\n    },\n  });\n\n  if (isLoading) return \u003CSpinner \u002F>;\n  if (error) return \u003CErrorDisplay error={error} \u002F>;\n\n  return (\n    \u003Cdiv>\n      {data?.guides?.map(guide => (\n        \u003CGuideCard key={guide.id} guide={guide} \u002F>\n      ))}\n      \u003Cbutton onClick={() => createMutation.mutate({ data: { title: \"New\" } })}>\n        Create Guide\n      \u003C\u002Fbutton>\n    \u003C\u002Fdiv>\n  );\n}\n```\n\n---\n\n# Data Flow Diagram\n\n```\nWeb App (TanStack Start):\n  Route Loader → Server Function (createServerFn) → api-client (api.guides.*) → API Server\n  Component UI → Route.useLoaderData()              ← typed data\n\nExtension App (WXT \u002F SPA):\n  Background\u002FScript → api.* from @repo\u002Fapi-client → API Server\n  Component → use*() Hook from @repo\u002Fapi-client   → API Server\n```\n\n---\n\n# Generic Component\n\nUse a simple, flat structure for generic components:\n\n```typescript\n\u002F\u002F Generic Component\ntype Props = {\n  title: string;\n  description: string;\n  disabled?: boolean;\n  onClick: () => void;\n};\n\nfunction ActionButton({ title, description, disabled, onClick }: Props) {\n  return (\n    \u003Cbutton disabled={disabled} onClick={onClick}>\n      \u003Cspan>{title}\u003C\u002Fspan>\n      \u003Cp>{description}\u003C\u002Fp>\n    \u003C\u002Fbutton>\n  );\n}\n```\n\n---\n\n# Generic Hook\n\nAlways co-locate hooks with the feature they serve:\n\n```typescript\n\u002F\u002F hooks\u002Fuse-guide-mutations.ts\nimport { useMutation, useQueryClient } from \"@tanstack\u002Freact-query\";\n\nimport { api } from \"@repo\u002Fapi-client\";\n\nexport function usePublishGuide() {\n  const queryClient = useQueryClient();\n\n  return useMutation({\n    mutationFn: (guideId: string) => api.guides.publishGuide(guideId),\n    onSuccess: () => {\n      queryClient.invalidateQueries({ queryKey: [\"guides\"] });\n      showToastSuccess(\"Guide published\");\n    },\n    onError: (error: any) => {\n      showToastError(\"Error\", error.message);\n    },\n  });\n}\n```\n\n---\n\n# Using TanStack Start Forms\n\nForms use TanStack Form with Zod:\n\n```typescript\nimport { useForm } from \"@tanstack\u002Freact-form\";\nimport { z } from \"zod\";\n\nconst formSchema = z.object({\n  title: z.string().min(1, \"Title is required\"),\n  description: z.string().optional(),\n});\n\nfunction CreateGuideForm() {\n  const form = useForm({\n    validators: { onChange: formSchema },\n    defaultValues: { title: \"\", description: \"\" },\n    onSubmit: async ({ value }) => {\n      try {\n        await createGuide({ data: value });\n        form.reset();\n      } catch (error: any) {\n        showToastError(\"Error\", error.message);\n      }\n    },\n  });\n\n  return (\n    \u003Cform onSubmit={(e) => { e.preventDefault(); form.handleSubmit(); }}>\n      {\u002F* fields *\u002F}\n    \u003C\u002Fform>\n  );\n}\n```\n\n---\n\n# Rules Summary\n\n### ✅ DO\n- Use route loaders for initial data (web app)\n- Use `createServerFn` to wrap `@repo\u002Fapi-client` calls (web app)\n- Use `@repo\u002Fapi-client` directly (`api.*` and hooks) for the extension app\n- Import types from `@repo\u002Fapi-client`\n- Use `try\u002Fcatch` with toast for error handling\n- Use TanStack Form with Zod for form validation\n- Use Shadcn UI primitives\n- Co-locate hooks with features\n\n### ❌ DON'T\n- Don't use `useEffect` for data fetching\n- Don't import from `@repo\u002Fapi-client` directly in web app client components — use server functions\n- Don't create manual `http-{domain}.service.ts` files for endpoints covered by api-client\n- Don't bypass route loaders for initial data\n- Don't manually type what `z.infer` or `@repo\u002Fapi-client` types already provide\n- Don't put API calls directly in components\n",{"name":5,"description":7},"main","f06510bcaf955afc66bbbc1606871e1a1576492e",".agents\u002Fskills\u002Ffrontend\u002Freact-components",0,"https:\u002F\u002Fgithub.com\u002FCliqRelay\u002Fcliqrelay","https:\u002F\u002Fcliqrelay.com","https:\u002F\u002Fgithub.com\u002FCliqRelay","Capture and refine workflows instantly to help your teams and AI agents perform at their best.","2026-11-04 22:56:05",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add CliqRelay\u002Fcliqrelay --skill react-components",{"tool":38,"command":39},"bunx","bunx skills add CliqRelay\u002Fcliqrelay --skill react-components",{"tool":41,"command":42},"pnpm","pnpm dlx skills add CliqRelay\u002Fcliqrelay --skill react-components","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FCliqRelay\u002Fcliqrelay\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ffrontend\u002Freact-components\u002FSKILL.md",true,[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":18},"01M758WG0JG18W5MZD6ZPM6PGG","typst","Typst document creation and package development. Use when: (1) Working with .typ files, (2) User mentions typst, typst.toml, or typst-cli, (3) Creating or using Typst packages, (4) Developing document templates, (5) Converting Markdown\u002FLaTeX to Typst","https:\u002F\u002Fgithub.com\u002FCliqRelay\u002Fcliqrelay\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftypst\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":18},"01M758WACKQMHG2BFF7T758J12","shadcn","Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI. 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\", or \"switch to --preset\".","https:\u002F\u002Fgithub.com\u002FCliqRelay\u002Fcliqrelay\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fshadcn\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":18},"01M758W82G2QQ5Q14FKYNHRXQW","handoff","Compact the current conversation into a handoff document for another agent to pick up.","https:\u002F\u002Fgithub.com\u002FCliqRelay\u002Fcliqrelay\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fproductivity\u002Fhandoff\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":18},"01M758W63H60EK55A93199B6NR","grilling","Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.","https:\u002F\u002Fgithub.com\u002FCliqRelay\u002Fcliqrelay\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fproductivity\u002Fgrilling\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":18},"01M758W4HD4PF66929V7MDGKW8","grill-me","A relentless interview to sharpen a plan or design.","https:\u002F\u002Fgithub.com\u002FCliqRelay\u002Fcliqrelay\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fproductivity\u002Fgrill-me\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":18},"01M758VYC5CCTP7EA5VKE7YWM5","dont-waffle","Use this skill when answering questions, explaining concepts, writing technical responses, reviewing code, or helping with development tasks. Communicate in clear, simple, standard English. Keep answers concise and focused, remove unnecessary filler and repetition, explain technical ideas in plain language, and structure information so it is easy to read and understand. When showing code, present it clearly with enough context for the developer to understand what it does and where it belongs.","https:\u002F\u002Fgithub.com\u002FCliqRelay\u002Fcliqrelay\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fproductivity\u002Fdont-waffle\u002FSKILL.md",[],[]]