[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CJ8NRP34PD9PCWS8S0V0X5":3,"skill-same:01M7CJ8NRP34PD9PCWS8S0V0X5":77},{"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":51,"commitSha":52,"skillDirectory":53,"forksCount":14,"repositoryHtmlUrl":54,"repositoryHomepageUrl":6,"ownerHtmlUrl":55,"ownerBlogUrl":56,"ownerDescription":57,"updatedAt":58,"install":59,"resources":71},"01M7CJ8NRP34PD9PCWS8S0V0X5","frontend-design",null,"Create distinctive, production-grade frontend interfaces with strong visual direction, polished typography, considered layout, and working HTML\u002FCSS\u002FJS or framework code. Use for websites, landing pages, dashboards, React components, application screens, and UI beautification.","Revenant-Systems-LLC\u002FRevenant-Agent-Armory","Revenant-Systems-LLC","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F229055145?v=4","01M7C9Y8FXGE71CA7DMC9MGBWY","Revenant Systems LLC","01M7C9Y8GJ89YGMYR5ZHV06761",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FRevenant-Systems-LLC\u002FRevenant-Agent-Armory\u002Fblob\u002Fmaster\u002Fskillz\u002Fopen-design\u002Ffrontend-design\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FRevenant-Systems-LLC\u002FRevenant-Agent-Armory\u002Fblob\u002Fmaster\u002Fskillz\u002Fopen-design\u002Ffrontend-design\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: frontend-design\ndescription: |\n  Create distinctive, production-grade frontend interfaces with strong visual direction, polished typography, considered layout, and working HTML\u002FCSS\u002FJS or framework code. Use for websites, landing pages, dashboards, React components, application screens, and UI beautification.\ntriggers:\n  - \"frontend design\"\n  - \"ui design\"\n  - \"ux design\"\n  - \"web design\"\n  - \"production ui\"\n  - \"landing page\"\n  - \"dashboard design\"\n  - \"react component design\"\nlicense: Complete terms in LICENSE.txt\nod:\n  mode: prototype\n  category: web-artifacts\n  craft:\n    requires: [typography, color, anti-ai-slop]\n  design_system:\n    requires: true\n    sections: [color, typography, layout, components]\n  example_prompt: \"Design and build a production-quality SaaS analytics dashboard for a finance team, with real interaction states, refined typography, and a distinctive visual direction.\"\n  upstream: \"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fskills\u002Ftree\u002Fmain\u002Fskills\u002Ffrontend-design\"\n---\n\n# frontend-design\n\n> Adapted from Anthropic's official `frontend-design` skill for Open Design.\n\nUse this skill when the user asks to build or improve a frontend interface: a website, landing page, dashboard, application screen, HTML\u002FCSS artifact, React\u002FVue\u002FSvelte component, or a visual redesign of an existing UI.\n\nThe goal is not just \"make it nicer.\" The goal is to ship working frontend code with a clear design point of view, strong craft, and enough product detail that the result feels designed for the user's actual context.\n\n## Workflow\n\n1. Understand the brief before choosing the look.\n   - Identify the audience, primary job, domain, and emotional tone.\n   - Note any technical constraints: framework, existing styles, accessibility, performance, export target, or responsive requirements.\n   - If the repo already has design tokens, components, screenshots, or a `DESIGN.md`, use those as the source of truth.\n\n2. Commit to one specific aesthetic direction.\n   - Pick a direction that fits the product: brutally minimal, editorial, luxury, playful, industrial, retro-futuristic, dense operational, calm enterprise, artful consumer, or another precise direction.\n   - Make the direction concrete through typography, spacing, color, hierarchy, motion, and component shape.\n   - Avoid generic AI defaults: purple-blue gradients, vague glass cards, interchangeable SaaS layouts, over-rounded cards, stock icon rows, and decorative blobs that do not serve the interface.\n\n3. Design the real interface, not a placeholder poster.\n   - Include the controls, empty\u002Floading\u002Ferror states, tables, filters, navigation, and responsive behavior a real user would expect.\n   - Use honest content. If data is unknown, label it as sample, pending, or unavailable instead of inventing claims.\n   - Keep workflows efficient for the target user. Dashboards and tools should be scannable and dense enough for repeated use; marketing pages can be more expressive.\n\n4. Build production-grade frontend code.\n   - Prefer the repository's existing framework, component conventions, icons, tokens, and styling approach.\n   - For standalone artifacts, create self-contained HTML\u002FCSS\u002FJS unless the user asked for a framework.\n   - Use semantic markup, keyboard-accessible controls, visible focus states, sensible contrast, and responsive layout constraints.\n   - Use CSS variables for repeated colors, spacing, shadows, and type scale.\n\n5. Refine visual craft.\n   - Typography: choose expressive but readable type pairings. Avoid using default system stacks as the main visual idea unless the direction is intentionally utilitarian.\n   - Color: create a balanced palette with role clarity. Use accent color sparingly and deliberately.\n   - Layout: use alignment, rhythm, density, and negative space intentionally. Do not let cards, panels, or labels drift.\n   - Motion: add purposeful transitions for state changes, reveals, and feedback. Prefer transforms and opacity for performance.\n   - Details: use texture, borders, shadows, dividers, media, and iconography only when they support the concept.\n\n6. Self-review before final delivery.\n   - The interface works at mobile and desktop widths.\n   - Text fits its containers and does not overlap adjacent UI.\n   - Interactive elements have hover\u002Ffocus\u002Factive\u002Fdisabled states.\n   - The design avoids obvious AI-generated visual tropes.\n   - The result has one memorable quality a user could describe after closing the page.\n\n## Open Design Integration\n\nWhen Open Design provides an active design system, treat it as the product's brand contract. Use the injected color, typography, layout, and component guidance first, then apply this skill's frontend craft rules where the design system is silent.\n\nWhen Open Design injects craft references such as `typography`, `color`, and `anti-ai-slop`, apply those checks before finishing. If the user's brand guidance conflicts with a generic craft rule, the user's brand guidance wins.\n\n## Source\n\n- Upstream: https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fskills\u002Ftree\u002Fmain\u002Fskills\u002Ffrontend-design\n- Category: `web-artifacts`\n\n## License\n\nThis skill is adapted from Anthropic's official skills repository. See `LICENSE.txt` in this folder for the upstream Apache-2.0 license terms.\n","# frontend-design\n\n> Adapted from Anthropic's official `frontend-design` skill for Open Design.\n\nUse this skill when the user asks to build or improve a frontend interface: a website, landing page, dashboard, application screen, HTML\u002FCSS artifact, React\u002FVue\u002FSvelte component, or a visual redesign of an existing UI.\n\nThe goal is not just \"make it nicer.\" The goal is to ship working frontend code with a clear design point of view, strong craft, and enough product detail that the result feels designed for the user's actual context.\n\n## Workflow\n\n1. Understand the brief before choosing the look.\n   - Identify the audience, primary job, domain, and emotional tone.\n   - Note any technical constraints: framework, existing styles, accessibility, performance, export target, or responsive requirements.\n   - If the repo already has design tokens, components, screenshots, or a `DESIGN.md`, use those as the source of truth.\n\n2. Commit to one specific aesthetic direction.\n   - Pick a direction that fits the product: brutally minimal, editorial, luxury, playful, industrial, retro-futuristic, dense operational, calm enterprise, artful consumer, or another precise direction.\n   - Make the direction concrete through typography, spacing, color, hierarchy, motion, and component shape.\n   - Avoid generic AI defaults: purple-blue gradients, vague glass cards, interchangeable SaaS layouts, over-rounded cards, stock icon rows, and decorative blobs that do not serve the interface.\n\n3. Design the real interface, not a placeholder poster.\n   - Include the controls, empty\u002Floading\u002Ferror states, tables, filters, navigation, and responsive behavior a real user would expect.\n   - Use honest content. If data is unknown, label it as sample, pending, or unavailable instead of inventing claims.\n   - Keep workflows efficient for the target user. Dashboards and tools should be scannable and dense enough for repeated use; marketing pages can be more expressive.\n\n4. Build production-grade frontend code.\n   - Prefer the repository's existing framework, component conventions, icons, tokens, and styling approach.\n   - For standalone artifacts, create self-contained HTML\u002FCSS\u002FJS unless the user asked for a framework.\n   - Use semantic markup, keyboard-accessible controls, visible focus states, sensible contrast, and responsive layout constraints.\n   - Use CSS variables for repeated colors, spacing, shadows, and type scale.\n\n5. Refine visual craft.\n   - Typography: choose expressive but readable type pairings. Avoid using default system stacks as the main visual idea unless the direction is intentionally utilitarian.\n   - Color: create a balanced palette with role clarity. Use accent color sparingly and deliberately.\n   - Layout: use alignment, rhythm, density, and negative space intentionally. Do not let cards, panels, or labels drift.\n   - Motion: add purposeful transitions for state changes, reveals, and feedback. Prefer transforms and opacity for performance.\n   - Details: use texture, borders, shadows, dividers, media, and iconography only when they support the concept.\n\n6. Self-review before final delivery.\n   - The interface works at mobile and desktop widths.\n   - Text fits its containers and does not overlap adjacent UI.\n   - Interactive elements have hover\u002Ffocus\u002Factive\u002Fdisabled states.\n   - The design avoids obvious AI-generated visual tropes.\n   - The result has one memorable quality a user could describe after closing the page.\n\n## Open Design Integration\n\nWhen Open Design provides an active design system, treat it as the product's brand contract. Use the injected color, typography, layout, and component guidance first, then apply this skill's frontend craft rules where the design system is silent.\n\nWhen Open Design injects craft references such as `typography`, `color`, and `anti-ai-slop`, apply those checks before finishing. If the user's brand guidance conflicts with a generic craft rule, the user's brand guidance wins.\n\n## Source\n\n- Upstream: https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fskills\u002Ftree\u002Fmain\u002Fskills\u002Ffrontend-design\n- Category: `web-artifacts`\n\n## License\n\nThis skill is adapted from Anthropic's official skills repository. See `LICENSE.txt` in this folder for the upstream Apache-2.0 license terms.\n",{"od":25,"name":5,"license":40,"triggers":41,"description":50},{"mode":26,"craft":27,"category":32,"upstream":33,"design_system":34,"example_prompt":39},"prototype",{"requires":28},[29,30,31],"typography","color","anti-ai-slop","web-artifacts","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fskills\u002Ftree\u002Fmain\u002Fskills\u002Ffrontend-design",{"requires":35,"sections":36},true,[30,29,37,38],"layout","components","Design and build a production-quality SaaS analytics dashboard for a finance team, with real interaction states, refined typography, and a distinctive visual direction.","Complete terms in LICENSE.txt",[42,43,44,45,46,47,48,49],"frontend design","ui design","ux design","web design","production ui","landing page","dashboard design","react component design","Create distinctive, production-grade frontend interfaces with strong visual direction, polished typography, considered layout, and working HTML\u002FCSS\u002FJS or framework code. Use for websites, landing pages, dashboards, React components, application screens, and UI beautification.\n","master","9ba12581aba079021c7bb49b145d7cf58fb0bd27","skillz\u002Fopen-design\u002Ffrontend-design","https:\u002F\u002Fgithub.com\u002FRevenant-Systems-LLC\u002FRevenant-Agent-Armory","https:\u002F\u002Fgithub.com\u002FRevenant-Systems-LLC","https:\u002F\u002Fwww.revenantsystems.net","The idea is not to live forever, but to create something that will.","2026-09-08 06:03:11",{"source":8,"skillName":5,"commands":60,"prompt":70,"zipAvailable":35},[61,64,67],{"tool":62,"command":63},"npx","npx skills add Revenant-Systems-LLC\u002FRevenant-Agent-Armory --skill frontend-design",{"tool":65,"command":66},"bunx","bunx skills add Revenant-Systems-LLC\u002FRevenant-Agent-Armory --skill frontend-design",{"tool":68,"command":69},"pnpm","pnpm dlx skills add Revenant-Systems-LLC\u002FRevenant-Agent-Armory --skill frontend-design","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FRevenant-Systems-LLC\u002FRevenant-Agent-Armory\u002Fblob\u002Fmaster\u002Fskillz\u002Fopen-design\u002Ffrontend-design\u002FSKILL.md",[72],{"path":73,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":76,"sourceHtmlUrl":16},"LICENSE.txt","LICENSE","许可证",10174,[78,87,95,103,111,119],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":82,"licenseFileUrl":83,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":20},"01M7CKSY45VGJA5RY04CVDV6PZ","last30days","Recent community and social trend research over the last 30 days. Use when\nthe brief asks what people are saying now, recent sentiment, community\nreactions, social proof, launch reaction, trend scan, or last-30-days context.","MIT","https:\u002F\u002Fgithub.com\u002FRevenant-Systems-LLC\u002FRevenant-Agent-Armory\u002Fblob\u002Fmaster\u002Ftemplatez\u002Fopen-design-design-templates\u002Flast30days\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FRevenant-Systems-LLC\u002FRevenant-Agent-Armory\u002Fblob\u002Fmaster\u002Ftemplatez\u002Fopen-design-design-templates\u002Flast30days\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":82,"licenseFileUrl":91,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":20},"01M7CKQVAKVW37MZACARH1TNQP","html-ppt","For consulting delivery work: turn diagnosis, frameworks, and project work into a client-adoptable action plan. Built around the core query \"consulting-final-deck\", with engagement manager judgment, buyer-ready proof, and this outcome: accept the recommendation and commit owners to the roadmap.","https:\u002F\u002Fgithub.com\u002FRevenant-Systems-LLC\u002FRevenant-Agent-Armory\u002Fblob\u002Fmaster\u002Ftemplatez\u002Fopen-design-design-templates\u002Fhtml-ppt\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FRevenant-Systems-LLC\u002FRevenant-Agent-Armory\u002Fblob\u002Fmaster\u002Ftemplatez\u002Fopen-design-design-templates\u002Fhtml-ppt\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":82,"licenseFileUrl":99,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":20},"01M7CKQHDFSAWX6MNXE31WTD5R","html-ppt-zhangzara-vellum","A humanities lecture: how Renaissance linear perspective reshaped early cartography — sources, argument, and evidence. Built as a decision-grade academic research deck for faculty, graduate seminar.","https:\u002F\u002Fgithub.com\u002FRevenant-Systems-LLC\u002FRevenant-Agent-Armory\u002Fblob\u002Fmaster\u002Ftemplatez\u002Fopen-design-design-templates\u002Fhtml-ppt-zhangzara-vellum\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FRevenant-Systems-LLC\u002FRevenant-Agent-Armory\u002Fblob\u002Fmaster\u002Ftemplatez\u002Fopen-design-design-templates\u002Fhtml-ppt-zhangzara-vellum\u002FSKILL.md",[],[],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":82,"licenseFileUrl":107,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":20},"01M7CKQ84S869JKY87HE4P1T27","html-ppt-zhangzara-studio","A photography studio's portfolio-and-rate deck — the signature work, the process, and the packages that win the brief. Built as a decision-grade design craft deck for prospective clients.","https:\u002F\u002Fgithub.com\u002FRevenant-Systems-LLC\u002FRevenant-Agent-Armory\u002Fblob\u002Fmaster\u002Ftemplatez\u002Fopen-design-design-templates\u002Fhtml-ppt-zhangzara-studio\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FRevenant-Systems-LLC\u002FRevenant-Agent-Armory\u002Fblob\u002Fmaster\u002Ftemplatez\u002Fopen-design-design-templates\u002Fhtml-ppt-zhangzara-studio\u002FSKILL.md",[],[],{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":82,"licenseFileUrl":115,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":20},"01M7CKPXVZ0XE28RV446DZZ2FH","html-ppt-zhangzara-stencil-tablet","A workplace-safety compliance review for a manufacturing regulator — findings, the evidence chain, and the corrective mandate. Built as a decision-grade policy briefing deck for regulator, plant leadership.","https:\u002F\u002Fgithub.com\u002FRevenant-Systems-LLC\u002FRevenant-Agent-Armory\u002Fblob\u002Fmaster\u002Ftemplatez\u002Fopen-design-design-templates\u002Fhtml-ppt-zhangzara-stencil-tablet\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FRevenant-Systems-LLC\u002FRevenant-Agent-Armory\u002Fblob\u002Fmaster\u002Ftemplatez\u002Fopen-design-design-templates\u002Fhtml-ppt-zhangzara-stencil-tablet\u002FSKILL.md",[],[],{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":82,"licenseFileUrl":123,"sourceHtmlUrl":124,"categories":125,"keywords":126,"publishedAt":20},"01M7CKPKRY1Y2ENVYNT3QR9EJJ","html-ppt-zhangzara-soft-editorial","A digital-transformation roadmap for a legacy insurer — the diagnosis, the sequenced bets, and the operating rhythm to land them. Built as a decision-grade consulting deck for client executives.","https:\u002F\u002Fgithub.com\u002FRevenant-Systems-LLC\u002FRevenant-Agent-Armory\u002Fblob\u002Fmaster\u002Ftemplatez\u002Fopen-design-design-templates\u002Fhtml-ppt-zhangzara-soft-editorial\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FRevenant-Systems-LLC\u002FRevenant-Agent-Armory\u002Fblob\u002Fmaster\u002Ftemplatez\u002Fopen-design-design-templates\u002Fhtml-ppt-zhangzara-soft-editorial\u002FSKILL.md",[],[]]