[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7C4PWR7WPHS9FPXN2W8MM2N":3,"skill-same:01M7C4PWR7WPHS9FPXN2W8MM2N":84},{"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},"01M7C4PWR7WPHS9FPXN2W8MM2N","swiftui-performance-audit",null,"Audit SwiftUI performance issues from code review and profiling evidence.","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\u002Fswiftui-performance-audit\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: swiftui-performance-audit\ndescription: Audit SwiftUI performance issues from code review and profiling evidence.\nrisk: safe\nsource: \"Dimillian\u002FSkills (MIT)\"\ndate_added: \"2026-03-25\"\n---\n\n# SwiftUI Performance Audit\n\n## Quick start\n\nUse this skill to diagnose SwiftUI performance issues from code first, then request profiling evidence when code review alone cannot explain the symptoms.\n\n## When to Use\n- When the user reports slow rendering, janky scrolling, layout thrash, or high CPU in SwiftUI.\n- When you need a code-first audit plus Instruments guidance if profiling evidence is required.\n\n## Workflow\n\n1. Classify the symptom: slow rendering, janky scrolling, high CPU, memory growth, hangs, or excessive view updates.\n2. If code is available, start with a code-first review using `references\u002Fcode-smells.md`.\n3. If code is not available, ask for the smallest useful slice: target view, data flow, reproduction steps, and deployment target.\n4. If code review is inconclusive or runtime evidence is required, guide the user through profiling with `references\u002Fprofiling-intake.md`.\n5. Summarize likely causes, evidence, remediation, and validation steps using `references\u002Freport-template.md`.\n\n## 1. Intake\n\nCollect:\n- Target view or feature code.\n- Symptoms and exact reproduction steps.\n- Data flow: `@State`, `@Binding`, environment dependencies, and observable models.\n- Whether the issue shows up on device or simulator, and whether it was observed in Debug or Release.\n\nAsk the user to classify the issue if possible:\n- CPU spike or battery drain\n- Janky scrolling or dropped frames\n- High memory or image pressure\n- Hangs or unresponsive interactions\n- Excessive or unexpectedly broad view updates\n\nFor the full profiling intake checklist, read `references\u002Fprofiling-intake.md`.\n\n## 2. Code-First Review\n\nFocus on:\n- Invalidation storms from broad observation or environment reads.\n- Unstable identity in lists and `ForEach`.\n- Heavy derived work in `body` or view builders.\n- Layout thrash from complex hierarchies, `GeometryReader`, or preference chains.\n- Large image decode or resize work on the main thread.\n- Animation or transition work applied too broadly.\n\nUse `references\u002Fcode-smells.md` for the detailed smell catalog and fix guidance.\n\nProvide:\n- Likely root causes with code references.\n- Suggested fixes and refactors.\n- If needed, a minimal repro or instrumentation suggestion.\n\n## 3. Guide the User to Profile\n\nIf code review does not explain the issue, ask for runtime evidence:\n- A trace export or screenshots of the SwiftUI timeline and Time Profiler call tree.\n- Device\u002FOS\u002Fbuild configuration.\n- The exact interaction being profiled.\n- Before\u002Fafter metrics if the user is comparing a change.\n\nUse `references\u002Fprofiling-intake.md` for the exact checklist and collection steps.\n\n## 4. Analyze and Diagnose\n\n- Map the evidence to the most likely category: invalidation, identity churn, layout thrash, main-thread work, image cost, or animation cost.\n- Prioritize problems by impact, not by how easy they are to explain.\n- Distinguish code-level suspicion from trace-backed evidence.\n- Call out when profiling is still insufficient and what additional evidence would reduce uncertainty.\n\n## 5. Remediate\n\nApply targeted fixes:\n- Narrow state scope and reduce broad observation fan-out.\n- Stabilize identities for `ForEach` and lists.\n- Move heavy work out of `body` into derived state updated from inputs, model-layer precomputation, memoized helpers, or background preprocessing. Use `@State` only for view-owned state, not as an ad hoc cache for arbitrary computation.\n- Use `equatable()` only when equality is cheaper than recomputing the subtree and the inputs are truly value-semantic.\n- Downsample images before rendering.\n- Reduce layout complexity or use fixed sizing where possible.\n\nUse `references\u002Fcode-smells.md` for examples, Observation-specific fan-out guidance, and remediation patterns.\n\n## 6. Verify\n\nAsk the user to re-run the same capture and compare with baseline metrics.\nSummarize the delta (CPU, frame drops, memory peak) if provided.\n\n## Outputs\n\nProvide:\n- A short metrics table (before\u002Fafter if available).\n- Top issues (ordered by impact).\n- Proposed fixes with estimated effort.\n\nUse `references\u002Freport-template.md` when formatting the final audit.\n\n## References\n\n- Profiling intake and collection checklist: `references\u002Fprofiling-intake.md`\n- Common code smells and remediation patterns: `references\u002Fcode-smells.md`\n- Audit output template: `references\u002Freport-template.md`\n- Add Apple documentation and WWDC resources under `references\u002F` as they are supplied by the user.\n- Optimizing SwiftUI performance with Instruments: `references\u002Foptimizing-swiftui-performance-instruments.md`\n- Understanding and improving SwiftUI performance: `references\u002Funderstanding-improving-swiftui-performance.md`\n- Understanding hangs in your app: `references\u002Funderstanding-hangs-in-your-app.md`\n- Demystify SwiftUI performance (WWDC23): `references\u002Fdemystify-swiftui-performance-wwdc23.md`\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","# SwiftUI Performance Audit\n\n## Quick start\n\nUse this skill to diagnose SwiftUI performance issues from code first, then request profiling evidence when code review alone cannot explain the symptoms.\n\n## When to Use\n- When the user reports slow rendering, janky scrolling, layout thrash, or high CPU in SwiftUI.\n- When you need a code-first audit plus Instruments guidance if profiling evidence is required.\n\n## Workflow\n\n1. Classify the symptom: slow rendering, janky scrolling, high CPU, memory growth, hangs, or excessive view updates.\n2. If code is available, start with a code-first review using `references\u002Fcode-smells.md`.\n3. If code is not available, ask for the smallest useful slice: target view, data flow, reproduction steps, and deployment target.\n4. If code review is inconclusive or runtime evidence is required, guide the user through profiling with `references\u002Fprofiling-intake.md`.\n5. Summarize likely causes, evidence, remediation, and validation steps using `references\u002Freport-template.md`.\n\n## 1. Intake\n\nCollect:\n- Target view or feature code.\n- Symptoms and exact reproduction steps.\n- Data flow: `@State`, `@Binding`, environment dependencies, and observable models.\n- Whether the issue shows up on device or simulator, and whether it was observed in Debug or Release.\n\nAsk the user to classify the issue if possible:\n- CPU spike or battery drain\n- Janky scrolling or dropped frames\n- High memory or image pressure\n- Hangs or unresponsive interactions\n- Excessive or unexpectedly broad view updates\n\nFor the full profiling intake checklist, read `references\u002Fprofiling-intake.md`.\n\n## 2. Code-First Review\n\nFocus on:\n- Invalidation storms from broad observation or environment reads.\n- Unstable identity in lists and `ForEach`.\n- Heavy derived work in `body` or view builders.\n- Layout thrash from complex hierarchies, `GeometryReader`, or preference chains.\n- Large image decode or resize work on the main thread.\n- Animation or transition work applied too broadly.\n\nUse `references\u002Fcode-smells.md` for the detailed smell catalog and fix guidance.\n\nProvide:\n- Likely root causes with code references.\n- Suggested fixes and refactors.\n- If needed, a minimal repro or instrumentation suggestion.\n\n## 3. Guide the User to Profile\n\nIf code review does not explain the issue, ask for runtime evidence:\n- A trace export or screenshots of the SwiftUI timeline and Time Profiler call tree.\n- Device\u002FOS\u002Fbuild configuration.\n- The exact interaction being profiled.\n- Before\u002Fafter metrics if the user is comparing a change.\n\nUse `references\u002Fprofiling-intake.md` for the exact checklist and collection steps.\n\n## 4. Analyze and Diagnose\n\n- Map the evidence to the most likely category: invalidation, identity churn, layout thrash, main-thread work, image cost, or animation cost.\n- Prioritize problems by impact, not by how easy they are to explain.\n- Distinguish code-level suspicion from trace-backed evidence.\n- Call out when profiling is still insufficient and what additional evidence would reduce uncertainty.\n\n## 5. Remediate\n\nApply targeted fixes:\n- Narrow state scope and reduce broad observation fan-out.\n- Stabilize identities for `ForEach` and lists.\n- Move heavy work out of `body` into derived state updated from inputs, model-layer precomputation, memoized helpers, or background preprocessing. Use `@State` only for view-owned state, not as an ad hoc cache for arbitrary computation.\n- Use `equatable()` only when equality is cheaper than recomputing the subtree and the inputs are truly value-semantic.\n- Downsample images before rendering.\n- Reduce layout complexity or use fixed sizing where possible.\n\nUse `references\u002Fcode-smells.md` for examples, Observation-specific fan-out guidance, and remediation patterns.\n\n## 6. Verify\n\nAsk the user to re-run the same capture and compare with baseline metrics.\nSummarize the delta (CPU, frame drops, memory peak) if provided.\n\n## Outputs\n\nProvide:\n- A short metrics table (before\u002Fafter if available).\n- Top issues (ordered by impact).\n- Proposed fixes with estimated effort.\n\nUse `references\u002Freport-template.md` when formatting the final audit.\n\n## References\n\n- Profiling intake and collection checklist: `references\u002Fprofiling-intake.md`\n- Common code smells and remediation patterns: `references\u002Fcode-smells.md`\n- Audit output template: `references\u002Freport-template.md`\n- Add Apple documentation and WWDC resources under `references\u002F` as they are supplied by the user.\n- Optimizing SwiftUI performance with Instruments: `references\u002Foptimizing-swiftui-performance-instruments.md`\n- Understanding and improving SwiftUI performance: `references\u002Funderstanding-improving-swiftui-performance.md`\n- Understanding hangs in your app: `references\u002Funderstanding-hangs-in-your-app.md`\n- Demystify SwiftUI performance (WWDC23): `references\u002Fdemystify-swiftui-performance-wwdc23.md`\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","Dimillian\u002FSkills (MIT)","2026-03-25","main","87afe6ce96220accf50a345dea46784c8c9f210e","YYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fplugins\u002Fantigravity-awesome-skills-claude\u002Fskills\u002Fswiftui-performance-audit",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 swiftui-performance-audit",{"tool":42,"command":43},"bunx","bunx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill swiftui-performance-audit",{"tool":45,"command":46},"pnpm","pnpm dlx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill swiftui-performance-audit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fplugins\u002Fantigravity-awesome-skills-claude\u002Fskills\u002Fswiftui-performance-audit\u002FSKILL.md",true,[50,56,60,64,68,72,76,80],{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":55},"agents\u002Fopenai.yaml","REFERENCE","参考文档",242,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fplugins\u002Fantigravity-awesome-skills-claude\u002Fskills\u002Fswiftui-performance-audit\u002Fagents\u002Fopenai.yaml",{"path":57,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":58,"sourceHtmlUrl":59},"references\u002Fcode-smells.md",3753,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fplugins\u002Fantigravity-awesome-skills-claude\u002Fskills\u002Fswiftui-performance-audit\u002Freferences\u002Fcode-smells.md",{"path":61,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":62,"sourceHtmlUrl":63},"references\u002Fdemystify-swiftui-performance-wwdc23.md",1813,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fplugins\u002Fantigravity-awesome-skills-claude\u002Fskills\u002Fswiftui-performance-audit\u002Freferences\u002Fdemystify-swiftui-performance-wwdc23.md",{"path":65,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":66,"sourceHtmlUrl":67},"references\u002Foptimizing-swiftui-performance-instruments.md",1837,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fplugins\u002Fantigravity-awesome-skills-claude\u002Fskills\u002Fswiftui-performance-audit\u002Freferences\u002Foptimizing-swiftui-performance-instruments.md",{"path":69,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":70,"sourceHtmlUrl":71},"references\u002Fprofiling-intake.md",1904,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fplugins\u002Fantigravity-awesome-skills-claude\u002Fskills\u002Fswiftui-performance-audit\u002Freferences\u002Fprofiling-intake.md",{"path":73,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":74,"sourceHtmlUrl":75},"references\u002Freport-template.md",1201,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fplugins\u002Fantigravity-awesome-skills-claude\u002Fskills\u002Fswiftui-performance-audit\u002Freferences\u002Freport-template.md",{"path":77,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002Funderstanding-hangs-in-your-app.md",1267,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fplugins\u002Fantigravity-awesome-skills-claude\u002Fskills\u002Fswiftui-performance-audit\u002Freferences\u002Funderstanding-hangs-in-your-app.md",{"path":81,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":82,"sourceHtmlUrl":83},"references\u002Funderstanding-improving-swiftui-performance.md",2262,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fplugins\u002Fantigravity-awesome-skills-claude\u002Fskills\u002Fswiftui-performance-audit\u002Freferences\u002Funderstanding-improving-swiftui-performance.md",[85,92,99,106,113,120],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"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":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"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":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"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":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"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":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"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":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":126,"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",[],[]]