[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DG4WCXRXGJS4B6TQGPYV38":3,"skill-same:01M7DG4WCXRXGJS4B6TQGPYV38":43},{"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":23,"commitSha":24,"skillDirectory":25,"forksCount":13,"repositoryHtmlUrl":26,"repositoryHomepageUrl":6,"ownerHtmlUrl":27,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":28,"install":29,"resources":42},"01M7DG4WCXRXGJS4B6TQGPYV38","ui-sources",null,"Where the parts of a UI come from and how to put them into the product: shadcn\u002Fui (base components, blocks, charts), Motion (animations, transitions, gestures), Kokonut UI (animated cards, buttons, text effects), Bklit (advanced charts), 21st.dev (2,000+ UI components and blocks: AI chats, navigation, sign-ins, cards, heroes), Magic UI and Aceternity (animated app components and effects). Picks the right source for a need, shows real examples before choosing, installs through the shadcn CLI or the source's own MCP, and restyles to the product's tokens. Works in Cowork and the Code tab. Use when the user mentions any of these sites, asks how something could be built or animated (\"kan vi lave en animeret graf\", \"en fed hero\", \"kortene skal bevæge sig\", \"hvilken komponent\", \"brug kokonut\", \"find en komponent\"), or when a ticket adds or changes a UI component, chart or animation.","phillippasqualato\u002FPAPcSetup","phillippasqualato","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F243869150?v=4","01M7DFRVNH334NRG1TXEJPXBZH","01M7DFRVP62D3G2NB7N6KFCWCF",0,"MIT","https:\u002F\u002Fgithub.com\u002Fphillippasqualato\u002FPAPcSetup\u002Fblob\u002Fmain\u002Fplugins\u002Fproduct-studio\u002Fskills\u002Fui-sources\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: ui-sources\ndescription: \"Where the parts of a UI come from and how to put them into the product: shadcn\u002Fui (base components, blocks, charts), Motion (animations, transitions, gestures), Kokonut UI (animated cards, buttons, text effects), Bklit (advanced charts), 21st.dev (2,000+ UI components and blocks: AI chats, navigation, sign-ins, cards, heroes), Magic UI and Aceternity (animated app components and effects). Picks the right source for a need, shows real examples before choosing, installs through the shadcn CLI or the source's own MCP, and restyles to the product's tokens. Works in Cowork and the Code tab. Use when the user mentions any of these sites, asks how something could be built or animated (\\\"kan vi lave en animeret graf\\\", \\\"en fed hero\\\", \\\"kortene skal bevæge sig\\\", \\\"hvilken komponent\\\", \\\"brug kokonut\\\", \\\"find en komponent\\\"), or when a ticket adds or changes a UI component, chart or animation.\"\n---\n\n# UI sources\n\nimpeccable decides **how the product looks** (DESIGN.md). This skill decides **where each part comes from** and gets it into the code the right way. It never changes the look on its own: a new component is restyled to the existing tokens, and a change to the look goes through `grill-design` \u002F impeccable. Danish to the user, English in files.\n\nRead first: `..\u002Fdefine-design\u002Freferences\u002Fdesign-sources.md` (the sources, what each is for, install commands, licences, pitfalls, and \"Which source for what\"), then the project's `components.json`, `DESIGN.md` and `docs\u002Fdesign\u002Fcomponent-states.md` (its \"chosen source per component family\" wins over any new idea). Full evidence with source links: `..\u002Fdefine-toolchain\u002Freferences\u002Fdesign-sources.md`. Verify an install command on the source's docs (Context7 or the site's `llms.txt`) before running it.\n\n## 1. Pick the source (one winner per need)\n\nEvery source is broad: search all of them for the need, not only the one it's best known for (e.g. Aceternity has sidebars, tabs, modals, file upload, timelines and loaders; Magic UI has number tickers, animated lists, file trees, progress rings and bento grids; 21st.dev has AI chats, navigation, sign-ins and cards; Kokonut has AI inputs and buttons). The \"Which source for what\" table is a starting point, not a limit. Choose by fit: how well it serves the task, quality and accessibility, how easily it takes the product's tokens, performance, and licence. Rules:\n- The project's recorded choice wins: if component-states.md says \"charts: shadcn chart (Recharts)\", don't add Bklit next to it. A second chart stack, a second animation library (`framer-motion` next to `motion`) or a second icon set needs the user's explicit OK and a note in component-states.md.\n- Simple hover and enter states are Tailwind transitions, not Motion.\n- Judge an effect by where it sits, not by which site it's from. On a screen people work in every day, motion must support the task (show a change, guide attention, confirm an action), stay calm and fast, and respect reduced motion. Continuous canvas\u002FWebGL effects (globes, beams, shaders, 3D) belong where they don't slow down daily work; say the performance cost to the user when you suggest one.\n\n## 2. Show before choosing\n\nWhen the user asks \"how could this look\" or \"find something\", don't describe it: show 2-3 real candidates from the source (link plus a screenshot, or a small rendered artifact page using the product's tokens), each with one plain-Danish line on what it does and what it costs (free \u002F Pro). Let the user pick or say \"du bestemmer\" (log the choice in `docs\u002Fdesign\u002Fdecisions.md` like grill-design does). A choice that changes the look → `grill-design` pass C first.\n\n## 3. Put it into the product (Code tab)\n\n1. **Project setup, once per repo** (as a setup ticket if missing):\n   - `.mcp.json`: `\"shadcn\": { \"command\": \"npx\", \"args\": [\"shadcn@latest\", \"mcp\"] }`.\n   - `components.json` → `registries`: `\"@kokonutui\": \"https:\u002F\u002Fkokonutui.com\u002Fr\u002F{name}.json\"`, `\"@bklit\": \"https:\u002F\u002Fui.bklit.com\u002Fr\u002F{name}.json\"` (and `@magicui`, `@aceternity` only if the project uses them). Namespaces listed in the shadcn directory also work without this entry; writing it makes the source explicit.\n   - Motion: `npx motion-ai` (project install, Claude Code) adds Motion's MCP and skills; doc search is free, Motion+ features need the user's own sign-in.\n   - 21st.dev: only if the user wants it; its MCP needs the user's API key from 21st.dev, stored as an env variable, never in a file.\n2. **Install**: `npx shadcn@latest add @\u003Csource>\u002F\u003Citem> --dry-run` (or `--diff`) first; never let an item overwrite `components\u002Fui\u002F*` or `lib\u002Futils.ts` silently. Then install.\n3. **Restyle and finish** (the \"Rules after every add\" in design-sources.md): literal colours, sizes, radii and shadows → the product's tokens; add hover, focus-visible, disabled, loading and reduced-motion behaviour if missing; remove duplicate dependencies.\n4. **Record** the source and licence in `docs\u002Fdesign\u002Fsources.md`. Premium (Pro\u002FMotion+) code never goes into a public repo.\n5. Verify in the running app (`next-dev-loop` or `visual-qa`); the PR goes through `\u002Fharden` like any other change.\n\n## In Cowork\n\nCowork plans and shows; the Code tab installs. Pick and show candidates here, write the choice into the ticket (\"cards: @kokonutui\u002F\u003Citem>, restyled to tokens, hover as component-states.md\"), and hand it to the Code tab via `build-handoff` \u002F `build-ticket`.\n","# UI sources\n\nimpeccable decides **how the product looks** (DESIGN.md). This skill decides **where each part comes from** and gets it into the code the right way. It never changes the look on its own: a new component is restyled to the existing tokens, and a change to the look goes through `grill-design` \u002F impeccable. Danish to the user, English in files.\n\nRead first: `..\u002Fdefine-design\u002Freferences\u002Fdesign-sources.md` (the sources, what each is for, install commands, licences, pitfalls, and \"Which source for what\"), then the project's `components.json`, `DESIGN.md` and `docs\u002Fdesign\u002Fcomponent-states.md` (its \"chosen source per component family\" wins over any new idea). Full evidence with source links: `..\u002Fdefine-toolchain\u002Freferences\u002Fdesign-sources.md`. Verify an install command on the source's docs (Context7 or the site's `llms.txt`) before running it.\n\n## 1. Pick the source (one winner per need)\n\nEvery source is broad: search all of them for the need, not only the one it's best known for (e.g. Aceternity has sidebars, tabs, modals, file upload, timelines and loaders; Magic UI has number tickers, animated lists, file trees, progress rings and bento grids; 21st.dev has AI chats, navigation, sign-ins and cards; Kokonut has AI inputs and buttons). The \"Which source for what\" table is a starting point, not a limit. Choose by fit: how well it serves the task, quality and accessibility, how easily it takes the product's tokens, performance, and licence. Rules:\n- The project's recorded choice wins: if component-states.md says \"charts: shadcn chart (Recharts)\", don't add Bklit next to it. A second chart stack, a second animation library (`framer-motion` next to `motion`) or a second icon set needs the user's explicit OK and a note in component-states.md.\n- Simple hover and enter states are Tailwind transitions, not Motion.\n- Judge an effect by where it sits, not by which site it's from. On a screen people work in every day, motion must support the task (show a change, guide attention, confirm an action), stay calm and fast, and respect reduced motion. Continuous canvas\u002FWebGL effects (globes, beams, shaders, 3D) belong where they don't slow down daily work; say the performance cost to the user when you suggest one.\n\n## 2. Show before choosing\n\nWhen the user asks \"how could this look\" or \"find something\", don't describe it: show 2-3 real candidates from the source (link plus a screenshot, or a small rendered artifact page using the product's tokens), each with one plain-Danish line on what it does and what it costs (free \u002F Pro). Let the user pick or say \"du bestemmer\" (log the choice in `docs\u002Fdesign\u002Fdecisions.md` like grill-design does). A choice that changes the look → `grill-design` pass C first.\n\n## 3. Put it into the product (Code tab)\n\n1. **Project setup, once per repo** (as a setup ticket if missing):\n   - `.mcp.json`: `\"shadcn\": { \"command\": \"npx\", \"args\": [\"shadcn@latest\", \"mcp\"] }`.\n   - `components.json` → `registries`: `\"@kokonutui\": \"https:\u002F\u002Fkokonutui.com\u002Fr\u002F{name}.json\"`, `\"@bklit\": \"https:\u002F\u002Fui.bklit.com\u002Fr\u002F{name}.json\"` (and `@magicui`, `@aceternity` only if the project uses them). Namespaces listed in the shadcn directory also work without this entry; writing it makes the source explicit.\n   - Motion: `npx motion-ai` (project install, Claude Code) adds Motion's MCP and skills; doc search is free, Motion+ features need the user's own sign-in.\n   - 21st.dev: only if the user wants it; its MCP needs the user's API key from 21st.dev, stored as an env variable, never in a file.\n2. **Install**: `npx shadcn@latest add @\u003Csource>\u002F\u003Citem> --dry-run` (or `--diff`) first; never let an item overwrite `components\u002Fui\u002F*` or `lib\u002Futils.ts` silently. Then install.\n3. **Restyle and finish** (the \"Rules after every add\" in design-sources.md): literal colours, sizes, radii and shadows → the product's tokens; add hover, focus-visible, disabled, loading and reduced-motion behaviour if missing; remove duplicate dependencies.\n4. **Record** the source and licence in `docs\u002Fdesign\u002Fsources.md`. Premium (Pro\u002FMotion+) code never goes into a public repo.\n5. Verify in the running app (`next-dev-loop` or `visual-qa`); the PR goes through `\u002Fharden` like any other change.\n\n## In Cowork\n\nCowork plans and shows; the Code tab installs. Pick and show candidates here, write the choice into the ticket (\"cards: @kokonutui\u002F\u003Citem>, restyled to tokens, hover as component-states.md\"), and hand it to the Code tab via `build-handoff` \u002F `build-ticket`.\n",{"name":5,"description":7},"main","337c4b675cfdf7b5e53e9311f3c757dac9123236","plugins\u002Fproduct-studio\u002Fskills\u002Fui-sources","https:\u002F\u002Fgithub.com\u002Fphillippasqualato\u002FPAPcSetup","https:\u002F\u002Fgithub.com\u002Fphillippasqualato","2026-10-07 04:02:12",{"source":8,"skillName":5,"commands":30,"prompt":40,"zipAvailable":41},[31,34,37],{"tool":32,"command":33},"npx","npx skills add phillippasqualato\u002FPAPcSetup --skill ui-sources",{"tool":35,"command":36},"bunx","bunx skills add phillippasqualato\u002FPAPcSetup --skill ui-sources",{"tool":38,"command":39},"pnpm","pnpm dlx skills add phillippasqualato\u002FPAPcSetup --skill ui-sources","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fphillippasqualato\u002FPAPcSetup\u002Fblob\u002Fmain\u002Fplugins\u002Fproduct-studio\u002Fskills\u002Fui-sources\u002FSKILL.md",true,[],[44,51,58,65,72,81],{"skillNo":45,"name":46,"nameZh":6,"description":47,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":48,"categories":49,"keywords":50,"publishedAt":18},"01M7DG6ZPZW6PW5DMB4EA5X6AG","writing-skills","Use when creating new skills, editing existing skills, or verifying skills work before deployment [Superpowers; user-invoked. Use to write or pressure-test a skill, e.g. product-studio changes.]","https:\u002F\u002Fgithub.com\u002Fphillippasqualato\u002FPAPcSetup\u002Fblob\u002Fmain\u002Fplugins\u002Fproduct-studio\u002Fskills\u002Fwriting-skills\u002FSKILL.md",[],[],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":18},"01M7DG6WK1GVEQN4F2PM7JRV43","writing-plans","Use when you have a spec or requirements for a multi-step task, before touching code [product-studio: canonical Code-tab execution, entered via build-ticket; user-invoked otherwise]","https:\u002F\u002Fgithub.com\u002Fphillippasqualato\u002FPAPcSetup\u002Fblob\u002Fmain\u002Fplugins\u002Fproduct-studio\u002Fskills\u002Fwriting-plans\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":18},"01M7DG6RZ6Q3VSTTKFH519WC21","writing-for-agents","Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.","https:\u002F\u002Fgithub.com\u002Fphillippasqualato\u002FPAPcSetup\u002Fblob\u002Fmain\u002Fplugins\u002Fproduct-studio\u002Fskills\u002Fwriting-for-agents\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":18},"01M7DG6N1WY2DRM3XP41SP4M0W","wizard","Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.","https:\u002F\u002Fgithub.com\u002Fphillippasqualato\u002FPAPcSetup\u002Fblob\u002Fmain\u002Fplugins\u002Fproduct-studio\u002Fskills\u002Fwizard\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":76,"licenseFileUrl":77,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":18},"01M7DG6HBW3X6CFPBDZG16BNVR","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs. [Python alternative to playwright-skill (canonical for scripted browser checks); user-invoked only.]","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fphillippasqualato\u002FPAPcSetup\u002Fblob\u002Fmain\u002Fplugins\u002Fproduct-studio\u002Fskills\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fphillippasqualato\u002FPAPcSetup\u002Fblob\u002Fmain\u002Fplugins\u002Fproduct-studio\u002Fskills\u002Fwebapp-testing\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":18},"01M7DG6E1K8KEPBHP6GGDTDG4W","web-design-guidelines","Review UI code for Web Interface Guidelines compliance. Use when asked to \"review my UI\", \"check accessibility\", \"audit design\", \"review UX\", or \"check my site against best practices\".","https:\u002F\u002Fgithub.com\u002Fphillippasqualato\u002FPAPcSetup\u002Fblob\u002Fmain\u002Fplugins\u002Fproduct-studio\u002Fskills\u002Fweb-design-guidelines\u002FSKILL.md",[],[]]