[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M730Z862F31M2PVF9F058W68":3,"skill-same:01M730Z862F31M2PVF9F058W68":48},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M730Z862F31M2PVF9F058W68","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.","SriramGandhiS\u002FSkills","SriramGandhiS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F211849986?v=4","01M72WQCW12BYX71C6WN584TTA","Sriram S","01M72WQCWTJ2RD0ET1X31AF1RC",1,"MIT","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fskills\u002Ffrontend-design-direction\u002FSKILL.md",[],[],"2026-11-11 15:11:14",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.\norigin: 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,"origin":24,"description":7},"community","master","d6ca01da0f24a3b0e26e4a8b7b66cbd25d429f5d","skills\u002Ffrontend-design-direction",0,"https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills","https:\u002F\u002Fgithub.com\u002FSriramGandhiS","https:\u002F\u002Fsriram.website\u002F","Curious guy who keeps tinkering until something works","2026-05-20 16:21:34",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add SriramGandhiS\u002FSkills --skill frontend-design-direction",{"tool":40,"command":41},"bunx","bunx skills add SriramGandhiS\u002FSkills --skill frontend-design-direction",{"tool":43,"command":44},"pnpm","pnpm dlx skills add SriramGandhiS\u002FSkills --skill frontend-design-direction","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fskills\u002Ffrontend-design-direction\u002FSKILL.md",true,[],[49,56,61,67,74,81],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M732609EPJWV13PVTX3GT4TM","webgpu-threejs-tsl","Comprehensive guide for developing WebGPU-enabled Three.js applications using TSL (Three.js Shading Language). Covers WebGPU renderer setup, TSL syntax and node materials, compute shaders, post-processing effects, and WGSL integration. Use this skill when working with Three.js WebGPU, TSL shaders, node materials, or GPU compute in Three.js.","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fwebgpu-threejs-tsl\u002Fskills\u002Fwebgpu-threejs-tsl\u002FSKILL.md",[],[],{"skillNo":57,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M7325XM47AGWB6K6C4VXKE6B","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fwebgpu-threejs-tsl\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"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":64,"categories":65,"keywords":66,"publishedAt":19},"01M7325WP6DES69JKC840VMFEP","verification-loop","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fweb-assets\u002Fdocs\u002Fzh-TW\u002Fskills\u002Fverification-loop\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7325TFQF1DZTQ6J3WGQQ1VR","tdd-workflow","Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fweb-assets\u002Fdocs\u002Fzh-TW\u002Fskills\u002Ftdd-workflow\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7325RGV9AY9PK92D2V8KKPW","strategic-compact","Suggests manual context compaction at logical intervals to preserve context through task phases rather than arbitrary auto-compaction.","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fweb-assets\u002Fdocs\u002Fzh-TW\u002Fskills\u002Fstrategic-compact\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7325MZC28SE86E7NMCNEFS4","security-review","Use this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment\u002Fsensitive features. Provides comprehensive security checklist and patterns.","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fweb-assets\u002Fdocs\u002Fzh-TW\u002Fskills\u002Fsecurity-review\u002FSKILL.md",[],[]]