[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7B2E03SZ0762SN9CMPXW1YC":3,"skill-same:01M7B2E03SZ0762SN9CMPXW1YC":50},{"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":31,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M7B2E03SZ0762SN9CMPXW1YC","frontend-design-direction",null,"Set an ECC-specific frontend design direction for production UI work. Use when building or improving websites, dashboards, applications, components, landing pages, visual tools, or any web UI that needs stronger product-specific design judgment.","lytong760-cell\u002Fcompiler_ko","lytong760-cell","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F289977458?v=4","01M7B1YD239K88PFQRD4PVC9DW","Nguyên Games","01M7B1YD2RM70TZ71QNQ0XTN4R",2,"MIT","https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Ffrontend-design-direction\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: frontend-design-direction\ndescription: Set an ECC-specific frontend design direction for production UI work. Use when building or improving websites, dashboards, applications, components, landing pages, visual tools, or any web UI that needs stronger product-specific design judgment.\nmetadata:\n  origin: community\n---\n\n# Frontend Design Direction\n\nUse this skill when the work is not just making UI function, but making it feel\npurposeful, polished, and appropriate to the product domain.\n\nSource: salvaged from stale community PR #1659 by `linus707`.\n\nNote: ECC intentionally does not rebundle the canonical Anthropic\n`frontend-design` skill. Install that from `anthropics\u002Fskills` when you want the\nofficial upstream skill. This skill is the ECC-specific design-direction salvage\nof the useful local guidance from #1659.\n\n## When to Use\n\n- The user asks to build a web page, app, dashboard, artifact, component, or UI.\n- The user asks to make an interface more polished, distinctive, beautiful, or\n  less generic.\n- The implementation needs visual hierarchy, typography, color, motion, layout,\n  and interaction choices.\n- The current UI works but reads as flat, generic, templated, or mismatched to\n  the audience.\n\n## Design Direction\n\nBefore coding, choose a specific direction:\n\n1. Purpose: what job does the interface do?\n2. Audience: who repeats this workflow, and what do they need to scan first?\n3. Tone: utilitarian, editorial, playful, industrial, refined, technical,\n   maximal, minimal, dense, calm, or another explicit direction.\n4. Memorable detail: one design idea that makes the result feel intentional.\n5. Constraints: framework, accessibility, performance, responsiveness, and\n   existing design system.\n\nMatch the direction to the domain. A SaaS operations tool should usually be\ndense, quiet, and scannable. A portfolio, launch page, game, or editorial piece\ncan be more expressive. Do not force a landing-page composition onto a tool that\nneeds repeated daily use.\n\n## Implementation Guidance\n\n- Build the actual usable experience as the first screen unless the user\n  explicitly asks for marketing copy.\n- Use existing project components, tokens, icon libraries, and routing patterns\n  before introducing a new visual system.\n- Use real or generated visual assets when the interface depends on images,\n  products, places, people, gameplay, charts, or inspectable media.\n- Prefer contextual typography and spacing over generic oversized hero text.\n- Keep palettes multi-dimensional: avoid a UI dominated by one hue family.\n- Use CSS variables or existing design tokens so the direction remains\n  coherent across states.\n- Design responsive constraints explicitly: grids, aspect ratios, min\u002Fmax\n  sizes, stable toolbars, and fixed-format controls should not shift when labels\n  or hover states appear.\n- Use motion sparingly but deliberately. Prefer high-signal transitions that\n  clarify state over decorative animation.\n- Verify text fit on mobile and desktop. Long labels must wrap or resize\n  cleanly rather than overflowing.\n\n## Anti-Patterns\n\n- Do not default to common generated patterns: purple gradients, decorative\n  blobs, oversized cards, vague hero copy, or stock-like atmospheric media.\n- Do not add UI cards inside other cards.\n- Do not use a single decorative style everywhere when the domain calls for\n  restraint.\n- Do not hide the primary product, tool, object, or workflow behind generic\n  marketing sections.\n- Do not add a new dependency for a design flourish unless it clearly pays for\n  itself.\n- Do not describe the UI's features inside the UI when the controls can speak\n  for themselves.\n\n## Review Checklist\n\n- The first viewport immediately communicates the product, workflow, or object.\n- The visual hierarchy supports scanning and repeated use.\n- Typography fits the container and does not overlap adjacent content.\n- Color choices have contrast and do not collapse into a one-note palette.\n- Icons are used for familiar tool actions where available.\n- Responsive layout has stable dimensions for boards, grids, toolbars,\n  controls, tiles, and counters.\n- Assets render and carry the subject matter instead of acting as filler.\n- Motion improves orientation and does not mask sluggishness.\n- The result matches the repo's existing frontend conventions unless there is a\n  clear reason to depart.\n","# Frontend Design Direction\n\nUse this skill when the work is not just making UI function, but making it feel\npurposeful, polished, and appropriate to the product domain.\n\nSource: salvaged from stale community PR #1659 by `linus707`.\n\nNote: ECC intentionally does not rebundle the canonical Anthropic\n`frontend-design` skill. Install that from `anthropics\u002Fskills` when you want the\nofficial upstream skill. This skill is the ECC-specific design-direction salvage\nof the useful local guidance from #1659.\n\n## When to Use\n\n- The user asks to build a web page, app, dashboard, artifact, component, or UI.\n- The user asks to make an interface more polished, distinctive, beautiful, or\n  less generic.\n- The implementation needs visual hierarchy, typography, color, motion, layout,\n  and interaction choices.\n- The current UI works but reads as flat, generic, templated, or mismatched to\n  the audience.\n\n## Design Direction\n\nBefore coding, choose a specific direction:\n\n1. Purpose: what job does the interface do?\n2. Audience: who repeats this workflow, and what do they need to scan first?\n3. Tone: utilitarian, editorial, playful, industrial, refined, technical,\n   maximal, minimal, dense, calm, or another explicit direction.\n4. Memorable detail: one design idea that makes the result feel intentional.\n5. Constraints: framework, accessibility, performance, responsiveness, and\n   existing design system.\n\nMatch the direction to the domain. A SaaS operations tool should usually be\ndense, quiet, and scannable. A portfolio, launch page, game, or editorial piece\ncan be more expressive. Do not force a landing-page composition onto a tool that\nneeds repeated daily use.\n\n## Implementation Guidance\n\n- Build the actual usable experience as the first screen unless the user\n  explicitly asks for marketing copy.\n- Use existing project components, tokens, icon libraries, and routing patterns\n  before introducing a new visual system.\n- Use real or generated visual assets when the interface depends on images,\n  products, places, people, gameplay, charts, or inspectable media.\n- Prefer contextual typography and spacing over generic oversized hero text.\n- Keep palettes multi-dimensional: avoid a UI dominated by one hue family.\n- Use CSS variables or existing design tokens so the direction remains\n  coherent across states.\n- Design responsive constraints explicitly: grids, aspect ratios, min\u002Fmax\n  sizes, stable toolbars, and fixed-format controls should not shift when labels\n  or hover states appear.\n- Use motion sparingly but deliberately. Prefer high-signal transitions that\n  clarify state over decorative animation.\n- Verify text fit on mobile and desktop. Long labels must wrap or resize\n  cleanly rather than overflowing.\n\n## Anti-Patterns\n\n- Do not default to common generated patterns: purple gradients, decorative\n  blobs, oversized cards, vague hero copy, or stock-like atmospheric media.\n- Do not add UI cards inside other cards.\n- Do not use a single decorative style everywhere when the domain calls for\n  restraint.\n- Do not hide the primary product, tool, object, or workflow behind generic\n  marketing sections.\n- Do not add a new dependency for a design flourish unless it clearly pays for\n  itself.\n- Do not describe the UI's features inside the UI when the controls can speak\n  for themselves.\n\n## Review Checklist\n\n- The first viewport immediately communicates the product, workflow, or object.\n- The visual hierarchy supports scanning and repeated use.\n- Typography fits the container and does not overlap adjacent content.\n- Color choices have contrast and do not collapse into a one-note palette.\n- Icons are used for familiar tool actions where available.\n- Responsive layout has stable dimensions for boards, grids, toolbars,\n  controls, tiles, and counters.\n- Assets render and carry the subject matter instead of acting as filler.\n- Motion improves orientation and does not mask sluggishness.\n- The result matches the repo's existing frontend conventions unless there is a\n  clear reason to depart.\n",{"name":5,"metadata":24,"description":7},{"origin":25},"community","main","c32dc0b68600587f78aff3310f3bbd4212173ab3",".kilo\u002Fskills\u002Ffrontend-design-direction",1,"https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko","https:\u002F\u002Fko-lang.ai.studio","https:\u002F\u002Fgithub.com\u002Flytong760-cell","hanaminikata.com","hello ","2026-11-05 18:26:32",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add lytong760-cell\u002Fcompiler_ko --skill frontend-design-direction",{"tool":42,"command":43},"bunx","bunx skills add lytong760-cell\u002Fcompiler_ko --skill frontend-design-direction",{"tool":45,"command":46},"pnpm","pnpm dlx skills add lytong760-cell\u002Fcompiler_ko --skill frontend-design-direction","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Ffrontend-design-direction\u002FSKILL.md",true,[],[51,58,65,72,79,86],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":19},"01M7B36K22Z7155PTGEGTSDNJ4","x-api","X\u002FTwitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.","https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fx-api\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"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},"01M7B36HCAE9ESGBVS6J0FR52F","writing-for-agents","Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.","https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fwriting-for-agents\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":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7B36DYH4ZFJ3GZHPAEMVQAY","workspace-surface-audit","Audit the active repo, MCP servers, plugins, connectors, env surfaces, and harness setup, then recommend the highest-value ECC-native skills, hooks, agents, and operator workflows. Use when the user wants help setting up Claude Code or understanding what capabilities are actually available in their environment.","https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fworkspace-surface-audit\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":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7B36A1QXMEZT8VZMFVQNR5E","wizard","Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.","https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fwizard\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7B364EK3N88VQQJ6HFATJQE","windows-desktop-e2e","E2E testing for Windows native desktop apps (WPF, WinForms, Win32\u002FMFC, Qt) using pywinauto and Windows UI Automation. Use when writing E2E tests for a Windows native desktop app with pywinauto or UI Automation.","https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fwindows-desktop-e2e\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":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7B360YF7GGNAF21KT4QB5PG","wayfinder","Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.","https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fwayfinder\u002FSKILL.md",[],[]]