[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72AMQXVDRPXFD7X5KM02366":3,"skill-same:01M72AMQXVDRPXFD7X5KM02366":60},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":40,"commitSha":41,"skillDirectory":42,"forksCount":13,"repositoryHtmlUrl":43,"repositoryHomepageUrl":6,"ownerHtmlUrl":44,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":45,"install":46,"resources":59},"01M72AMQXVDRPXFD7X5KM02366","ui-component",null,"Generate a new UI component that follows StyleSeed Toss conventions for structure, tokens, accessibility, and component ergonomics.","Sansar35\u002Fclaude-agent","Sansar35","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F145020281?v=4","01M724CQ2SCC86MGNSD87D0D4K","01M724CQ3965G9WJ3QXE3AJ5YY",1,"MIT","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fantigravity\u002Fui-component\u002FSKILL.md",[],[],"2026-11-10 18:39:20",false,"---\nname: ui-component\ndescription: \"Generate a new UI component that follows StyleSeed Toss conventions for structure, tokens, accessibility, and component ergonomics.\"\ncategory: design\nrisk: safe\nsource: community\nsource_repo: bitjaru\u002Fstyleseed\nsource_type: community\ndate_added: \"2026-04-08\"\nauthor: bitjaru\ntags: [ui, components, design-system, frontend, styleseed]\ntools: [claude, cursor, codex, gemini]\n---\n\n# UI Component\n\n## Overview\n\nPart of [StyleSeed](https:\u002F\u002Fgithub.com\u002Fbitjaru\u002Fstyleseed), this skill generates components that respect the Toss seed's design language instead of improvising ad hoc markup and styling. It emphasizes semantic tokens, predictable typing, reusable variants, and mobile-friendly accessibility defaults.\n\n## When to Use\n- Use when you need a new UI primitive or composed component inside a StyleSeed-based project\n- Use when you want a component to match the existing Toss seed conventions\n- Use when a component should be reusable, typed, and design-token driven\n- Use when the AI might otherwise invent spacing, colors, or interaction patterns\n\n## How It Works\n\n### Step 1: Read the Local Design Context\n\nBefore generating code, inspect the seed's source of truth:\n- `CLAUDE.md` for conventions\n- `css\u002Ftheme.css` for semantic tokens\n- at least one representative component from `components\u002Fui\u002F`\n\nIf the user already has a better local example, follow the local codebase over a generic template.\n\n### Step 2: Choose the Correct Home\n\nPlace the output where it belongs:\n- `src\u002Fcomponents\u002Fui\u002F` for primitives and low-level building blocks\n- `src\u002Fcomponents\u002Fpatterns\u002F` for composed sections or multi-part patterns\n\nDo not create a new primitive if an existing one can be extended safely.\n\n### Step 3: Follow the Structural Rules\n\nUse these defaults unless the host project strongly disagrees:\n- function declaration instead of a `const` component\n- `React.ComponentProps\u003C>` or equivalent native prop typing\n- `className` passthrough support\n- `cn()` or the project's standard class merger\n- `data-slot` for component identification\n- CVA or equivalent only when variants are genuinely needed\n\n### Step 4: Use Semantic Tokens Only\n\nDo not hardcode visual values if the design system has a token for them.\n\nPreferred examples:\n- `bg-card`\n- `text-foreground`\n- `text-muted-foreground`\n- `border-border`\n- `shadow-[var(--shadow-card)]`\n\n### Step 5: Preserve StyleSeed Typography and Spacing\n\n- Use the scale already defined by the seed\n- Prefer multiples of 6px\n- Use logical spacing utilities where supported\n- Keep display and heading text tight, body text readable, captions restrained\n\n### Step 6: Bake in Accessibility\n\n- Touch targets should be at least 44x44px for interactive elements\n- Keyboard focus must be visible\n- Pass through `aria-*` attributes where appropriate\n- Respect reduced-motion preferences for nonessential motion\n\n## Output\n\nProvide:\n1. The generated component\n2. The target path\n3. Any required imports or dependencies\n4. Notes on variants, tokens, or follow-up integration work\n\n## Best Practices\n\n- Compose from existing primitives before inventing new ones\n- Keep the component API small and predictable\n- Prefer semantic layout classes over arbitrary values\n- Export named components unless the host project uses another standard consistently\n\n## Additional Resources\n\n- [StyleSeed repository](https:\u002F\u002Fgithub.com\u002Fbitjaru\u002Fstyleseed)\n- [Source skill](https:\u002F\u002Fgithub.com\u002Fbitjaru\u002Fstyleseed\u002Fblob\u002Fmain\u002Fseeds\u002Ftoss\u002F.claude\u002Fskills\u002Fui-component\u002FSKILL.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","# UI Component\n\n## Overview\n\nPart of [StyleSeed](https:\u002F\u002Fgithub.com\u002Fbitjaru\u002Fstyleseed), this skill generates components that respect the Toss seed's design language instead of improvising ad hoc markup and styling. It emphasizes semantic tokens, predictable typing, reusable variants, and mobile-friendly accessibility defaults.\n\n## When to Use\n- Use when you need a new UI primitive or composed component inside a StyleSeed-based project\n- Use when you want a component to match the existing Toss seed conventions\n- Use when a component should be reusable, typed, and design-token driven\n- Use when the AI might otherwise invent spacing, colors, or interaction patterns\n\n## How It Works\n\n### Step 1: Read the Local Design Context\n\nBefore generating code, inspect the seed's source of truth:\n- `CLAUDE.md` for conventions\n- `css\u002Ftheme.css` for semantic tokens\n- at least one representative component from `components\u002Fui\u002F`\n\nIf the user already has a better local example, follow the local codebase over a generic template.\n\n### Step 2: Choose the Correct Home\n\nPlace the output where it belongs:\n- `src\u002Fcomponents\u002Fui\u002F` for primitives and low-level building blocks\n- `src\u002Fcomponents\u002Fpatterns\u002F` for composed sections or multi-part patterns\n\nDo not create a new primitive if an existing one can be extended safely.\n\n### Step 3: Follow the Structural Rules\n\nUse these defaults unless the host project strongly disagrees:\n- function declaration instead of a `const` component\n- `React.ComponentProps\u003C>` or equivalent native prop typing\n- `className` passthrough support\n- `cn()` or the project's standard class merger\n- `data-slot` for component identification\n- CVA or equivalent only when variants are genuinely needed\n\n### Step 4: Use Semantic Tokens Only\n\nDo not hardcode visual values if the design system has a token for them.\n\nPreferred examples:\n- `bg-card`\n- `text-foreground`\n- `text-muted-foreground`\n- `border-border`\n- `shadow-[var(--shadow-card)]`\n\n### Step 5: Preserve StyleSeed Typography and Spacing\n\n- Use the scale already defined by the seed\n- Prefer multiples of 6px\n- Use logical spacing utilities where supported\n- Keep display and heading text tight, body text readable, captions restrained\n\n### Step 6: Bake in Accessibility\n\n- Touch targets should be at least 44x44px for interactive elements\n- Keyboard focus must be visible\n- Pass through `aria-*` attributes where appropriate\n- Respect reduced-motion preferences for nonessential motion\n\n## Output\n\nProvide:\n1. The generated component\n2. The target path\n3. Any required imports or dependencies\n4. Notes on variants, tokens, or follow-up integration work\n\n## Best Practices\n\n- Compose from existing primitives before inventing new ones\n- Keep the component API small and predictable\n- Prefer semantic layout classes over arbitrary values\n- Export named components unless the host project uses another standard consistently\n\n## Additional Resources\n\n- [StyleSeed repository](https:\u002F\u002Fgithub.com\u002Fbitjaru\u002Fstyleseed)\n- [Source skill](https:\u002F\u002Fgithub.com\u002Fbitjaru\u002Fstyleseed\u002Fblob\u002Fmain\u002Fseeds\u002Ftoss\u002F.claude\u002Fskills\u002Fui-component\u002FSKILL.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":23,"tags":24,"tools":30,"author":35,"source":36,"category":37,"date_added":38,"description":7,"source_repo":39,"source_type":36},"safe",[25,26,27,28,29],"ui","components","design-system","frontend","styleseed",[31,32,33,34],"claude","cursor","codex","gemini","bitjaru","community","design","2026-04-08","bitjaru\u002Fstyleseed","main","d046d088ce5a79a083f0abc0fe1b7ded73bc5b1f","claude-config\u002Fskills\u002Fantigravity\u002Fui-component","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent","https:\u002F\u002Fgithub.com\u002FSansar35","2026-05-10 16:04:53",{"source":8,"skillName":5,"commands":47,"prompt":57,"zipAvailable":58},[48,51,54],{"tool":49,"command":50},"npx","npx skills add Sansar35\u002Fclaude-agent --skill ui-component",{"tool":52,"command":53},"bunx","bunx skills add Sansar35\u002Fclaude-agent --skill ui-component",{"tool":55,"command":56},"pnpm","pnpm dlx skills add Sansar35\u002Fclaude-agent --skill ui-component","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fantigravity\u002Fui-component\u002FSKILL.md",true,[],[61,68,75,82,89,97],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":18},"01M72DVAN1JYEA302MT0C5MGD6","zustand-store-ts","Create Zustand stores following established patterns with proper TypeScript types and middleware.","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzustand-store-ts\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":18},"01M72DV8J5NBRRM4RPDFRV95N7","zod-validation-expert","Expert in Zod — TypeScript-first schema validation. Covers parsing, custom errors, refinements, type inference, and integration with React Hook Form, Next.js, and tRPC.","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzod-validation-expert\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":18},"01M72DV5EMHW0BHP9BZ167MDCB","zinc-database","Access ZINC (230M+ purchasable compounds). Search by ZINC ID\u002FSMILES, similarity searches, 3D-ready structures for docking, analog discovery, for virtual screening and drug discovery.","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzinc-database\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":18},"01M72DV216QY0E693ZPEVQ0DBS","zarr-python","Chunked N-D arrays for cloud storage. Compressed arrays, parallel I\u002FO, S3\u002FGCS integration, NumPy\u002FDask\u002FXarray compatible, for large-scale scientific computing pipelines.","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzarr-python\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":93,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":18},"01M72DTXQREMCRKA8NHCVKHN4W","zapier-workflows","Manage and trigger pre-built Zapier workflows and MCP tool orchestration. Use when user mentions workflows, Zaps, automations, daily digest, research, search, lead tracking, expenses, or asks to \"run\" any process. Also handles Perplexity-based research and Google Sheets data tracking.","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzapier-workflows\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzapier-workflows\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":18},"01M72DTT17TBSJ0Y8J2XZ4C9TZ","zapier-make-patterns","No-code automation democratizes workflow building. Zapier and Make (formerly Integromat) let non-developers automate business processes without writing code. But no-code doesn't mean no-complexity - these platforms have their own patterns, pitfalls, and breaking points.  This skill covers when to use which platform, how to build reliable automations, and when to graduate to code-based solutions. Key insight: Zapier optimizes for simplicity and integrations (7000+ apps), Make optimizes for power","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzapier-make-patterns\u002FSKILL.md",[],[]]