[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77W39KVZQYPVRMN2Q0S16EP":3,"skill-same:01M77W39KVZQYPVRMN2Q0S16EP":45},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M77W39KVZQYPVRMN2Q0S16EP","frontend-design",null,"Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. Use for any The Sovereign Imperia Citadel Z UI work.","Hvuj\u002FThe-Soverign-Imperia-citadel","Hvuj","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F56831016?v=4","01M77W2P3G85MYKVGV2R24KRV1","Eli Sigal","01M77W2P473NNYMVQCBJTDVRKS",0,"GPL-3.0","https:\u002F\u002Fgithub.com\u002FHvuj\u002FThe-Soverign-Imperia-citadel\u002Fblob\u002Fmain\u002Fsrc\u002Fcitadel\u002Fassets\u002Fclaude_template\u002Fskills\u002Ffrontend-design\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\r\nname: frontend-design\r\ndescription: Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. Use for any The Sovereign Imperia Citadel Z UI work.\r\n---\r\n\r\n# Frontend Design\r\n\r\nApproach this as the design lead at a small studio known for giving every client a visual identity\r\nthat could not be mistaken for anyone else's. Make deliberate, opinionated choices about palette,\r\ntypography, and layout specific to this brief, and take one real aesthetic risk you can justify.\r\n\r\n## Ground it in the subject\r\n\r\nIf the brief does not pin down what the product is, pin it yourself before designing: name one\r\nconcrete subject, its audience, and the page's single job, and state your choice. Use anything in\r\nmemory about the human's preferences or prior designs. The subject's own world — its materials,\r\ninstruments, artifacts, vernacular — is where distinctive choices come from. For The Sovereign Imperia Citadel Z the\r\nsubject is a self-healing, zero-token orchestration brain over a whole workspace of repos.\r\n\r\n## Design principles\r\n\r\n- The hero is a thesis. Open with the most characteristic thing in the subject's world (a headline,\r\n  image, animation, live demo, interactive moment). The \"big number + label + gradient accent\" is\r\n  the template answer — only use it if it's truly best.\r\n- Typography carries the personality. Pair display and body faces deliberately; set a clear type\r\n  scale with intentional weights, widths, spacing. Make the type treatment memorable, not neutral.\r\n- Structure is information. Numbering, eyebrows, dividers, labels should encode something true about\r\n  the content, not decorate. Numbered markers (01\u002F02\u002F03) only if the content is a real sequence.\r\n- Leverage motion deliberately: a page-load sequence, scroll-triggered reveal, hover\r\n  micro-interactions, ambient atmosphere. One orchestrated moment beats scattered effects; sometimes\r\n  less is more (extra animation reads as AI-generated).\r\n- Match complexity to the vision: maximalist needs elaborate execution; minimal needs precision in\r\n  spacing, type, detail. Elegance is executing the chosen vision well.\r\n- Consider written content carefully — copy can make a design feel as templated as the layout.\r\n\r\n## Calibration — avoid the AI defaults\r\n\r\nAI-generated design clusters around three looks: (1) warm cream (#F4F1EA) + high-contrast serif +\r\nterracotta accent; (2) near-black + a single acid-green\u002Fvermilion accent; (3) broadsheet with\r\nhairline rules, zero border-radius, dense columns. All are legitimate for some briefs but are\r\ndefaults, not choices. Where the brief pins a direction, follow it exactly. Where it leaves an axis\r\nfree, don't spend that freedom on a default.\r\n\r\n## Process: brainstorm → plan → critique → build → critique again\r\n\r\nFirst pass — a compact token system: Color (4–6 named hex), Type (display + body + utility faces),\r\nLayout (one-sentence concept + ASCII wireframe), Signature (the one memorable element embodying the\r\nbrief). Then review the plan against the brief: if any part reads like the generic default you'd\r\nproduce for any similar page, revise it and say what changed and why. Only then write code, deriving\r\nevery color\u002Ftype decision from the revised plan.\r\n\r\nWhen writing CSS, watch selector specificity (type-based `.section` vs element-based `.cta` can\r\ncancel margins\u002Fpaddings between sections). Do planning\u002Fiteration in thinking; show the user only\r\nhigher-confidence work.\r\n\r\n## Restraint and self-critique\r\n\r\nSpend boldness in one place — let the signature element be the one memorable thing and keep\r\neverything around it quiet. Cut decoration that doesn't serve the brief. Build to a quality floor\r\nwithout announcing it: responsive to mobile, visible keyboard focus, reduced-motion respected.\r\nCritique your own work as you build (screenshots if available). Before shipping, remove one accessory.\r\n\r\n## Writing in design\r\n\r\nWords exist to make the design easier to understand and use — design material, not decoration. Write\r\nfrom the end user's side of the screen; name things by what people control, not how the system is\r\nbuilt. Active voice; an action keeps its name through the whole flow (a \"Publish\" button → a\r\n\"Published\" toast). Treat errors and empty states as direction, not mood: explain what happened and\r\nhow to fix it, in the interface's voice. Keep the register conversational, sentence case, no filler.\r\n","# Frontend Design\r\n\r\nApproach this as the design lead at a small studio known for giving every client a visual identity\r\nthat could not be mistaken for anyone else's. Make deliberate, opinionated choices about palette,\r\ntypography, and layout specific to this brief, and take one real aesthetic risk you can justify.\r\n\r\n## Ground it in the subject\r\n\r\nIf the brief does not pin down what the product is, pin it yourself before designing: name one\r\nconcrete subject, its audience, and the page's single job, and state your choice. Use anything in\r\nmemory about the human's preferences or prior designs. The subject's own world — its materials,\r\ninstruments, artifacts, vernacular — is where distinctive choices come from. For The Sovereign Imperia Citadel Z the\r\nsubject is a self-healing, zero-token orchestration brain over a whole workspace of repos.\r\n\r\n## Design principles\r\n\r\n- The hero is a thesis. Open with the most characteristic thing in the subject's world (a headline,\r\n  image, animation, live demo, interactive moment). The \"big number + label + gradient accent\" is\r\n  the template answer — only use it if it's truly best.\r\n- Typography carries the personality. Pair display and body faces deliberately; set a clear type\r\n  scale with intentional weights, widths, spacing. Make the type treatment memorable, not neutral.\r\n- Structure is information. Numbering, eyebrows, dividers, labels should encode something true about\r\n  the content, not decorate. Numbered markers (01\u002F02\u002F03) only if the content is a real sequence.\r\n- Leverage motion deliberately: a page-load sequence, scroll-triggered reveal, hover\r\n  micro-interactions, ambient atmosphere. One orchestrated moment beats scattered effects; sometimes\r\n  less is more (extra animation reads as AI-generated).\r\n- Match complexity to the vision: maximalist needs elaborate execution; minimal needs precision in\r\n  spacing, type, detail. Elegance is executing the chosen vision well.\r\n- Consider written content carefully — copy can make a design feel as templated as the layout.\r\n\r\n## Calibration — avoid the AI defaults\r\n\r\nAI-generated design clusters around three looks: (1) warm cream (#F4F1EA) + high-contrast serif +\r\nterracotta accent; (2) near-black + a single acid-green\u002Fvermilion accent; (3) broadsheet with\r\nhairline rules, zero border-radius, dense columns. All are legitimate for some briefs but are\r\ndefaults, not choices. Where the brief pins a direction, follow it exactly. Where it leaves an axis\r\nfree, don't spend that freedom on a default.\r\n\r\n## Process: brainstorm → plan → critique → build → critique again\r\n\r\nFirst pass — a compact token system: Color (4–6 named hex), Type (display + body + utility faces),\r\nLayout (one-sentence concept + ASCII wireframe), Signature (the one memorable element embodying the\r\nbrief). Then review the plan against the brief: if any part reads like the generic default you'd\r\nproduce for any similar page, revise it and say what changed and why. Only then write code, deriving\r\nevery color\u002Ftype decision from the revised plan.\r\n\r\nWhen writing CSS, watch selector specificity (type-based `.section` vs element-based `.cta` can\r\ncancel margins\u002Fpaddings between sections). Do planning\u002Fiteration in thinking; show the user only\r\nhigher-confidence work.\r\n\r\n## Restraint and self-critique\r\n\r\nSpend boldness in one place — let the signature element be the one memorable thing and keep\r\neverything around it quiet. Cut decoration that doesn't serve the brief. Build to a quality floor\r\nwithout announcing it: responsive to mobile, visible keyboard focus, reduced-motion respected.\r\nCritique your own work as you build (screenshots if available). Before shipping, remove one accessory.\r\n\r\n## Writing in design\r\n\r\nWords exist to make the design easier to understand and use — design material, not decoration. Write\r\nfrom the end user's side of the screen; name things by what people control, not how the system is\r\nbuilt. Active voice; an action keeps its name through the whole flow (a \"Publish\" button → a\r\n\"Published\" toast). Treat errors and empty states as direction, not mood: explain what happened and\r\nhow to fix it, in the interface's voice. Keep the register conversational, sentence case, no filler.\r\n",{"name":5,"description":7},"main","17dc63a82b93c8e1b7cce2332da2b383a7201d6d","src\u002Fcitadel\u002Fassets\u002Fclaude_template\u002Fskills\u002Ffrontend-design","https:\u002F\u002Fgithub.com\u002FHvuj\u002FThe-Soverign-Imperia-citadel","https:\u002F\u002Fgithub.com\u002FHvuj","Data engineer \\ Backend Engineer","2026-07-22 22:23:12",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add Hvuj\u002FThe-Soverign-Imperia-citadel --skill frontend-design",{"tool":37,"command":38},"bunx","bunx skills add Hvuj\u002FThe-Soverign-Imperia-citadel --skill frontend-design",{"tool":40,"command":41},"pnpm","pnpm dlx skills add Hvuj\u002FThe-Soverign-Imperia-citadel --skill frontend-design","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHvuj\u002FThe-Soverign-Imperia-citadel\u002Fblob\u002Fmain\u002Fsrc\u002Fcitadel\u002Fassets\u002Fclaude_template\u002Fskills\u002Ffrontend-design\u002FSKILL.md",true,[],[46,53,59,65,71,77],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":19},"01M77W4TYKKDXDSPGW9H5BRTBH","workspace-visualize","Generate an interactive collapsible HTML tree view of the codebase with file sizes, type breakdown bar chart, and color-coded file types. Opens in your default browser. Use when exploring a new repo, understanding project structure, or identifying large files before refactoring.","https:\u002F\u002Fgithub.com\u002FHvuj\u002FThe-Soverign-Imperia-citadel\u002Fblob\u002Fmain\u002Fsrc\u002Fcitadel\u002Fassets\u002Fclaude_template\u002Fskills\u002Fworkspace-visualize\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M77W4QW746EVDEBNFG8RMMVX","testing-strategy-review","https:\u002F\u002Fgithub.com\u002FHvuj\u002FThe-Soverign-Imperia-citadel\u002Fblob\u002Fmain\u002Fsrc\u002Fcitadel\u002Fassets\u002Fclaude_template\u002Fskills\u002Ftesting-strategy-review\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M77W4NMMT3PCBHHFJ09CMY5H","technical-domain-routing","https:\u002F\u002Fgithub.com\u002FHvuj\u002FThe-Soverign-Imperia-citadel\u002Fblob\u002Fmain\u002Fsrc\u002Fcitadel\u002Fassets\u002Fclaude_template\u002Fskills\u002Ftechnical-domain-routing\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M77W4M39JPTXX5DSR5XWCYNG","target-codebase-overview","https:\u002F\u002Fgithub.com\u002FHvuj\u002FThe-Soverign-Imperia-citadel\u002Fblob\u002Fmain\u002Fsrc\u002Fcitadel\u002Fassets\u002Fclaude_template\u002Fskills\u002Ftarget-codebase-overview\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M77W4HNQR8XRW8NF7A691XEE","skill-forge","https:\u002F\u002Fgithub.com\u002FHvuj\u002FThe-Soverign-Imperia-citadel\u002Fblob\u002Fmain\u002Fsrc\u002Fcitadel\u002Fassets\u002Fclaude_template\u002Fskills\u002Fskill-forge\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M77W4DWRC7KB094CCTBSD3SE","settings-reference","Claude Code settings.json reference for permissions, sandbox, plugins, skill visibility, and configuration options. Claude loads automatically when asked about settings, permissions, configuration, or hooks.","https:\u002F\u002Fgithub.com\u002FHvuj\u002FThe-Soverign-Imperia-citadel\u002Fblob\u002Fmain\u002Fsrc\u002Fcitadel\u002Fassets\u002Fclaude_template\u002Fskills\u002Fsettings-reference\u002FSKILL.md",[],[]]