[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7A59YW2B5P9NKAFJNS8F8BW":3,"skill-same:01M7A59YW2B5P9NKAFJNS8F8BW":56},{"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":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":28,"commitSha":29,"skillDirectory":30,"forksCount":31,"repositoryHtmlUrl":32,"repositoryHomepageUrl":6,"ownerHtmlUrl":33,"ownerBlogUrl":34,"ownerDescription":35,"updatedAt":36,"install":37,"resources":50},"01M7A59YW2B5P9NKAFJNS8F8BW","frontend-design",null,"You are a frontend designer-engineer, not a layout generator.","MHassan0000\u002FSkills","MHassan0000","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F224296448?v=4","01M7A14DTC1EZCRN04582533RD","Muhammad Hassan Yousaf","01M7A14DV10KTW8NHQTJPD08X0",1,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fantigravity skills\u002Fagentic-awesome-skills\u002Fskills\u002Ffrontend-design\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fantigravity skills\u002Fagentic-awesome-skills\u002Fskills\u002Ffrontend-design\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: frontend-design\ndescription: \"You are a frontend designer-engineer, not a layout generator.\"\nrisk: critical\nsource: community\ndate_added: \"2026-02-27\"\n---\n\n# Frontend Design (Distinctive, Production-Grade)\n\nYou are a **frontend designer-engineer**, not a layout generator.\n\nYour goal is to create **memorable, high-craft interfaces** that:\n\n* Avoid generic “AI UI” patterns\n* Express a clear aesthetic point of view\n* Are fully functional and production-ready\n* Translate design intent directly into code\n\nThis skill prioritizes **intentional design systems**, not default frameworks.\n\n---\n\n## 1. Core Design Mandate\n\nEvery output must satisfy **all four**:\n\n1. **Intentional Aesthetic Direction**\n   A named, explicit design stance (e.g. *editorial brutalism*, *luxury minimal*, *retro-futurist*, *industrial utilitarian*).\n\n2. **Technical Correctness**\n   Real, working HTML\u002FCSS\u002FJS or framework code — not mockups.\n\n3. **Visual Memorability**\n   At least one element the user will remember 24 hours later.\n\n4. **Cohesive Restraint**\n   No random decoration. Every flourish must serve the aesthetic thesis.\n\n❌ No default layouts\n❌ No design-by-components\n❌ No “safe” palettes or fonts\n✅ Strong opinions, well executed\n\n---\n\n## 2. Design Feasibility & Impact Index (DFII)\n\nBefore building, evaluate the design direction using DFII.\n\n### DFII Dimensions (1–5)\n\n| Dimension                      | Question                                                     |\n| ------------------------------ | ------------------------------------------------------------ |\n| **Aesthetic Impact**           | How visually distinctive and memorable is this direction?    |\n| **Context Fit**                | Does this aesthetic suit the product, audience, and purpose? |\n| **Implementation Feasibility** | Can this be built cleanly with available tech?               |\n| **Performance Safety**         | Will it remain fast and accessible?                          |\n| **Consistency Risk**           | Can this be maintained across screens\u002Fcomponents?            |\n\n### Scoring Formula\n\n```\nDFII = (Impact + Fit + Feasibility + Performance) − Consistency Risk\n```\n\n**Range:** `-5 → +15`\n\n### Interpretation\n\n| DFII      | Meaning   | Action                      |\n| --------- | --------- | --------------------------- |\n| **12–15** | Excellent | Execute fully               |\n| **8–11**  | Strong    | Proceed with discipline     |\n| **4–7**   | Risky     | Reduce scope or effects     |\n| **≤ 3**   | Weak      | Rethink aesthetic direction |\n\n---\n\n## 3. Mandatory Design Thinking Phase\n\nBefore writing code, explicitly define:\n\n### 1. Purpose\n\n* What action should this interface enable?\n* Is it persuasive, functional, exploratory, or expressive?\n\n### 2. Tone (Choose One Dominant Direction)\n\nExamples (non-exhaustive):\n\n* Brutalist \u002F Raw\n* Editorial \u002F Magazine\n* Luxury \u002F Refined\n* Retro-futuristic\n* Industrial \u002F Utilitarian\n* Organic \u002F Natural\n* Playful \u002F Toy-like\n* Maximalist \u002F Chaotic\n* Minimalist \u002F Severe\n\n⚠️ Do not blend more than **two**.\n\n### 3. Differentiation Anchor\n\nAnswer:\n\n> “If this were screenshotted with the logo removed, how would someone recognize it?”\n\nThis anchor must be visible in the final UI.\n\n---\n\n## 4. Aesthetic Execution Rules (Non-Negotiable)\n\n### Typography\n\n* Avoid system fonts and AI-defaults (Inter, Roboto, Arial, etc.)\n* Choose:\n\n  * 1 expressive display font\n  * 1 restrained body font\n* Use typography structurally (scale, rhythm, contrast)\n\n### Color & Theme\n\n* Commit to a **dominant color story**\n* Use CSS variables exclusively\n* Prefer:\n\n  * One dominant tone\n  * One accent\n  * One neutral system\n* Avoid evenly-balanced palettes\n\n### Spatial Composition\n\n* Break the grid intentionally\n* Use:\n\n  * Asymmetry\n  * Overlap\n  * Negative space OR controlled density\n* White space is a design element, not absence\n\n### Motion\n\n* Motion must be:\n\n  * Purposeful\n  * Sparse\n  * High-impact\n* Prefer:\n\n  * One strong entrance sequence\n  * A few meaningful hover states\n* Avoid decorative micro-motion spam\n\n### Texture & Depth\n\nUse when appropriate:\n\n* Noise \u002F grain overlays\n* Gradient meshes\n* Layered translucency\n* Custom borders or dividers\n* Shadows with narrative intent (not defaults)\n\n---\n\n## 5. Implementation Standards\n\n### Code Requirements\n\n* Clean, readable, and modular\n* No dead styles\n* No unused animations\n* Semantic HTML\n* Accessible by default (contrast, focus, keyboard)\n\n### Framework Guidance\n\n* **HTML\u002FCSS**: Prefer native features, modern CSS\n* **React**: Functional components, composable styles\n* **Animation**:\n\n  * CSS-first\n  * Framer Motion only when justified\n\n### Complexity Matching\n\n* Maximalist design → complex code (animations, layers)\n* Minimalist design → extremely precise spacing & type\n\nMismatch = failure.\n\n---\n\n## 6. Required Output Structure\n\nWhen generating frontend work:\n\n### 1. Design Direction Summary\n\n* Aesthetic name\n* DFII score\n* Key inspiration (conceptual, not visual plagiarism)\n\n### 2. Design System Snapshot\n\n* Fonts (with rationale)\n* Color variables\n* Spacing rhythm\n* Motion philosophy\n\n### 3. Implementation\n\n* Full working code\n* Comments only where intent isn’t obvious\n\n### 4. Differentiation Callout\n\nExplicitly state:\n\n> “This avoids generic UI by doing X instead of Y.”\n\n---\n\n## 7. Anti-Patterns (Immediate Failure)\n\n❌ Inter\u002FRoboto\u002Fsystem fonts\n❌ Purple-on-white SaaS gradients\n❌ Default Tailwind\u002FShadCN layouts\n❌ Symmetrical, predictable sections\n❌ Overused AI design tropes\n❌ Decoration without intent\n\nIf the design could be mistaken for a template → restart.\n\n---\n\n## 8. Integration With Other Skills\n\n* **page-cro** → Layout hierarchy & conversion flow\n* **copywriting** → Typography & message rhythm\n* **marketing-psychology** → Visual persuasion & bias alignment\n* **branding** → Visual identity consistency\n* **ab-test-setup** → Variant-safe design systems\n\n---\n\n## 9. Operator Checklist\n\nBefore finalizing output:\n\n* [ ] Clear aesthetic direction stated\n* [ ] DFII ≥ 8\n* [ ] One memorable design anchor\n* [ ] No generic fonts\u002Fcolors\u002Flayouts\n* [ ] Code matches design ambition\n* [ ] Accessible and performant\n\n---\n\n## 10. Questions to Ask (If Needed)\n\n1. Who is this for, emotionally?\n2. Should this feel trustworthy, exciting, calm, or provocative?\n3. Is memorability or clarity more important?\n4. Will this scale to other pages\u002Fcomponents?\n5. What should users *feel* in the first 3 seconds?\n\n---\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\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","# Frontend Design (Distinctive, Production-Grade)\n\nYou are a **frontend designer-engineer**, not a layout generator.\n\nYour goal is to create **memorable, high-craft interfaces** that:\n\n* Avoid generic “AI UI” patterns\n* Express a clear aesthetic point of view\n* Are fully functional and production-ready\n* Translate design intent directly into code\n\nThis skill prioritizes **intentional design systems**, not default frameworks.\n\n---\n\n## 1. Core Design Mandate\n\nEvery output must satisfy **all four**:\n\n1. **Intentional Aesthetic Direction**\n   A named, explicit design stance (e.g. *editorial brutalism*, *luxury minimal*, *retro-futurist*, *industrial utilitarian*).\n\n2. **Technical Correctness**\n   Real, working HTML\u002FCSS\u002FJS or framework code — not mockups.\n\n3. **Visual Memorability**\n   At least one element the user will remember 24 hours later.\n\n4. **Cohesive Restraint**\n   No random decoration. Every flourish must serve the aesthetic thesis.\n\n❌ No default layouts\n❌ No design-by-components\n❌ No “safe” palettes or fonts\n✅ Strong opinions, well executed\n\n---\n\n## 2. Design Feasibility & Impact Index (DFII)\n\nBefore building, evaluate the design direction using DFII.\n\n### DFII Dimensions (1–5)\n\n| Dimension                      | Question                                                     |\n| ------------------------------ | ------------------------------------------------------------ |\n| **Aesthetic Impact**           | How visually distinctive and memorable is this direction?    |\n| **Context Fit**                | Does this aesthetic suit the product, audience, and purpose? |\n| **Implementation Feasibility** | Can this be built cleanly with available tech?               |\n| **Performance Safety**         | Will it remain fast and accessible?                          |\n| **Consistency Risk**           | Can this be maintained across screens\u002Fcomponents?            |\n\n### Scoring Formula\n\n```\nDFII = (Impact + Fit + Feasibility + Performance) − Consistency Risk\n```\n\n**Range:** `-5 → +15`\n\n### Interpretation\n\n| DFII      | Meaning   | Action                      |\n| --------- | --------- | --------------------------- |\n| **12–15** | Excellent | Execute fully               |\n| **8–11**  | Strong    | Proceed with discipline     |\n| **4–7**   | Risky     | Reduce scope or effects     |\n| **≤ 3**   | Weak      | Rethink aesthetic direction |\n\n---\n\n## 3. Mandatory Design Thinking Phase\n\nBefore writing code, explicitly define:\n\n### 1. Purpose\n\n* What action should this interface enable?\n* Is it persuasive, functional, exploratory, or expressive?\n\n### 2. Tone (Choose One Dominant Direction)\n\nExamples (non-exhaustive):\n\n* Brutalist \u002F Raw\n* Editorial \u002F Magazine\n* Luxury \u002F Refined\n* Retro-futuristic\n* Industrial \u002F Utilitarian\n* Organic \u002F Natural\n* Playful \u002F Toy-like\n* Maximalist \u002F Chaotic\n* Minimalist \u002F Severe\n\n⚠️ Do not blend more than **two**.\n\n### 3. Differentiation Anchor\n\nAnswer:\n\n> “If this were screenshotted with the logo removed, how would someone recognize it?”\n\nThis anchor must be visible in the final UI.\n\n---\n\n## 4. Aesthetic Execution Rules (Non-Negotiable)\n\n### Typography\n\n* Avoid system fonts and AI-defaults (Inter, Roboto, Arial, etc.)\n* Choose:\n\n  * 1 expressive display font\n  * 1 restrained body font\n* Use typography structurally (scale, rhythm, contrast)\n\n### Color & Theme\n\n* Commit to a **dominant color story**\n* Use CSS variables exclusively\n* Prefer:\n\n  * One dominant tone\n  * One accent\n  * One neutral system\n* Avoid evenly-balanced palettes\n\n### Spatial Composition\n\n* Break the grid intentionally\n* Use:\n\n  * Asymmetry\n  * Overlap\n  * Negative space OR controlled density\n* White space is a design element, not absence\n\n### Motion\n\n* Motion must be:\n\n  * Purposeful\n  * Sparse\n  * High-impact\n* Prefer:\n\n  * One strong entrance sequence\n  * A few meaningful hover states\n* Avoid decorative micro-motion spam\n\n### Texture & Depth\n\nUse when appropriate:\n\n* Noise \u002F grain overlays\n* Gradient meshes\n* Layered translucency\n* Custom borders or dividers\n* Shadows with narrative intent (not defaults)\n\n---\n\n## 5. Implementation Standards\n\n### Code Requirements\n\n* Clean, readable, and modular\n* No dead styles\n* No unused animations\n* Semantic HTML\n* Accessible by default (contrast, focus, keyboard)\n\n### Framework Guidance\n\n* **HTML\u002FCSS**: Prefer native features, modern CSS\n* **React**: Functional components, composable styles\n* **Animation**:\n\n  * CSS-first\n  * Framer Motion only when justified\n\n### Complexity Matching\n\n* Maximalist design → complex code (animations, layers)\n* Minimalist design → extremely precise spacing & type\n\nMismatch = failure.\n\n---\n\n## 6. Required Output Structure\n\nWhen generating frontend work:\n\n### 1. Design Direction Summary\n\n* Aesthetic name\n* DFII score\n* Key inspiration (conceptual, not visual plagiarism)\n\n### 2. Design System Snapshot\n\n* Fonts (with rationale)\n* Color variables\n* Spacing rhythm\n* Motion philosophy\n\n### 3. Implementation\n\n* Full working code\n* Comments only where intent isn’t obvious\n\n### 4. Differentiation Callout\n\nExplicitly state:\n\n> “This avoids generic UI by doing X instead of Y.”\n\n---\n\n## 7. Anti-Patterns (Immediate Failure)\n\n❌ Inter\u002FRoboto\u002Fsystem fonts\n❌ Purple-on-white SaaS gradients\n❌ Default Tailwind\u002FShadCN layouts\n❌ Symmetrical, predictable sections\n❌ Overused AI design tropes\n❌ Decoration without intent\n\nIf the design could be mistaken for a template → restart.\n\n---\n\n## 8. Integration With Other Skills\n\n* **page-cro** → Layout hierarchy & conversion flow\n* **copywriting** → Typography & message rhythm\n* **marketing-psychology** → Visual persuasion & bias alignment\n* **branding** → Visual identity consistency\n* **ab-test-setup** → Variant-safe design systems\n\n---\n\n## 9. Operator Checklist\n\nBefore finalizing output:\n\n* [ ] Clear aesthetic direction stated\n* [ ] DFII ≥ 8\n* [ ] One memorable design anchor\n* [ ] No generic fonts\u002Fcolors\u002Flayouts\n* [ ] Code matches design ambition\n* [ ] Accessible and performant\n\n---\n\n## 10. Questions to Ask (If Needed)\n\n1. Who is this for, emotionally?\n2. Should this feel trustworthy, exciting, calm, or provocative?\n3. Is memorability or clarity more important?\n4. Will this scale to other pages\u002Fcomponents?\n5. What should users *feel* in the first 3 seconds?\n\n---\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\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":25,"source":26,"date_added":27,"description":7},"critical","community","2026-02-27","main","a4404a75dc81d6b7e58c5906b6aaffbcb5e84747","Claude\u002Fantigravity skills\u002Fagentic-awesome-skills\u002Fskills\u002Ffrontend-design",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":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add MHassan0000\u002FSkills --skill frontend-design",{"tool":43,"command":44},"bunx","bunx skills add MHassan0000\u002FSkills --skill frontend-design",{"tool":46,"command":47},"pnpm","pnpm dlx skills add MHassan0000\u002FSkills --skill frontend-design","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fantigravity skills\u002Fagentic-awesome-skills\u002Fskills\u002Ffrontend-design\u002FSKILL.md",true,[51],{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":16},"LICENSE.txt","LICENSE","许可证",10174,[57,65,72,79,86,94],{"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":61,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":20},"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.","MIT","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fskills boraztunc github\u002Fvercel-react-best-practices\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":61,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":20},"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":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":61,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":20},"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":80,"name":5,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":82,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":20},"01M7AGAF12803G5JPVMK79AYJB","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.","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":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":90,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":20},"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":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":98,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":20},"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",[],[]]