[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BQE2EF70A633JDVKWH09PR":3,"skill-same:01M7BQE2EF70A633JDVKWH09PR":49},{"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":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":31,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M7BQE2EF70A633JDVKWH09PR","clickhouse-pr-description",null,"Generate PR descriptions for ClickHouse\u002FClickHouse that match maintainer expectations. Use when creating or updating PR descriptions.","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-Data-数据存储\u002FYYC3-Data-数据存储-ClickHouse\u002F.claude\u002Fskills\u002Fclickhouse-pr-description\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: clickhouse-pr-description\ndescription: Generate PR descriptions for ClickHouse\u002FClickHouse that match maintainer expectations. Use when creating or updating PR descriptions.\nargument-hint: \"[PR-number or branch-name]\"\ndisable-model-invocation: false\nallowed-tools: Task, Bash(gh:*), Bash(git:*), Read, Glob, Grep, AskUserQuestion\n---\n\n# ClickHouse PR Description Skill\n\nGenerate a good PR description and apply it, with optional confirmation based on user preference.\n\n## Title\n\nPlain description of what changed. No prefix conventions like `fix():` or `feat():`.\n\n- Good: `Change default stderr_reaction to log_last for executable UDFs`\n- Good: `Fix exception when inserting NULL into non-nullable column via CAST`\n- Bad: `fix(udf): Change default stderr_reaction` — conventional commits, ClickHouse doesn't use them\n- Bad: `Fuzzer fixes` — too vague, tells the reviewer nothing\n- Bad: `Improve error handling and enrich exit code exceptions with stderr context` — too vague, doesn't say what was actually changed\n\n## Body\n\nRead `.github\u002FPULL_REQUEST_TEMPLATE.md` for the exact template structure.\n\nA good PR description has two parts:\n\n**1. Free-form context (above the template, optional but encouraged for non-trivial changes)**\n\nExplain to a future reader: what was the problem, why did it need fixing, what approach was taken, what were the results or trade-offs. This is the right place for:\n- Motivation and background\n- Description of the approach and why it was chosen over alternatives\n- Benchmark results or measurements\n- Links to related issues, discussions, or previous attempts\n- Any caveats or known limitations\n\nUse plain paragraphs. Headers like `## Motivation`, `## Changes`, `## Results` are fine and helpful — they make the PR easier to navigate for reviewers. Bullet lists are fine. Be as detailed as needed.\n\n**2. Template section (mandatory)**\n\nFill in the changelog category (delete the rest of the list), write the changelog entry, and keep the documentation checkbox.\n\n**Exception — CI Fix or Improvement:** omit the Changelog entry and Documentation entry sections entirely (they are not required). Keep the entire PR body under 100 words.\n\n### Example of a well-written body\n\nFrom [#96110](https:\u002F\u002Fgithub.com\u002FClickHouse\u002FClickHouse\u002Fpull\u002F96110):\n\n```\n### Changelog category (leave one):\n- Backward Incompatible Change\n\n### Changelog entry:\nThe semantics of the `do_not_merge_across_partitions_select_final` setting were\nmade more obvious. Previously, the feature could be automatically enabled when\nthe setting was not explicitly set in the configs. It caused confusion repeatedly\nand, unfortunately, led to some issues in production. Now, the rules are simpler:\n`do_not_merge_across_partitions_select_final=1` enables the functionality\nunconditionally. If `do_not_merge_across_partitions_select_final=0`, then automatic\nis used only if the new setting\n`enable_automatic_decision_for_merging_across_partitions_for_final=1` and not used\notherwise. To preserve the old behaviour as much as possible, the defaults were set\nto `do_not_merge_across_partitions_select_final=0` and\n`enable_automatic_decision_for_merging_across_partitions_for_final=1`.\n\n### Documentation entry for user-facing changes\n- [ ] Documentation is written (mandatory for new features)\n\n---\n\nThe backward-incompatible part is that if someone has\n`do_not_merge_across_partitions_select_final=0` explicitly set in the configs,\nit no longer protects against the use of automatics. I'm open to discussion on\nwhether we should conservatively default to disabled automatics.\n```\n\nNote: extra context after `---` is fine — reviewers see it, but only the changelog entry above the blank line goes into the CHANGELOG.\n\n## Changelog entry guidelines\n\nThe entry is what ends up in the published CHANGELOG. Write it for a user who is upgrading and scanning for what affects them. The PR link and author attribution are appended automatically by tooling — do not include them.\n\n**Format:** the changelog script (`tests\u002Fci\u002Fchangelog.py`) collects all lines after the `### Changelog entry:` header up to the first blank line, then joins them with spaces into a single string. This means:\n- The entry can span multiple lines in the template — they become one paragraph\n- A blank line terminates collection — anything after it is ignored\n- Write it as a single paragraph (no bullet lists, no blank lines within)\n\n**Tense:** mixed is fine and natural. \"Added X\", \"Fix a case where...\", \"The `X` setting is now Y\" are all real examples from the CHANGELOG. Don't force everything into present tense.\n\n**Length:** match the impact. A small new function can be one sentence. A changed default or backward-incompatible behavior warrants as many sentences as needed, including what users must do to adapt.\n\n**Specificity:** always name the exact thing that changed. Never write \"Fix a bug\" or \"Improve performance\" without saying what specifically.\n\n**For backward-incompatible changes:** always explain the old behavior, the new behavior, and how to restore the old one if possible.\n\n**Real examples from the ClickHouse CHANGELOG:**\n\nOne sentence, sufficient for a focused addition:\n> Add `xxh3_128` hashing function.\n\nOne sentence with enough context:\n> `DATE` columns from PostgreSQL are now inferred as `Date32` in ClickHouse (in previous versions they were inferred as `Date`, which led to overflow of values outside a narrow range). Allow inserting `Date32` values back to PostgreSQL.\n\nFull migration instructions for a default change:\n> Deduplication is turned ON for all inserts by default. It was OFF before for async inserts and for MV's, but it was ON for sync inserts. The goal is to have the same defaults for both ways of inserts. If you have deduplication explicitly disabled on your cluster, you have to explicitly set `deduplicate_insert='backward_compatible_choice'` to keep the old behavior.\n\nDescribes new capability with enough detail to understand when to use it:\n> Added `OPTIMIZE \u003Ctable> DRY RUN PARTS \u003Cpart names>` query to simulate merges without committing the result part. It may be useful for testing purposes: verifying merge correctness in the new version, deterministically reproducing merge-related bugs, and reliably benchmarking merge performance.\n\nReference the issue if one exists: `Closes #XXXXX` or `Fixes #XXXXX` at the end.\n\n## What to avoid\n\nThese patterns make PRs harder to read or signal low effort:\n\n- `fix(scope):` \u002F `feat():` \u002F `chore():` — ClickHouse doesn't use conventional commits\n- `This PR ...` to start any section — just describe the change\n- Vague titles like `Fuzzer fixes`, `Fix bug`, `Improvements` — always say what specifically\n- Markdown tables comparing \"before\u002Fafter behavior\" unless genuinely useful\n- Perfectly parallel sentence structure throughout — vary phrasing naturally\n\n## AI co-authorship\n\nIt's fine to mention AI assistance openly. `Co-Authored-By:` in commits or acknowledgements in the PR description are acceptable — ClickHouse is open about AI-assisted development.\n\nWhen creating a PR, open it as a **Draft** — this prevents accidental merges.\n\nBefore creating or updating the PR, check user memory for a confirmation preference. If no preference is stored and the session is interactive, ask once: \"Should I always show you the description for approval before applying it, or just go ahead every time?\" Save the answer to memory and apply it from then on. If the session is non-interactive, proceed directly without asking.\n\n## Fork vs upstream\n\nIf the current repository is a fork (i.e. `git remote get-url origin` does not contain `ClickHouse\u002FClickHouse`), always target the upstream repository. Pass `--repo ClickHouse\u002FClickHouse` to `gh pr create` and set `--head \u003Cfork-owner>:\u003Cbranch>` so the PR is opened against the canonical repo, not the fork.\n","# ClickHouse PR Description Skill\n\nGenerate a good PR description and apply it, with optional confirmation based on user preference.\n\n## Title\n\nPlain description of what changed. No prefix conventions like `fix():` or `feat():`.\n\n- Good: `Change default stderr_reaction to log_last for executable UDFs`\n- Good: `Fix exception when inserting NULL into non-nullable column via CAST`\n- Bad: `fix(udf): Change default stderr_reaction` — conventional commits, ClickHouse doesn't use them\n- Bad: `Fuzzer fixes` — too vague, tells the reviewer nothing\n- Bad: `Improve error handling and enrich exit code exceptions with stderr context` — too vague, doesn't say what was actually changed\n\n## Body\n\nRead `.github\u002FPULL_REQUEST_TEMPLATE.md` for the exact template structure.\n\nA good PR description has two parts:\n\n**1. Free-form context (above the template, optional but encouraged for non-trivial changes)**\n\nExplain to a future reader: what was the problem, why did it need fixing, what approach was taken, what were the results or trade-offs. This is the right place for:\n- Motivation and background\n- Description of the approach and why it was chosen over alternatives\n- Benchmark results or measurements\n- Links to related issues, discussions, or previous attempts\n- Any caveats or known limitations\n\nUse plain paragraphs. Headers like `## Motivation`, `## Changes`, `## Results` are fine and helpful — they make the PR easier to navigate for reviewers. Bullet lists are fine. Be as detailed as needed.\n\n**2. Template section (mandatory)**\n\nFill in the changelog category (delete the rest of the list), write the changelog entry, and keep the documentation checkbox.\n\n**Exception — CI Fix or Improvement:** omit the Changelog entry and Documentation entry sections entirely (they are not required). Keep the entire PR body under 100 words.\n\n### Example of a well-written body\n\nFrom [#96110](https:\u002F\u002Fgithub.com\u002FClickHouse\u002FClickHouse\u002Fpull\u002F96110):\n\n```\n### Changelog category (leave one):\n- Backward Incompatible Change\n\n### Changelog entry:\nThe semantics of the `do_not_merge_across_partitions_select_final` setting were\nmade more obvious. Previously, the feature could be automatically enabled when\nthe setting was not explicitly set in the configs. It caused confusion repeatedly\nand, unfortunately, led to some issues in production. Now, the rules are simpler:\n`do_not_merge_across_partitions_select_final=1` enables the functionality\nunconditionally. If `do_not_merge_across_partitions_select_final=0`, then automatic\nis used only if the new setting\n`enable_automatic_decision_for_merging_across_partitions_for_final=1` and not used\notherwise. To preserve the old behaviour as much as possible, the defaults were set\nto `do_not_merge_across_partitions_select_final=0` and\n`enable_automatic_decision_for_merging_across_partitions_for_final=1`.\n\n### Documentation entry for user-facing changes\n- [ ] Documentation is written (mandatory for new features)\n\n---\n\nThe backward-incompatible part is that if someone has\n`do_not_merge_across_partitions_select_final=0` explicitly set in the configs,\nit no longer protects against the use of automatics. I'm open to discussion on\nwhether we should conservatively default to disabled automatics.\n```\n\nNote: extra context after `---` is fine — reviewers see it, but only the changelog entry above the blank line goes into the CHANGELOG.\n\n## Changelog entry guidelines\n\nThe entry is what ends up in the published CHANGELOG. Write it for a user who is upgrading and scanning for what affects them. The PR link and author attribution are appended automatically by tooling — do not include them.\n\n**Format:** the changelog script (`tests\u002Fci\u002Fchangelog.py`) collects all lines after the `### Changelog entry:` header up to the first blank line, then joins them with spaces into a single string. This means:\n- The entry can span multiple lines in the template — they become one paragraph\n- A blank line terminates collection — anything after it is ignored\n- Write it as a single paragraph (no bullet lists, no blank lines within)\n\n**Tense:** mixed is fine and natural. \"Added X\", \"Fix a case where...\", \"The `X` setting is now Y\" are all real examples from the CHANGELOG. Don't force everything into present tense.\n\n**Length:** match the impact. A small new function can be one sentence. A changed default or backward-incompatible behavior warrants as many sentences as needed, including what users must do to adapt.\n\n**Specificity:** always name the exact thing that changed. Never write \"Fix a bug\" or \"Improve performance\" without saying what specifically.\n\n**For backward-incompatible changes:** always explain the old behavior, the new behavior, and how to restore the old one if possible.\n\n**Real examples from the ClickHouse CHANGELOG:**\n\nOne sentence, sufficient for a focused addition:\n> Add `xxh3_128` hashing function.\n\nOne sentence with enough context:\n> `DATE` columns from PostgreSQL are now inferred as `Date32` in ClickHouse (in previous versions they were inferred as `Date`, which led to overflow of values outside a narrow range). Allow inserting `Date32` values back to PostgreSQL.\n\nFull migration instructions for a default change:\n> Deduplication is turned ON for all inserts by default. It was OFF before for async inserts and for MV's, but it was ON for sync inserts. The goal is to have the same defaults for both ways of inserts. If you have deduplication explicitly disabled on your cluster, you have to explicitly set `deduplicate_insert='backward_compatible_choice'` to keep the old behavior.\n\nDescribes new capability with enough detail to understand when to use it:\n> Added `OPTIMIZE \u003Ctable> DRY RUN PARTS \u003Cpart names>` query to simulate merges without committing the result part. It may be useful for testing purposes: verifying merge correctness in the new version, deterministically reproducing merge-related bugs, and reliably benchmarking merge performance.\n\nReference the issue if one exists: `Closes #XXXXX` or `Fixes #XXXXX` at the end.\n\n## What to avoid\n\nThese patterns make PRs harder to read or signal low effort:\n\n- `fix(scope):` \u002F `feat():` \u002F `chore():` — ClickHouse doesn't use conventional commits\n- `This PR ...` to start any section — just describe the change\n- Vague titles like `Fuzzer fixes`, `Fix bug`, `Improvements` — always say what specifically\n- Markdown tables comparing \"before\u002Fafter behavior\" unless genuinely useful\n- Perfectly parallel sentence structure throughout — vary phrasing naturally\n\n## AI co-authorship\n\nIt's fine to mention AI assistance openly. `Co-Authored-By:` in commits or acknowledgements in the PR description are acceptable — ClickHouse is open about AI-assisted development.\n\nWhen creating a PR, open it as a **Draft** — this prevents accidental merges.\n\nBefore creating or updating the PR, check user memory for a confirmation preference. If no preference is stored and the session is interactive, ask once: \"Should I always show you the description for approval before applying it, or just go ahead every time?\" Save the answer to memory and apply it from then on. If the session is non-interactive, proceed directly without asking.\n\n## Fork vs upstream\n\nIf the current repository is a fork (i.e. `git remote get-url origin` does not contain `ClickHouse\u002FClickHouse`), always target the upstream repository. Pass `--repo ClickHouse\u002FClickHouse` to `gh pr create` and set `--head \u003Cfork-owner>:\u003Cbranch>` so the PR is opened against the canonical repo, not the fork.\n",{"name":5,"description":7,"allowed-tools":24,"argument-hint":25,"disable-model-invocation":20},"Task, Bash(gh:*), Bash(git:*), Read, Glob, Grep, AskUserQuestion","[PR-number or branch-name]","main","87afe6ce96220accf50a345dea46784c8c9f210e","YYC3-Data-数据存储\u002FYYC3-Data-数据存储-ClickHouse\u002F.claude\u002Fskills\u002Fclickhouse-pr-description",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":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill clickhouse-pr-description",{"tool":41,"command":42},"bunx","bunx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill clickhouse-pr-description",{"tool":44,"command":45},"pnpm","pnpm dlx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill clickhouse-pr-description","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Data-数据存储\u002FYYC3-Data-数据存储-ClickHouse\u002F.claude\u002Fskills\u002Fclickhouse-pr-description\u002FSKILL.md",true,[],[50,57,64,71,78,85],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"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":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"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":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"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":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"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":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"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":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},"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",[],[]]