[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BV2TT3NR94MP64VB2A1WVT":3,"skill-same:01M7BV2TT3NR94MP64VB2A1WVT":62},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":30,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7BV2TT3NR94MP64VB2A1WVT","server-components",null,"This skill should be used when the user asks about \"Server Components\", \"Client Components\", \"'use client' directive\", \"when to use server vs client\", \"RSC patterns\", \"component composition\", \"data fetching in components\", or needs guidance on React Server Components architecture in Next.js.","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-Plugin-插件协议\u002FYYC3-Plugin-插件协议-external_plugins\u002Fnextjs-expert\u002Fskills\u002Fserver-components\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: server-components\ndescription: This skill should be used when the user asks about \"Server Components\", \"Client Components\", \"'use client' directive\", \"when to use server vs client\", \"RSC patterns\", \"component composition\", \"data fetching in components\", or needs guidance on React Server Components architecture in Next.js.\nversion: 1.0.0\n---\n\n# React Server Components in Next.js\n\n## Overview\n\nReact Server Components (RSC) allow components to render on the server, reducing client-side JavaScript and enabling direct data access. In Next.js App Router, all components are Server Components by default.\n\n## Server vs Client Components\n\n### Server Components (Default)\n\nServer Components run only on the server:\n\n```tsx\n\u002F\u002F app\u002Fusers\u002Fpage.tsx (Server Component - default)\nasync function UsersPage() {\n  const users = await db.user.findMany() \u002F\u002F Direct DB access\n\n  return (\n    \u003Cul>\n      {users.map(user => (\n        \u003Cli key={user.id}>{user.name}\u003C\u002Fli>\n      ))}\n    \u003C\u002Ful>\n  )\n}\n```\n\n**Benefits:**\n- Direct database\u002Ffilesystem access\n- Keep sensitive data on server (API keys, tokens)\n- Reduce client bundle size\n- Automatic code splitting\n\n### Client Components\n\nAdd `'use client'` directive for interactivity:\n\n```tsx\n\u002F\u002F components\u002Fcounter.tsx\n'use client'\n\nimport { useState } from 'react'\n\nexport function Counter() {\n  const [count, setCount] = useState(0)\n\n  return (\n    \u003Cbutton onClick={() => setCount(count + 1)}>\n      Count: {count}\n    \u003C\u002Fbutton>\n  )\n}\n```\n\n**Use Client Components for:**\n- `useState`, `useEffect`, `useReducer`\n- Event handlers (`onClick`, `onChange`)\n- Browser APIs (`window`, `document`)\n- Custom hooks with state\n\n## The Mental Model\n\nThink of the component tree as having a \"client boundary\":\n\n```\nServer Component (page.tsx)\n├── Server Component (header.tsx)\n├── Client Component ('use client') ← boundary\n│   ├── Client Component (child)\n│   └── Client Component (child)\n└── Server Component (footer.tsx)\n```\n\n**Key rules:**\n1. Server Components can import Client Components\n2. Client Components cannot import Server Components\n3. You can pass Server Components as `children` to Client Components\n\n## Composition Patterns\n\n### Pattern 1: Server Data → Client Interactivity\n\nFetch data in Server Component, pass to Client:\n\n```tsx\n\u002F\u002F app\u002Fproducts\u002Fpage.tsx (Server)\nimport { ProductList } from '.\u002Fproduct-list'\n\nexport default async function ProductsPage() {\n  const products = await getProducts()\n  return \u003CProductList products={products} \u002F>\n}\n\n\u002F\u002F app\u002Fproducts\u002Fproduct-list.tsx (Client)\n'use client'\n\nexport function ProductList({ products }: { products: Product[] }) {\n  const [filter, setFilter] = useState('')\n\n  const filtered = products.filter(p =>\n    p.name.includes(filter)\n  )\n\n  return (\n    \u003C>\n      \u003Cinput onChange={e => setFilter(e.target.value)} \u002F>\n      {filtered.map(p => \u003CProductCard key={p.id} product={p} \u002F>)}\n    \u003C\u002F>\n  )\n}\n```\n\n### Pattern 2: Children as Server Components\n\nPass Server Components through children prop:\n\n```tsx\n\u002F\u002F components\u002Fclient-wrapper.tsx\n'use client'\n\nexport function ClientWrapper({ children }: { children: React.ReactNode }) {\n  const [isOpen, setIsOpen] = useState(false)\n\n  return (\n    \u003Cdiv>\n      \u003Cbutton onClick={() => setIsOpen(!isOpen)}>Toggle\u003C\u002Fbutton>\n      {isOpen && children} {\u002F* Server Component content *\u002F}\n    \u003C\u002Fdiv>\n  )\n}\n\n\u002F\u002F app\u002Fpage.tsx (Server)\nimport { ClientWrapper } from '@\u002Fcomponents\u002Fclient-wrapper'\nimport { ServerContent } from '@\u002Fcomponents\u002Fserver-content'\n\nexport default function Page() {\n  return (\n    \u003CClientWrapper>\n      \u003CServerContent \u002F> {\u002F* Renders on server! *\u002F}\n    \u003C\u002FClientWrapper>\n  )\n}\n```\n\n### Pattern 3: Slots for Complex Layouts\n\nUse multiple children slots:\n\n```tsx\n\u002F\u002F components\u002Fdashboard-shell.tsx\n'use client'\n\ninterface Props {\n  sidebar: React.ReactNode\n  main: React.ReactNode\n}\n\nexport function DashboardShell({ sidebar, main }: Props) {\n  const [collapsed, setCollapsed] = useState(false)\n\n  return (\n    \u003Cdiv className=\"flex\">\n      {!collapsed && \u003Caside>{sidebar}\u003C\u002Faside>}\n      \u003Cmain>{main}\u003C\u002Fmain>\n    \u003C\u002Fdiv>\n  )\n}\n```\n\n## Data Fetching\n\n### Async Server Components\n\nServer Components can be async:\n\n```tsx\n\u002F\u002F app\u002Fposts\u002Fpage.tsx\nexport default async function PostsPage() {\n  const posts = await fetch('https:\u002F\u002Fapi.example.com\u002Fposts')\n    .then(res => res.json())\n\n  return (\n    \u003Cul>\n      {posts.map(post => (\n        \u003Cli key={post.id}>{post.title}\u003C\u002Fli>\n      ))}\n    \u003C\u002Ful>\n  )\n}\n```\n\n### Parallel Data Fetching\n\nFetch multiple resources in parallel:\n\n```tsx\nexport default async function DashboardPage() {\n  const [user, posts, analytics] = await Promise.all([\n    getUser(),\n    getPosts(),\n    getAnalytics(),\n  ])\n\n  return (\n    \u003CDashboard user={user} posts={posts} analytics={analytics} \u002F>\n  )\n}\n```\n\n### Streaming with Suspense\n\nStream slow components:\n\n```tsx\nimport { Suspense } from 'react'\n\nexport default function Page() {\n  return (\n    \u003Cdiv>\n      \u003CHeader \u002F> {\u002F* Renders immediately *\u002F}\n      \u003CSuspense fallback={\u003CPostsSkeleton \u002F>}>\n        \u003CSlowPosts \u002F> {\u002F* Streams when ready *\u002F}\n      \u003C\u002FSuspense>\n    \u003C\u002Fdiv>\n  )\n}\n```\n\n## Decision Guide\n\n**Use Server Component when:**\n- Fetching data\n- Accessing backend resources\n- Keeping sensitive info on server\n- Reducing client JavaScript\n- Component has no interactivity\n\n**Use Client Component when:**\n- Using state (`useState`, `useReducer`)\n- Using effects (`useEffect`)\n- Using event listeners\n- Using browser APIs\n- Using custom hooks with state\n\n## Common Mistakes\n\n1. **Don't** add `'use client'` unnecessarily - it increases bundle size\n2. **Don't** try to import Server Components into Client Components\n3. **Do** serialize data at boundaries (no functions, classes, or dates)\n4. **Do** use the children pattern for composition\n\n## Resources\n\nFor detailed patterns, see:\n- `references\u002Fserver-vs-client.md` - Complete comparison guide\n- `references\u002Fcomposition-patterns.md` - Advanced composition\n- `examples\u002Fdata-fetching-patterns.md` - Data fetching examples\n","# React Server Components in Next.js\n\n## Overview\n\nReact Server Components (RSC) allow components to render on the server, reducing client-side JavaScript and enabling direct data access. In Next.js App Router, all components are Server Components by default.\n\n## Server vs Client Components\n\n### Server Components (Default)\n\nServer Components run only on the server:\n\n```tsx\n\u002F\u002F app\u002Fusers\u002Fpage.tsx (Server Component - default)\nasync function UsersPage() {\n  const users = await db.user.findMany() \u002F\u002F Direct DB access\n\n  return (\n    \u003Cul>\n      {users.map(user => (\n        \u003Cli key={user.id}>{user.name}\u003C\u002Fli>\n      ))}\n    \u003C\u002Ful>\n  )\n}\n```\n\n**Benefits:**\n- Direct database\u002Ffilesystem access\n- Keep sensitive data on server (API keys, tokens)\n- Reduce client bundle size\n- Automatic code splitting\n\n### Client Components\n\nAdd `'use client'` directive for interactivity:\n\n```tsx\n\u002F\u002F components\u002Fcounter.tsx\n'use client'\n\nimport { useState } from 'react'\n\nexport function Counter() {\n  const [count, setCount] = useState(0)\n\n  return (\n    \u003Cbutton onClick={() => setCount(count + 1)}>\n      Count: {count}\n    \u003C\u002Fbutton>\n  )\n}\n```\n\n**Use Client Components for:**\n- `useState`, `useEffect`, `useReducer`\n- Event handlers (`onClick`, `onChange`)\n- Browser APIs (`window`, `document`)\n- Custom hooks with state\n\n## The Mental Model\n\nThink of the component tree as having a \"client boundary\":\n\n```\nServer Component (page.tsx)\n├── Server Component (header.tsx)\n├── Client Component ('use client') ← boundary\n│   ├── Client Component (child)\n│   └── Client Component (child)\n└── Server Component (footer.tsx)\n```\n\n**Key rules:**\n1. Server Components can import Client Components\n2. Client Components cannot import Server Components\n3. You can pass Server Components as `children` to Client Components\n\n## Composition Patterns\n\n### Pattern 1: Server Data → Client Interactivity\n\nFetch data in Server Component, pass to Client:\n\n```tsx\n\u002F\u002F app\u002Fproducts\u002Fpage.tsx (Server)\nimport { ProductList } from '.\u002Fproduct-list'\n\nexport default async function ProductsPage() {\n  const products = await getProducts()\n  return \u003CProductList products={products} \u002F>\n}\n\n\u002F\u002F app\u002Fproducts\u002Fproduct-list.tsx (Client)\n'use client'\n\nexport function ProductList({ products }: { products: Product[] }) {\n  const [filter, setFilter] = useState('')\n\n  const filtered = products.filter(p =>\n    p.name.includes(filter)\n  )\n\n  return (\n    \u003C>\n      \u003Cinput onChange={e => setFilter(e.target.value)} \u002F>\n      {filtered.map(p => \u003CProductCard key={p.id} product={p} \u002F>)}\n    \u003C\u002F>\n  )\n}\n```\n\n### Pattern 2: Children as Server Components\n\nPass Server Components through children prop:\n\n```tsx\n\u002F\u002F components\u002Fclient-wrapper.tsx\n'use client'\n\nexport function ClientWrapper({ children }: { children: React.ReactNode }) {\n  const [isOpen, setIsOpen] = useState(false)\n\n  return (\n    \u003Cdiv>\n      \u003Cbutton onClick={() => setIsOpen(!isOpen)}>Toggle\u003C\u002Fbutton>\n      {isOpen && children} {\u002F* Server Component content *\u002F}\n    \u003C\u002Fdiv>\n  )\n}\n\n\u002F\u002F app\u002Fpage.tsx (Server)\nimport { ClientWrapper } from '@\u002Fcomponents\u002Fclient-wrapper'\nimport { ServerContent } from '@\u002Fcomponents\u002Fserver-content'\n\nexport default function Page() {\n  return (\n    \u003CClientWrapper>\n      \u003CServerContent \u002F> {\u002F* Renders on server! *\u002F}\n    \u003C\u002FClientWrapper>\n  )\n}\n```\n\n### Pattern 3: Slots for Complex Layouts\n\nUse multiple children slots:\n\n```tsx\n\u002F\u002F components\u002Fdashboard-shell.tsx\n'use client'\n\ninterface Props {\n  sidebar: React.ReactNode\n  main: React.ReactNode\n}\n\nexport function DashboardShell({ sidebar, main }: Props) {\n  const [collapsed, setCollapsed] = useState(false)\n\n  return (\n    \u003Cdiv className=\"flex\">\n      {!collapsed && \u003Caside>{sidebar}\u003C\u002Faside>}\n      \u003Cmain>{main}\u003C\u002Fmain>\n    \u003C\u002Fdiv>\n  )\n}\n```\n\n## Data Fetching\n\n### Async Server Components\n\nServer Components can be async:\n\n```tsx\n\u002F\u002F app\u002Fposts\u002Fpage.tsx\nexport default async function PostsPage() {\n  const posts = await fetch('https:\u002F\u002Fapi.example.com\u002Fposts')\n    .then(res => res.json())\n\n  return (\n    \u003Cul>\n      {posts.map(post => (\n        \u003Cli key={post.id}>{post.title}\u003C\u002Fli>\n      ))}\n    \u003C\u002Ful>\n  )\n}\n```\n\n### Parallel Data Fetching\n\nFetch multiple resources in parallel:\n\n```tsx\nexport default async function DashboardPage() {\n  const [user, posts, analytics] = await Promise.all([\n    getUser(),\n    getPosts(),\n    getAnalytics(),\n  ])\n\n  return (\n    \u003CDashboard user={user} posts={posts} analytics={analytics} \u002F>\n  )\n}\n```\n\n### Streaming with Suspense\n\nStream slow components:\n\n```tsx\nimport { Suspense } from 'react'\n\nexport default function Page() {\n  return (\n    \u003Cdiv>\n      \u003CHeader \u002F> {\u002F* Renders immediately *\u002F}\n      \u003CSuspense fallback={\u003CPostsSkeleton \u002F>}>\n        \u003CSlowPosts \u002F> {\u002F* Streams when ready *\u002F}\n      \u003C\u002FSuspense>\n    \u003C\u002Fdiv>\n  )\n}\n```\n\n## Decision Guide\n\n**Use Server Component when:**\n- Fetching data\n- Accessing backend resources\n- Keeping sensitive info on server\n- Reducing client JavaScript\n- Component has no interactivity\n\n**Use Client Component when:**\n- Using state (`useState`, `useReducer`)\n- Using effects (`useEffect`)\n- Using event listeners\n- Using browser APIs\n- Using custom hooks with state\n\n## Common Mistakes\n\n1. **Don't** add `'use client'` unnecessarily - it increases bundle size\n2. **Don't** try to import Server Components into Client Components\n3. **Do** serialize data at boundaries (no functions, classes, or dates)\n4. **Do** use the children pattern for composition\n\n## Resources\n\nFor detailed patterns, see:\n- `references\u002Fserver-vs-client.md` - Complete comparison guide\n- `references\u002Fcomposition-patterns.md` - Advanced composition\n- `examples\u002Fdata-fetching-patterns.md` - Data fetching examples\n",{"name":5,"version":24,"description":7},"1.0.0","main","87afe6ce96220accf50a345dea46784c8c9f210e","YYC3-Plugin-插件协议\u002FYYC3-Plugin-插件协议-external_plugins\u002Fnextjs-expert\u002Fskills\u002Fserver-components",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":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill server-components",{"tool":40,"command":41},"bunx","bunx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill server-components",{"tool":43,"command":44},"pnpm","pnpm dlx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill server-components","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Plugin-插件协议\u002FYYC3-Plugin-插件协议-external_plugins\u002Fnextjs-expert\u002Fskills\u002Fserver-components\u002FSKILL.md",true,[48,54,58],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"examples\u002Fdata-fetching-patterns.md","REFERENCE","参考文档",8787,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Plugin-插件协议\u002FYYC3-Plugin-插件协议-external_plugins\u002Fnextjs-expert\u002Fskills\u002Fserver-components\u002Fexamples\u002Fdata-fetching-patterns.md",{"path":55,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002Fcomposition-patterns.md",8483,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Plugin-插件协议\u002FYYC3-Plugin-插件协议-external_plugins\u002Fnextjs-expert\u002Fskills\u002Fserver-components\u002Freferences\u002Fcomposition-patterns.md",{"path":59,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":60,"sourceHtmlUrl":61},"references\u002Fserver-vs-client.md",7431,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Plugin-插件协议\u002FYYC3-Plugin-插件协议-external_plugins\u002Fnextjs-expert\u002Fskills\u002Fserver-components\u002Freferences\u002Fserver-vs-client.md",[63,70,77,84,91,98],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"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":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"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":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"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":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"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":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"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":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"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",[],[]]