[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7A9431C0RJ73D2FMYMX96AS":3,"skill-same:01M7A9431C0RJ73D2FMYMX96AS":53},{"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":30,"commitSha":31,"skillDirectory":32,"forksCount":33,"repositoryHtmlUrl":34,"repositoryHomepageUrl":6,"ownerHtmlUrl":35,"ownerBlogUrl":36,"ownerDescription":37,"updatedAt":38,"install":39,"resources":52},"01M7A9431C0RJ73D2FMYMX96AS","ui-score",null,"Score a UI file's design quality 0-100 against StyleSeed's design language — per-category breakdown, the worst offenders, and a prioritized fix list. A quantified version of \u002Fss-review.","MHassan0000\u002FSkills","MHassan0000","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F224296448?v=4","01M7A14DTC1EZCRN04582533RD","Muhammad Hassan Yousaf","01M7A14DV10KTW8NHQTJPD08X0",1,"MIT","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fantigravity skills\u002Fagentic-awesome-skills\u002Fskills\u002Fui-score\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: ui-score\ndescription: Score a UI file's design quality 0-100 against StyleSeed's design language — per-category breakdown, the worst offenders, and a prioritized fix list. A quantified version of \u002Fss-review.\nrisk: critical\nsource: https:\u002F\u002Fgithub.com\u002Fbitjaru\u002Fstyleseed\u002Ftree\u002Fmain\u002Fengine\u002F.claude\u002Fskills\u002Fss-score\nsource_repo: bitjaru\u002Fstyleseed\nsource_type: community\ndate_added: 2026-07-01\nlicense: MIT\nlicense_source: https:\u002F\u002Fgithub.com\u002Fbitjaru\u002Fstyleseed\u002Fblob\u002Fmain\u002FLICENSE\n---\n\n# Design Score\n## When to Use\n\nUse this skill when you need score a UI file's design quality 0-100 against StyleSeed's design language — per-category breakdown, the worst offenders, and a prioritized fix list. A quantified version of \u002Fss-review.\n\n\n`\u002Fss-review` tells you *what's wrong*. `\u002Fss-score` tells you *how good it is\noverall* and *what to fix first* — a single number plus a category breakdown, so\nyou can track UI quality like you track test coverage.\n\n## When NOT to use\n\n- For a quick pass\u002Ffail before committing → use `\u002Fss-lint`\n- For a full prose audit with fixes → use `\u002Fss-review`\n- For non-UI files (logic, config) — scoring is meaningless\n\n## What to score\n\nScore the file (or each file in a directory) on **six weighted categories** that\nmap to the design language. Total = 100.\n\n| Category | Weight | Reads from |\n|---|---|---|\n| **Color discipline** | 18 | DESIGN-LANGUAGE §1, §18, §72 + VISUAL-CRAFT §C4 |\n| **Hierarchy & typography** | 18 | §2, §3, §4, §16 + Font Size table + VISUAL-CRAFT §C2 |\n| **Layout & rhythm** | 14 | §13, §14, §15, §61 + VISUAL-CRAFT §C1 |\n| **Cards & elevation** | 12 | §7, §8, §12, §1 + VISUAL-CRAFT §C3 |\n| **States & a11y** | 18 | §11, §70, §71, §72 + VISUAL-CRAFT §C3 |\n| **Motion & interaction** | 8 | §24, §59 + `engine\u002Fmotion` |\n| **Coherence** | 12 | VISUAL-CRAFT §C0 (one choice per axis) |\n\n## How to score each category\n\nFor each category, start at full marks and **subtract** for violations you find by\nreading the code. Be specific and evidence-based — cite the line.\n\n**Color discipline (20)** — deduct for: any `#000`\u002F`text-black` (−4 each, cap −8);\nmore than one accent hue used decoratively (−5); **emoji used as UI icons** (multi-color,\nbreaks single accent) (−5); **a normal\u002FOK\u002F\"보통\" state shown in a status color** instead of\nneutral grey (−4); **status color on most\u002Fevery row** (no severity hierarchy) (−4);\n**decorative hues** (gold stars, rainbow category dots) instead of accent\u002Fgrey (−3);\nhardcoded hex where a semantic token exists (−2 each, cap −6); status conveyed by color\nalone (−4).\n\n**Hierarchy & typography (20)** — deduct for: number\u002Funit not ~2:1 (−4); font\nsizes off the Font Size table \u002F `text-[var(--…)]` for size (−5); everything the\nsame weight, no clear primary (−5); cramped or wrong line-height on body (−3).\n\n**Layout & rhythm (15)** — deduct for: content on bare background, not in cards\n(−6); `px-4`\u002F`px-8`\u002F`mx-4` instead of `px-6`\u002F`mx-6` (−3); same section type\nrepeated in a row (−4); no `space-y-6` rhythm (−3).\n\n**Cards & elevation (15)** — deduct for: 1px borders doing separation work that\ntone+shadow should (−4); shadows over ~8% opacity \u002F visibly heavy (−4); no\ncard\u002Fbackground tone separation (−5).\n\n**States & a11y (20)** — deduct for: missing empty\u002Floading\u002Ferror state on a data\nsurface (−5 each, cap −10); contrast below 4.5:1 body \u002F 3:1 large (−6); touch\ntarget \u003C 44px (−4); no visible focus \u002F `outline:none` (−5); icon-only control\nwithout `aria-label` (−3).\n\n**Motion & interaction (8)** — deduct for: random\u002Fad-hoc fades instead of a named\nseed\u002Fkeyword (−3); motion that delays content or blocks an action (−4); no\n`prefers-reduced-motion` handling on custom motion (−3); scroll-linked\u002Fparallax\n(forbidden, §59) (−5).\n\n**Coherence (12)** — the \"one choice per axis\" laws (VISUAL-CRAFT §C0). Deduct for\neach axis that is *mixed* rather than unified across the file: mixed radius\npersonalities, e.g. sharp panel + pill buttons (−5); two+ competing accent hues used\nfor emphasis (−4); mixed shadow languages \u002F light directions (−3); mixed icon\nfamilies, fill modes, or stroke weights (−3); same radius on a nested element instead\nof `inner = outer − padding` (−2); inconsistent control heights for buttons\u002Finputs\n(−2). This is the category that most predicts \"looks AI-generated\" — weight evidence\nof system-wide consistency, not per-component prettiness.\n\nClamp each category at 0. Sum to a total.\n\n## Output format\n\n```\n## Design Score: 70 \u002F 100   (src\u002Fapp\u002FDashboard.tsx)\n\n████████████████░░░░░░  C-\n\nColor discipline      13\u002F18   ▓▓▓░  #000 headings (l.12,40); orange+blue+green accents (l.28-34)\nHierarchy & typography 15\u002F18  ▓▓▓▓  number\u002Funit 1:1 on hero (l.18)\nLayout & rhythm        11\u002F14  ▓▓▓░  two identical KPI rows (l.22-31)\nCards & elevation       8\u002F12  ▓▓░░  1px borders doing separation (l.22)\nStates & a11y          11\u002F18  ▓▓░░  no empty\u002Floading state; focus ring missing (l.55)\nMotion & interaction    6\u002F8   ▓▓▓░  default fade, not a named seed\nCoherence               6\u002F12  ▓▓░░  sharp cards (l.22) + pill buttons (l.48); 3 accent hues (§C0)\n\n### Fix first (highest score gain)\n1. Add empty + loading states to the orders list       → +7 states (§71)\n2. Unify radius (pick soft 8-12px) + collapse to one accent → +9 coherence+color (§C0, §2)\n3. Drop the 1px borders, use tone + ≤8% shadow         → +4 cards  (§7)\n\nRe-score after: ~92 \u002F 100.\n```\n\nUse letter bands: 90+ A · 80-89 B · 70-79 C · 60-69 D · \u003C60 F.\n\n## Gate mode (use this as the Quality Gate before showing the user UI)\n\nThe Quality Gate (CLAUDE.md \u002F AGENTS.md) is `\u002Fss-score` run as a loop, not a one-off:\n\n1. Score the just-generated UI.\n2. If **\u003C 80**, apply the \"fix first\" list (use `\u002Fss-review` to make the edits), then **re-score**.\n3. Repeat up to ~3×, or until ≥ 80.\n4. Present the UI with the final score and a one-line \"fixed: …\".\n\nThe pass bar is a **floor, not a ceiling** — get to ≥ 80 and stop; don't chase 100. The point\nis that no first-draft, obviously-incoherent UI reaches the user. Especially never ship below\n80 with a rainbow status list, emoji icons, two accents, or missing states — those are the\nexact tells the gate exists to catch.\n\n## Rules\n\n- **Read the file** — score from real evidence (line numbers), never guess.\n- Order the \"fix first\" list by **score gain**, not by severity alone — the goal\n  is the fastest path to a better number.\n- For a directory, print a one-line score per file, then the lowest-scoring file's\n  full breakdown.\n- Don't auto-edit in plain scoring. `\u002Fss-score` measures; `\u002Fss-review` and `\u002Fss-motion` fix.\n  In **Gate mode** (above) you do fix-and-re-score until the floor is met.\n- As a *gate*, ≥ 80 is a floor before showing the user — but don't over-polish: chasing 95→100\n  to delay shipping is worse than shipping a clean 85.\n\n## Limitations\n\n- Use this skill only when the task clearly matches its upstream source and local project context.\n- Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.\n- Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.\n","# Design Score\n## When to Use\n\nUse this skill when you need score a UI file's design quality 0-100 against StyleSeed's design language — per-category breakdown, the worst offenders, and a prioritized fix list. A quantified version of \u002Fss-review.\n\n\n`\u002Fss-review` tells you *what's wrong*. `\u002Fss-score` tells you *how good it is\noverall* and *what to fix first* — a single number plus a category breakdown, so\nyou can track UI quality like you track test coverage.\n\n## When NOT to use\n\n- For a quick pass\u002Ffail before committing → use `\u002Fss-lint`\n- For a full prose audit with fixes → use `\u002Fss-review`\n- For non-UI files (logic, config) — scoring is meaningless\n\n## What to score\n\nScore the file (or each file in a directory) on **six weighted categories** that\nmap to the design language. Total = 100.\n\n| Category | Weight | Reads from |\n|---|---|---|\n| **Color discipline** | 18 | DESIGN-LANGUAGE §1, §18, §72 + VISUAL-CRAFT §C4 |\n| **Hierarchy & typography** | 18 | §2, §3, §4, §16 + Font Size table + VISUAL-CRAFT §C2 |\n| **Layout & rhythm** | 14 | §13, §14, §15, §61 + VISUAL-CRAFT §C1 |\n| **Cards & elevation** | 12 | §7, §8, §12, §1 + VISUAL-CRAFT §C3 |\n| **States & a11y** | 18 | §11, §70, §71, §72 + VISUAL-CRAFT §C3 |\n| **Motion & interaction** | 8 | §24, §59 + `engine\u002Fmotion` |\n| **Coherence** | 12 | VISUAL-CRAFT §C0 (one choice per axis) |\n\n## How to score each category\n\nFor each category, start at full marks and **subtract** for violations you find by\nreading the code. Be specific and evidence-based — cite the line.\n\n**Color discipline (20)** — deduct for: any `#000`\u002F`text-black` (−4 each, cap −8);\nmore than one accent hue used decoratively (−5); **emoji used as UI icons** (multi-color,\nbreaks single accent) (−5); **a normal\u002FOK\u002F\"보통\" state shown in a status color** instead of\nneutral grey (−4); **status color on most\u002Fevery row** (no severity hierarchy) (−4);\n**decorative hues** (gold stars, rainbow category dots) instead of accent\u002Fgrey (−3);\nhardcoded hex where a semantic token exists (−2 each, cap −6); status conveyed by color\nalone (−4).\n\n**Hierarchy & typography (20)** — deduct for: number\u002Funit not ~2:1 (−4); font\nsizes off the Font Size table \u002F `text-[var(--…)]` for size (−5); everything the\nsame weight, no clear primary (−5); cramped or wrong line-height on body (−3).\n\n**Layout & rhythm (15)** — deduct for: content on bare background, not in cards\n(−6); `px-4`\u002F`px-8`\u002F`mx-4` instead of `px-6`\u002F`mx-6` (−3); same section type\nrepeated in a row (−4); no `space-y-6` rhythm (−3).\n\n**Cards & elevation (15)** — deduct for: 1px borders doing separation work that\ntone+shadow should (−4); shadows over ~8% opacity \u002F visibly heavy (−4); no\ncard\u002Fbackground tone separation (−5).\n\n**States & a11y (20)** — deduct for: missing empty\u002Floading\u002Ferror state on a data\nsurface (−5 each, cap −10); contrast below 4.5:1 body \u002F 3:1 large (−6); touch\ntarget \u003C 44px (−4); no visible focus \u002F `outline:none` (−5); icon-only control\nwithout `aria-label` (−3).\n\n**Motion & interaction (8)** — deduct for: random\u002Fad-hoc fades instead of a named\nseed\u002Fkeyword (−3); motion that delays content or blocks an action (−4); no\n`prefers-reduced-motion` handling on custom motion (−3); scroll-linked\u002Fparallax\n(forbidden, §59) (−5).\n\n**Coherence (12)** — the \"one choice per axis\" laws (VISUAL-CRAFT §C0). Deduct for\neach axis that is *mixed* rather than unified across the file: mixed radius\npersonalities, e.g. sharp panel + pill buttons (−5); two+ competing accent hues used\nfor emphasis (−4); mixed shadow languages \u002F light directions (−3); mixed icon\nfamilies, fill modes, or stroke weights (−3); same radius on a nested element instead\nof `inner = outer − padding` (−2); inconsistent control heights for buttons\u002Finputs\n(−2). This is the category that most predicts \"looks AI-generated\" — weight evidence\nof system-wide consistency, not per-component prettiness.\n\nClamp each category at 0. Sum to a total.\n\n## Output format\n\n```\n## Design Score: 70 \u002F 100   (src\u002Fapp\u002FDashboard.tsx)\n\n████████████████░░░░░░  C-\n\nColor discipline      13\u002F18   ▓▓▓░  #000 headings (l.12,40); orange+blue+green accents (l.28-34)\nHierarchy & typography 15\u002F18  ▓▓▓▓  number\u002Funit 1:1 on hero (l.18)\nLayout & rhythm        11\u002F14  ▓▓▓░  two identical KPI rows (l.22-31)\nCards & elevation       8\u002F12  ▓▓░░  1px borders doing separation (l.22)\nStates & a11y          11\u002F18  ▓▓░░  no empty\u002Floading state; focus ring missing (l.55)\nMotion & interaction    6\u002F8   ▓▓▓░  default fade, not a named seed\nCoherence               6\u002F12  ▓▓░░  sharp cards (l.22) + pill buttons (l.48); 3 accent hues (§C0)\n\n### Fix first (highest score gain)\n1. Add empty + loading states to the orders list       → +7 states (§71)\n2. Unify radius (pick soft 8-12px) + collapse to one accent → +9 coherence+color (§C0, §2)\n3. Drop the 1px borders, use tone + ≤8% shadow         → +4 cards  (§7)\n\nRe-score after: ~92 \u002F 100.\n```\n\nUse letter bands: 90+ A · 80-89 B · 70-79 C · 60-69 D · \u003C60 F.\n\n## Gate mode (use this as the Quality Gate before showing the user UI)\n\nThe Quality Gate (CLAUDE.md \u002F AGENTS.md) is `\u002Fss-score` run as a loop, not a one-off:\n\n1. Score the just-generated UI.\n2. If **\u003C 80**, apply the \"fix first\" list (use `\u002Fss-review` to make the edits), then **re-score**.\n3. Repeat up to ~3×, or until ≥ 80.\n4. Present the UI with the final score and a one-line \"fixed: …\".\n\nThe pass bar is a **floor, not a ceiling** — get to ≥ 80 and stop; don't chase 100. The point\nis that no first-draft, obviously-incoherent UI reaches the user. Especially never ship below\n80 with a rainbow status list, emoji icons, two accents, or missing states — those are the\nexact tells the gate exists to catch.\n\n## Rules\n\n- **Read the file** — score from real evidence (line numbers), never guess.\n- Order the \"fix first\" list by **score gain**, not by severity alone — the goal\n  is the fastest path to a better number.\n- For a directory, print a one-line score per file, then the lowest-scoring file's\n  full breakdown.\n- Don't auto-edit in plain scoring. `\u002Fss-score` measures; `\u002Fss-review` and `\u002Fss-motion` fix.\n  In **Gate mode** (above) you do fix-and-re-score until the floor is met.\n- As a *gate*, ≥ 80 is a floor before showing the user — but don't over-polish: chasing 95→100\n  to delay shipping is worse than shipping a clean 85.\n\n## Limitations\n\n- Use this skill only when the task clearly matches its upstream source and local project context.\n- Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.\n- Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.\n",{"name":5,"risk":24,"source":25,"license":15,"date_added":26,"description":7,"source_repo":27,"source_type":28,"license_source":29},"critical","https:\u002F\u002Fgithub.com\u002Fbitjaru\u002Fstyleseed\u002Ftree\u002Fmain\u002Fengine\u002F.claude\u002Fskills\u002Fss-score",1782864000000,"bitjaru\u002Fstyleseed","community","https:\u002F\u002Fgithub.com\u002Fbitjaru\u002Fstyleseed\u002Fblob\u002Fmain\u002FLICENSE","main","a4404a75dc81d6b7e58c5906b6aaffbcb5e84747","Claude\u002Fantigravity skills\u002Fagentic-awesome-skills\u002Fskills\u002Fui-score",0,"https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills","https:\u002F\u002Fgithub.com\u002FMHassan0000","https:\u002F\u002Fhassanyousaf.vercel.app","Full Stack Developer building web apps, SaaS, AI systems, and automations. Passionate about clean code, UI\u002FUX, backend systems, and turning ideas into products.","2026-08-07 20:42:05",{"source":8,"skillName":5,"commands":40,"prompt":50,"zipAvailable":51},[41,44,47],{"tool":42,"command":43},"npx","npx skills add MHassan0000\u002FSkills --skill ui-score",{"tool":45,"command":46},"bunx","bunx skills add MHassan0000\u002FSkills --skill ui-score",{"tool":48,"command":49},"pnpm","pnpm dlx skills add MHassan0000\u002FSkills --skill ui-score","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fantigravity skills\u002Fagentic-awesome-skills\u002Fskills\u002Fui-score\u002FSKILL.md",true,[],[54,61,68,75,84,92],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M7AGBX58S04DX8DKKME8N311","vercel-react-best-practices","React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React\u002FNext.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fskills boraztunc github\u002Fvercel-react-best-practices\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7AGBREE890608Z7YDMAKH27","stop-slop","Remove AI writing patterns from prose. Use when drafting, editing, or reviewing text to eliminate predictable AI tells and produce more human-like writing.","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fskills boraztunc github\u002Fstop-slop\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7AGAS972A2AN7Q5EW8HEAXK","ogilvy-copywriting","Apply David Ogilvy's advertising principles when writing or reviewing copy, headlines, product descriptions, landing pages, ads, emails, or any persuasive text. Use when the goal is copy that sells, not copy that wins awards. Covers positioning, headlines, promises, brand voice, long-form copy, and visual logic. Source: How to Create Advertising That Sells (1972) + Ogilvy on Advertising.","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fskills boraztunc github\u002Fogilvy\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":79,"licenseFileUrl":80,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7AGAF12803G5JPVMK79AYJB","frontend-design","Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML\u002FCSS layouts, or when styling\u002Fbeautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fskills boraztunc github\u002Ffrontend-design\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fskills boraztunc github\u002Ffrontend-design\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":79,"licenseFileUrl":88,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7AG88WWVWCGJY9WA9CH7EY4","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.","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fobra superpower skills\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fobra superpower skills\u002Fwebapp-testing\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":79,"licenseFileUrl":96,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M7AG7ZTNV7XQCWDQ9674FBYB","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fobra superpower skills\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fobra superpower skills\u002Fweb-artifacts-builder\u002FSKILL.md",[],[]]