[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7C1SEF4SC0E07VZCVSSRRV7":3,"skill-same:01M7C1SEF4SC0E07VZCVSSRRV7":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":39,"commitSha":40,"skillDirectory":41,"forksCount":42,"repositoryHtmlUrl":43,"repositoryHomepageUrl":44,"ownerHtmlUrl":45,"ownerBlogUrl":6,"ownerDescription":46,"updatedAt":47,"install":48,"resources":61},"01M7C1SEF4SC0E07VZCVSSRRV7","minimalist-ui",null,"Use when creating clean editorial interfaces with warm monochrome palettes, crisp borders, restrained motion, and flat bento layouts.","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\u002Fminimalist-ui\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: minimalist-ui\ndescription: \"Use when creating clean editorial interfaces with warm monochrome palettes, crisp borders, restrained motion, and flat bento layouts.\"\ncategory: frontend\nrisk: safe\nsource: community\nsource_repo: Leonxlnx\u002Ftaste-skill\nsource_type: community\ndate_added: \"2026-04-17\"\nauthor: Leonxlnx\ntags: [frontend, design, minimalism, ui]\ntools: [claude, cursor, codex, antigravity]\n---\n# Protocol: Premium Utilitarian Minimalism UI Architect\n\n## When to Use\n\n- Use when the user wants a refined minimalist UI inspired by tools like Notion, Linear, or editorial workspace products.\n- Use when designing warm monochrome interfaces with crisp borders, generous whitespace, muted pastel accents, and quiet motion.\n- Use when the task should avoid gradients, heavy shadows, saturated colors, pill-heavy components, and generic SaaS visuals.\n\n## Limitations\n\n- Minimalism can hide hierarchy when content is dense; validate scannability, contrast, and navigation clarity with real content.\n- This skill assumes the product can support restrained palettes and typography-led layouts; do not override an established brand system without cause.\n- Subtle motion and flat surfaces still need responsive, keyboard, and screen-reader verification in the target project.\n\n\n## 1. Protocol Overview\nName: Premium Utilitarian Minimalism & Editorial UI\nDescription: An advanced frontend engineering directive for generating highly refined, ultra-minimalist, \"document-style\" web interfaces analogous to top-tier workspace platforms. This protocol strictly enforces a high-contrast warm monochrome palette, bespoke typographic hierarchies, meticulous structural macro-whitespace, bento-grid layouts, and an ultra-flat component architecture with deliberate muted pastel accents. It actively rejects standard generic SaaS design trends.\n\n## 2. Absolute Negative Constraints (Banned Elements)\nThe AI must strictly avoid the following generic web development defaults:\n- DO NOT use the \"Inter\", \"Roboto\", or \"Open Sans\" typefaces.\n- DO NOT use generic, thin-line icon libraries like \"Lucide\", \"Feather\", or standard \"Heroicons\".\n- DO NOT use Tailwind's default heavy drop shadows (e.g., `shadow-md`, `shadow-lg`, `shadow-xl`). Shadows must be practically non-existent or heavily customized to be ultra-diffuse and low opacity (\u003C 0.05).\n- DO NOT use primary colored backgrounds for large elements or sections (e.g., no bright blue, green, or red hero sections).\n- DO NOT use gradients, neon colors, or 3D glassmorphism (beyond subtle navbar blurs).\n- DO NOT use `rounded-full` (pill shapes) for large containers, cards, or primary buttons.\n- DO NOT use emojis anywhere in code, markup, text content, headings, or alt text. Replace with proper icons or clean SVG primitives.\n- DO NOT use generic placeholder names like \"John Doe\", \"Acme Corp\", or \"Lorem Ipsum\". Use realistic, contextual content.\n- DO NOT use AI copywriting clichés: \"Elevate\", \"Seamless\", \"Unleash\", \"Next-Gen\", \"Game-changer\", \"Delve\". Write plain, specific language.\n\n## 3. Typographic Architecture\nThe interface must rely on extreme typographic contrast and premium font selection to establish an editorial feel.\n- Primary Sans-Serif (Body, UI, Buttons): Use clean, geometric, or system-native fonts with character. Target: `font-family: 'SF Pro Display', 'Geist Sans', 'Helvetica Neue', 'Switzer', sans-serif`.\n- Editorial Serif (Hero Headings & Quotes): Target: `font-family: 'Lyon Text', 'Newsreader', 'Playfair Display', 'Instrument Serif', serif`. Apply tight tracking (`letter-spacing: -0.02em` to `-0.04em`) and tight line-height (`1.1`).\n- Monospace (Code, Keystrokes, Meta-data): Target: `font-family: 'Geist Mono', 'SF Mono', 'JetBrains Mono', monospace`.\n- Text Colors: Body text must never be absolute black (`#000000`). Use off-black\u002Fcharcoal (`#111111` or `#2F3437`) with a generous `line-height` of `1.6` for legibility. Secondary text should be muted gray (`#787774`).\n\n## 4. Color Palette (Warm Monochrome + Spot Pastels)\nColor is a scarce resource, utilized only for semantic meaning or subtle accents.\n- Canvas \u002F Background: Pure White `#FFFFFF` or Warm Bone\u002FOff-White `#F7F6F3` \u002F `#FBFBFA`.\n- Primary Surface (Cards): `#FFFFFF` or `#F9F9F8`.\n- Structural Borders \u002F Dividers: Ultra-light gray `#EAEAEA` or `rgba(0,0,0,0.06)`.\n- Accent Colors: Exclusively use highly desaturated, washed-out pastels for tags, inline code backgrounds, or subtle icon backgrounds.\n  - Pale Red: `#FDEBEC` (Text: `#9F2F2D`)\n  - Pale Blue: `#E1F3FE` (Text: `#1F6C9F`)\n  - Pale Green: `#EDF3EC` (Text: `#346538`)\n  - Pale Yellow: `#FBF3DB` (Text: `#956400`)\n\n## 5. Component Specifications\n- Bento Box Feature Grids:\n  - Utilize asymmetrical CSS Grid layouts.\n  - Cards must have exactly `border: 1px solid #EAEAEA`.\n  - Border-radius must be crisp: `8px` or `12px` maximum.\n  - Internal padding must be generous (e.g., `24px` to `40px`).\n- Primary Call-To-Action (Buttons):\n  - Solid background `#111111`, text `#FFFFFF`.\n  - Slight border-radius (`4px` to `6px`). No box-shadow.\n  - Hover state should be a subtle color shift to `#333333` or a micro-scale `transform: scale(0.98)`.\n- Tags & Status Badges:\n  - Pill-shaped (`border-radius: 9999px`), very small typography (`text-xs`), uppercase with wide tracking (`letter-spacing: 0.05em`).\n  - Background must use the defined Muted Pastels.\n- Accordions (FAQ):\n  - Strip all container boxes. Separate items only with a `border-bottom: 1px solid #EAEAEA`.\n  - Use a clean, sharp `+` and `-` icon for the toggle state.\n- Keystroke Micro-UIs:\n  - Render shortcuts as physical keys using `\u003Ckbd>` tags: `border: 1px solid #EAEAEA`, `border-radius: 4px`, `background: #F7F6F3`, using the Monospace font.\n- Faux-OS Window Chrome:\n  - When mocking up software, wrap it in a minimalist container with a white top bar containing three small, light gray circles (replicating macOS window controls).\n\n## 6. Iconography & Imagery Directives\n- System Icons: Use \"Phosphor Icons (Bold or Fill weights)\" or \"Radix UI Icons\" for a technical, slightly thicker-stroke aesthetic. Standardize stroke width across all icons.\n- Illustrations: Monochromatic, rough continuous-line ink sketches on a white background, featuring a single offset geometric shape filled with a muted pastel color.\n- Photography: Use high-quality, desaturated images with a warm tone. Apply subtle overlays (`opacity: 0.04` warm grain) to blend photos into the monochrome palette. Never use oversaturated stock photos. Use reliable placeholders like `https:\u002F\u002Fpicsum.photos\u002Fseed\u002F{context}\u002F1200\u002F800` when real assets are unavailable.\n- Hero & Section Backgrounds: Sections should not feel empty and flat. Use subtle full-width background imagery at very low opacity, soft radial light spots (`radial-gradient` with warm tones at `opacity: 0.03`), or minimal geometric line patterns to add depth without breaking the clean aesthetic.\n\n## 7. Subtle Motion & Micro-Animations\nMotion should feel invisible — present but never distracting. The goal is quiet sophistication, not spectacle.\n- Scroll Entry: Elements fade in gently as they enter the viewport. Use `translateY(12px)` + `opacity: 0` resolving over `600ms` with `cubic-bezier(0.16, 1, 0.3, 1)`. Use `IntersectionObserver`, never `window.addEventListener('scroll')`.\n- Hover States: Cards lift with an ultra-subtle shadow shift (`box-shadow` transitioning from `0 0 0` to `0 2px 8px rgba(0,0,0,0.04)` over `200ms`). Buttons respond with `scale(0.98)` on `:active`.\n- Staggered Reveals: Lists and grid items enter with a cascade delay (`animation-delay: calc(var(--index) * 80ms)`). Never mount everything at once.\n- Background Ambient Motion: Optional. A single, very slow-moving radial gradient blob (`animation-duration: 20s+`, `opacity: 0.02-0.04`) drifting behind hero sections. Must be applied to a `position: fixed; pointer-events: none` layer. Never on scrolling containers.\n- Performance: Animate exclusively via `transform` and `opacity`. No layout-triggering properties (`top`, `left`, `width`, `height`). Use `will-change: transform` sparingly and only on actively animating elements.\n\n## 8. Execution Protocol\nWhen tasked with writing frontend code (HTML, React, Tailwind, Vue) or designing a layout:\n1. Establish the macro-whitespace first. Use massive vertical padding between sections (e.g., `py-24` or `py-32` in Tailwind).\n2. Constrain the main typography content width to `max-w-4xl` or `max-w-5xl`.\n3. Apply the custom typographic hierarchy and monochromatic color variables immediately.\n4. Ensure every card, divider, and border adheres strictly to the `1px solid #EAEAEA` rule.\n5. Add scroll-entry animations to all major content blocks.\n6. Ensure sections have visual depth through imagery, ambient gradients, or subtle textures — no empty flat backgrounds.\n7. Provide code that reflects this high-end, uncluttered, editorial aesthetic natively without requiring manual adjustments.\n","# Protocol: Premium Utilitarian Minimalism UI Architect\n\n## When to Use\n\n- Use when the user wants a refined minimalist UI inspired by tools like Notion, Linear, or editorial workspace products.\n- Use when designing warm monochrome interfaces with crisp borders, generous whitespace, muted pastel accents, and quiet motion.\n- Use when the task should avoid gradients, heavy shadows, saturated colors, pill-heavy components, and generic SaaS visuals.\n\n## Limitations\n\n- Minimalism can hide hierarchy when content is dense; validate scannability, contrast, and navigation clarity with real content.\n- This skill assumes the product can support restrained palettes and typography-led layouts; do not override an established brand system without cause.\n- Subtle motion and flat surfaces still need responsive, keyboard, and screen-reader verification in the target project.\n\n\n## 1. Protocol Overview\nName: Premium Utilitarian Minimalism & Editorial UI\nDescription: An advanced frontend engineering directive for generating highly refined, ultra-minimalist, \"document-style\" web interfaces analogous to top-tier workspace platforms. This protocol strictly enforces a high-contrast warm monochrome palette, bespoke typographic hierarchies, meticulous structural macro-whitespace, bento-grid layouts, and an ultra-flat component architecture with deliberate muted pastel accents. It actively rejects standard generic SaaS design trends.\n\n## 2. Absolute Negative Constraints (Banned Elements)\nThe AI must strictly avoid the following generic web development defaults:\n- DO NOT use the \"Inter\", \"Roboto\", or \"Open Sans\" typefaces.\n- DO NOT use generic, thin-line icon libraries like \"Lucide\", \"Feather\", or standard \"Heroicons\".\n- DO NOT use Tailwind's default heavy drop shadows (e.g., `shadow-md`, `shadow-lg`, `shadow-xl`). Shadows must be practically non-existent or heavily customized to be ultra-diffuse and low opacity (\u003C 0.05).\n- DO NOT use primary colored backgrounds for large elements or sections (e.g., no bright blue, green, or red hero sections).\n- DO NOT use gradients, neon colors, or 3D glassmorphism (beyond subtle navbar blurs).\n- DO NOT use `rounded-full` (pill shapes) for large containers, cards, or primary buttons.\n- DO NOT use emojis anywhere in code, markup, text content, headings, or alt text. Replace with proper icons or clean SVG primitives.\n- DO NOT use generic placeholder names like \"John Doe\", \"Acme Corp\", or \"Lorem Ipsum\". Use realistic, contextual content.\n- DO NOT use AI copywriting clichés: \"Elevate\", \"Seamless\", \"Unleash\", \"Next-Gen\", \"Game-changer\", \"Delve\". Write plain, specific language.\n\n## 3. Typographic Architecture\nThe interface must rely on extreme typographic contrast and premium font selection to establish an editorial feel.\n- Primary Sans-Serif (Body, UI, Buttons): Use clean, geometric, or system-native fonts with character. Target: `font-family: 'SF Pro Display', 'Geist Sans', 'Helvetica Neue', 'Switzer', sans-serif`.\n- Editorial Serif (Hero Headings & Quotes): Target: `font-family: 'Lyon Text', 'Newsreader', 'Playfair Display', 'Instrument Serif', serif`. Apply tight tracking (`letter-spacing: -0.02em` to `-0.04em`) and tight line-height (`1.1`).\n- Monospace (Code, Keystrokes, Meta-data): Target: `font-family: 'Geist Mono', 'SF Mono', 'JetBrains Mono', monospace`.\n- Text Colors: Body text must never be absolute black (`#000000`). Use off-black\u002Fcharcoal (`#111111` or `#2F3437`) with a generous `line-height` of `1.6` for legibility. Secondary text should be muted gray (`#787774`).\n\n## 4. Color Palette (Warm Monochrome + Spot Pastels)\nColor is a scarce resource, utilized only for semantic meaning or subtle accents.\n- Canvas \u002F Background: Pure White `#FFFFFF` or Warm Bone\u002FOff-White `#F7F6F3` \u002F `#FBFBFA`.\n- Primary Surface (Cards): `#FFFFFF` or `#F9F9F8`.\n- Structural Borders \u002F Dividers: Ultra-light gray `#EAEAEA` or `rgba(0,0,0,0.06)`.\n- Accent Colors: Exclusively use highly desaturated, washed-out pastels for tags, inline code backgrounds, or subtle icon backgrounds.\n  - Pale Red: `#FDEBEC` (Text: `#9F2F2D`)\n  - Pale Blue: `#E1F3FE` (Text: `#1F6C9F`)\n  - Pale Green: `#EDF3EC` (Text: `#346538`)\n  - Pale Yellow: `#FBF3DB` (Text: `#956400`)\n\n## 5. Component Specifications\n- Bento Box Feature Grids:\n  - Utilize asymmetrical CSS Grid layouts.\n  - Cards must have exactly `border: 1px solid #EAEAEA`.\n  - Border-radius must be crisp: `8px` or `12px` maximum.\n  - Internal padding must be generous (e.g., `24px` to `40px`).\n- Primary Call-To-Action (Buttons):\n  - Solid background `#111111`, text `#FFFFFF`.\n  - Slight border-radius (`4px` to `6px`). No box-shadow.\n  - Hover state should be a subtle color shift to `#333333` or a micro-scale `transform: scale(0.98)`.\n- Tags & Status Badges:\n  - Pill-shaped (`border-radius: 9999px`), very small typography (`text-xs`), uppercase with wide tracking (`letter-spacing: 0.05em`).\n  - Background must use the defined Muted Pastels.\n- Accordions (FAQ):\n  - Strip all container boxes. Separate items only with a `border-bottom: 1px solid #EAEAEA`.\n  - Use a clean, sharp `+` and `-` icon for the toggle state.\n- Keystroke Micro-UIs:\n  - Render shortcuts as physical keys using `\u003Ckbd>` tags: `border: 1px solid #EAEAEA`, `border-radius: 4px`, `background: #F7F6F3`, using the Monospace font.\n- Faux-OS Window Chrome:\n  - When mocking up software, wrap it in a minimalist container with a white top bar containing three small, light gray circles (replicating macOS window controls).\n\n## 6. Iconography & Imagery Directives\n- System Icons: Use \"Phosphor Icons (Bold or Fill weights)\" or \"Radix UI Icons\" for a technical, slightly thicker-stroke aesthetic. Standardize stroke width across all icons.\n- Illustrations: Monochromatic, rough continuous-line ink sketches on a white background, featuring a single offset geometric shape filled with a muted pastel color.\n- Photography: Use high-quality, desaturated images with a warm tone. Apply subtle overlays (`opacity: 0.04` warm grain) to blend photos into the monochrome palette. Never use oversaturated stock photos. Use reliable placeholders like `https:\u002F\u002Fpicsum.photos\u002Fseed\u002F{context}\u002F1200\u002F800` when real assets are unavailable.\n- Hero & Section Backgrounds: Sections should not feel empty and flat. Use subtle full-width background imagery at very low opacity, soft radial light spots (`radial-gradient` with warm tones at `opacity: 0.03`), or minimal geometric line patterns to add depth without breaking the clean aesthetic.\n\n## 7. Subtle Motion & Micro-Animations\nMotion should feel invisible — present but never distracting. The goal is quiet sophistication, not spectacle.\n- Scroll Entry: Elements fade in gently as they enter the viewport. Use `translateY(12px)` + `opacity: 0` resolving over `600ms` with `cubic-bezier(0.16, 1, 0.3, 1)`. Use `IntersectionObserver`, never `window.addEventListener('scroll')`.\n- Hover States: Cards lift with an ultra-subtle shadow shift (`box-shadow` transitioning from `0 0 0` to `0 2px 8px rgba(0,0,0,0.04)` over `200ms`). Buttons respond with `scale(0.98)` on `:active`.\n- Staggered Reveals: Lists and grid items enter with a cascade delay (`animation-delay: calc(var(--index) * 80ms)`). Never mount everything at once.\n- Background Ambient Motion: Optional. A single, very slow-moving radial gradient blob (`animation-duration: 20s+`, `opacity: 0.02-0.04`) drifting behind hero sections. Must be applied to a `position: fixed; pointer-events: none` layer. Never on scrolling containers.\n- Performance: Animate exclusively via `transform` and `opacity`. No layout-triggering properties (`top`, `left`, `width`, `height`). Use `will-change: transform` sparingly and only on actively animating elements.\n\n## 8. Execution Protocol\nWhen tasked with writing frontend code (HTML, React, Tailwind, Vue) or designing a layout:\n1. Establish the macro-whitespace first. Use massive vertical padding between sections (e.g., `py-24` or `py-32` in Tailwind).\n2. Constrain the main typography content width to `max-w-4xl` or `max-w-5xl`.\n3. Apply the custom typographic hierarchy and monochromatic color variables immediately.\n4. Ensure every card, divider, and border adheres strictly to the `1px solid #EAEAEA` rule.\n5. Add scroll-entry animations to all major content blocks.\n6. Ensure sections have visual depth through imagery, ambient gradients, or subtle textures — no empty flat backgrounds.\n7. Provide code that reflects this high-end, uncluttered, editorial aesthetic natively without requiring manual adjustments.\n",{"name":5,"risk":24,"tags":25,"tools":30,"author":35,"source":36,"category":26,"date_added":37,"description":7,"source_repo":38,"source_type":36},"safe",[26,27,28,29],"frontend","design","minimalism","ui",[31,32,33,34],"claude","cursor","codex","antigravity","Leonxlnx","community","2026-04-17","Leonxlnx\u002Ftaste-skill","main","87afe6ce96220accf50a345dea46784c8c9f210e","YYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fplugins\u002Fantigravity-awesome-skills-claude\u002Fskills\u002Fminimalist-ui",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":49,"prompt":59,"zipAvailable":60},[50,53,56],{"tool":51,"command":52},"npx","npx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill minimalist-ui",{"tool":54,"command":55},"bunx","bunx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill minimalist-ui",{"tool":57,"command":58},"pnpm","pnpm dlx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill minimalist-ui","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fplugins\u002Fantigravity-awesome-skills-claude\u002Fskills\u002Fminimalist-ui\u002FSKILL.md",true,[],[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",[],[]]