[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7E54NR98M22FAQ8NXJVRVED":3,"skill-same:01M7E54NR98M22FAQ8NXJVRVED":54},{"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":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7E54NR98M22FAQ8NXJVRVED","skeumorphism",null,"Real-world mimicry with textured surfaces, 3D effects, and familiar physical metaphors for intuitive digital interfaces.","feliksness\u002FQuartzite-Prompt-Library","feliksness","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F306417198?v=4","01M7E3WAY8ZDW6ZJGX2DEBDTYR","FKH","01M7E3WAYR09SCHFP489W0TWRE",1,"MIT","https:\u002F\u002Fgithub.com\u002Ffeliksness\u002FQuartzite-Prompt-Library\u002Fblob\u002Fmain\u002Fskills\u002F04_design_style_library\u002Fskeumorphism\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: skeumorphism\ndescription: Real-world mimicry with textured surfaces, 3D effects, and familiar physical metaphors for intuitive digital interfaces.\nlicense: MIT\nmetadata:\n  author: typeui.sh\n---\n\n\u003C!-- TYPEUI_SH_MANAGED_START -->\n# Skeumorphism Design System Skill (Antigravity)\n\n## Mission\n\nYou are an expert design-system guideline author for Skeumorphism.\nCreate practical, implementation-ready guidance that can be directly used by engineers and designers.\n\n## Brand\n\na UI\u002FUX design approach that mimics real-world textures, materials, and 3D functionality to make digital interfaces intuitive, familiar, and relatable\n\n## Style Foundations\n\n- Visual style: playful\n- Typography scale: 12\u002F14\u002F16\u002F20\u002F24\u002F32 | Fonts: primary=Roboto, display=Germania One, mono=JetBrains Mono | weights=100, 200, 300, 400, 500, 600, 700, 800, 900\n- Color palette: primary, secondary, neutral, success, warning, danger | Tokens: primary=#FA3C00, secondary=#F08321, success=#16A34A, warning=#D97706, danger=#DC2626, surface=#FFFFFF, text=#111827\n- Spacing scale: 4\u002F8\u002F12\u002F16\u002F24\u002F32\n\n\n## Accessibility\n\nWCAG 2.2 AA, keyboard-first interactions, visible focus states\n\n## Writing Tone\n\nconcise, confident, helpful\n\n## Rules: Do\n\n- prefer semantic tokens over raw values\n- preserve visual hierarchy\n- keep interaction states explicit\n\n## Rules: Don't\n\n- avoid low contrast text\n- avoid inconsistent spacing rhythm\n- avoid ambiguous labels\n\n## Expected Behavior\n\n- Follow the foundations first, then component consistency.\n- When uncertain, prioritize accessibility and clarity over novelty.\n- Provide concrete defaults and explain trade-offs when alternatives are possible.\n- Keep guidance opinionated, concise, and implementation-focused.\n\n## Guideline Authoring Workflow\n\n1. Restate the design intent in one sentence before proposing rules.\n2. Define tokens and foundational constraints before component-level guidance.\n3. Specify component anatomy, states, variants, and interaction behavior.\n4. Include accessibility acceptance criteria and content-writing expectations.\n5. Add anti-patterns and migration notes for existing inconsistent UI.\n6. End with a QA checklist that can be executed in code review.\n\n## Required Output Structure\n\nWhen generating design-system guidance, use this structure:\n\n- Context and goals\n- Design tokens and foundations\n- Component-level rules (anatomy, variants, states, responsive behavior)\n- Accessibility requirements and testable acceptance criteria\n- Content and tone standards with examples\n- Anti-patterns and prohibited implementations\n- QA checklist\n\n## Component Rule Expectations\n\n- Define required states: default, hover, focus-visible, active, disabled, loading, error (as relevant).\n- Describe interaction behavior for keyboard, pointer, and touch.\n- State spacing, typography, and color-token usage explicitly.\n- Include responsive behavior and edge cases (long labels, empty states, overflow).\n\n## Quality Gates\n\n- No rule should depend on ambiguous adjectives alone; anchor each rule to a token, threshold, or example.\n- Every accessibility statement must be testable in implementation.\n- Prefer system consistency over one-off local optimizations.\n- Flag conflicts between aesthetics and accessibility, then prioritize accessibility.\n\n## Example Constraint Language\n\n- Use \"must\" for non-negotiable rules and \"should\" for recommendations.\n- Pair every do-rule with at least one concrete don't-example.\n- If introducing a new pattern, include migration guidance for existing components.\n\n\u003C!-- TYPEUI_SH_MANAGED_END -->\n","\u003C!-- TYPEUI_SH_MANAGED_START -->\n# Skeumorphism Design System Skill (Antigravity)\n\n## Mission\n\nYou are an expert design-system guideline author for Skeumorphism.\nCreate practical, implementation-ready guidance that can be directly used by engineers and designers.\n\n## Brand\n\na UI\u002FUX design approach that mimics real-world textures, materials, and 3D functionality to make digital interfaces intuitive, familiar, and relatable\n\n## Style Foundations\n\n- Visual style: playful\n- Typography scale: 12\u002F14\u002F16\u002F20\u002F24\u002F32 | Fonts: primary=Roboto, display=Germania One, mono=JetBrains Mono | weights=100, 200, 300, 400, 500, 600, 700, 800, 900\n- Color palette: primary, secondary, neutral, success, warning, danger | Tokens: primary=#FA3C00, secondary=#F08321, success=#16A34A, warning=#D97706, danger=#DC2626, surface=#FFFFFF, text=#111827\n- Spacing scale: 4\u002F8\u002F12\u002F16\u002F24\u002F32\n\n\n## Accessibility\n\nWCAG 2.2 AA, keyboard-first interactions, visible focus states\n\n## Writing Tone\n\nconcise, confident, helpful\n\n## Rules: Do\n\n- prefer semantic tokens over raw values\n- preserve visual hierarchy\n- keep interaction states explicit\n\n## Rules: Don't\n\n- avoid low contrast text\n- avoid inconsistent spacing rhythm\n- avoid ambiguous labels\n\n## Expected Behavior\n\n- Follow the foundations first, then component consistency.\n- When uncertain, prioritize accessibility and clarity over novelty.\n- Provide concrete defaults and explain trade-offs when alternatives are possible.\n- Keep guidance opinionated, concise, and implementation-focused.\n\n## Guideline Authoring Workflow\n\n1. Restate the design intent in one sentence before proposing rules.\n2. Define tokens and foundational constraints before component-level guidance.\n3. Specify component anatomy, states, variants, and interaction behavior.\n4. Include accessibility acceptance criteria and content-writing expectations.\n5. Add anti-patterns and migration notes for existing inconsistent UI.\n6. End with a QA checklist that can be executed in code review.\n\n## Required Output Structure\n\nWhen generating design-system guidance, use this structure:\n\n- Context and goals\n- Design tokens and foundations\n- Component-level rules (anatomy, variants, states, responsive behavior)\n- Accessibility requirements and testable acceptance criteria\n- Content and tone standards with examples\n- Anti-patterns and prohibited implementations\n- QA checklist\n\n## Component Rule Expectations\n\n- Define required states: default, hover, focus-visible, active, disabled, loading, error (as relevant).\n- Describe interaction behavior for keyboard, pointer, and touch.\n- State spacing, typography, and color-token usage explicitly.\n- Include responsive behavior and edge cases (long labels, empty states, overflow).\n\n## Quality Gates\n\n- No rule should depend on ambiguous adjectives alone; anchor each rule to a token, threshold, or example.\n- Every accessibility statement must be testable in implementation.\n- Prefer system consistency over one-off local optimizations.\n- Flag conflicts between aesthetics and accessibility, then prioritize accessibility.\n\n## Example Constraint Language\n\n- Use \"must\" for non-negotiable rules and \"should\" for recommendations.\n- Pair every do-rule with at least one concrete don't-example.\n- If introducing a new pattern, include migration guidance for existing components.\n\n\u003C!-- TYPEUI_SH_MANAGED_END -->\n",{"name":5,"license":15,"metadata":24,"description":7},{"author":25},"typeui.sh","main","e2c0b5e0b02b3d8ee33c348da5392e885c98757b","skills\u002F04_design_style_library\u002Fskeumorphism",0,"https:\u002F\u002Fgithub.com\u002Ffeliksness\u002FQuartzite-Prompt-Library","https:\u002F\u002Fgithub.com\u002Ffeliksness","Economics • AI & Computer Vision • FinTech • Software Development • Entrepreneurship | Building ideas into real projects.","2026-10-04 03:14:33",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add feliksness\u002FQuartzite-Prompt-Library --skill skeumorphism",{"tool":40,"command":41},"bunx","bunx skills add feliksness\u002FQuartzite-Prompt-Library --skill skeumorphism",{"tool":43,"command":44},"pnpm","pnpm dlx skills add feliksness\u002FQuartzite-Prompt-Library --skill skeumorphism","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ffeliksness\u002FQuartzite-Prompt-Library\u002Fblob\u002Fmain\u002Fskills\u002F04_design_style_library\u002Fskeumorphism\u002FSKILL.md",true,[48],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"DESIGN.md","REFERENCE","参考文档",1554,"https:\u002F\u002Fgithub.com\u002Ffeliksness\u002FQuartzite-Prompt-Library\u002Fblob\u002Fmain\u002Fskills\u002F04_design_style_library\u002Fskeumorphism\u002FDESIGN.md",[55,63,72,80,87,94],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":59,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7E55RYQF73KMB8KPSCAKEG1","claude-design","Produce thoughtful, high-fidelity design artifacts in HTML — landing pages, slide decks, interactive prototypes, animated videos, posters, wireframes, and visual explorations. Use whenever the user asks to design, mock up, prototype, visualize, storyboard, or explore UI options — including phrases like \"make a deck\", \"design a landing page\", \"prototype this flow\", \"animate this concept\", \"build a pitch deck\", \"create a poster\", \"visualize this idea\", or \"design something for a brand\". Enforces fact verification (WebSearch before assuming a product exists or its version), the Core Asset Protocol for branded work (logo, product shots, and UI screenshots are first-class, not just colors and fonts), a Design Direction Advisor fallback that offers 3 differentiated directions from 10 design philosophies when the brief is too vague, commits to a visual system up front, presents multiple variations, and avoids AI-design tropes (aggressive gradients, emoji bullets, generic templates).","https:\u002F\u002Fgithub.com\u002Ffeliksness\u002FQuartzite-Prompt-Library\u002Fblob\u002Fmain\u002Fskills\u002F05_design_workflow_specialists\u002Fhtml-artifact-designer\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Ffeliksness\u002FQuartzite-Prompt-Library\u002Fblob\u002Fmain\u002Fskills\u002F05_design_workflow_specialists\u002Fhtml-artifact-designer\u002FSKILL.md",[],[],{"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":67,"licenseFileUrl":68,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7E55GTYM1CGKM6Z78DNW9RX","color-expert","Use when working with color naming, color theory, color spaces, color definitions, or any task involving color knowledge - palettes, ramps, gradients, conversions, accessibility, perceptual matching, pigment mixing, print-vs-screen color, CSS color syntax, or historical color terminology. Use this skill whenever the user is choosing, comparing, generating, naming, converting, or explaining colors, even if they do not explicitly ask for \"color theory.\"","CC-BY-4.0","https:\u002F\u002Fgithub.com\u002Ffeliksness\u002FQuartzite-Prompt-Library\u002Fblob\u002Fmain\u002Fskills\u002F05_design_workflow_specialists\u002Fcolor-science-expert\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Ffeliksness\u002FQuartzite-Prompt-Library\u002Fblob\u002Fmain\u002Fskills\u002F05_design_workflow_specialists\u002Fcolor-science-expert\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":15,"licenseFileUrl":76,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M7E553X7CWSFW56GE6ASZ4JF","ai-graphic-design","Guide for creating logos, brand identities, and visual assets using AI tools — covers tool selection, prompt engineering, vectorization pipelines, mockups, automation, and IP safety.","https:\u002F\u002Fgithub.com\u002Ffeliksness\u002FQuartzite-Prompt-Library\u002Fblob\u002Fmain\u002Fskills\u002F05_design_workflow_specialists\u002Fai-graphic-design-branding\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Ffeliksness\u002FQuartzite-Prompt-Library\u002Fblob\u002Fmain\u002Fskills\u002F05_design_workflow_specialists\u002Fai-graphic-design-branding\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7E54VW1C902WRM4XJD356J7","vintage","1950s-1990s nostalgia with skeuomorphic touches, grainy textures, retro color palettes, and pixel-style typography.","https:\u002F\u002Fgithub.com\u002Ffeliksness\u002FQuartzite-Prompt-Library\u002Fblob\u002Fmain\u002Fskills\u002F04_design_style_library\u002Fvintage\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M7E54GC2VDE21R2J8RA1X92X","retro","Throwback design with vintage-inspired typography, high-contrast retro palettes, and nostalgic visual elements.","https:\u002F\u002Fgithub.com\u002Ffeliksness\u002FQuartzite-Prompt-Library\u002Fblob\u002Fmain\u002Fskills\u002F04_design_style_library\u002Fretro\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":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":19},"01M7E54E1XTS2D4PBAWMJ2P6QE","paper","Paper-textured, print-inspired design with minimal colors, clean serif\u002Fsans typography, and tactile surface qualities.","https:\u002F\u002Fgithub.com\u002Ffeliksness\u002FQuartzite-Prompt-Library\u002Fblob\u002Fmain\u002Fskills\u002F04_design_style_library\u002Fpaper\u002FSKILL.md",[],[]]