[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75CDJ4BD237FN2RFVN83WKJ":3,"skill-same:01M75CDJ4BD237FN2RFVN83WKJ":51},{"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":26,"commitSha":27,"skillDirectory":28,"forksCount":14,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M75CDJ4BD237FN2RFVN83WKJ","frontend-design",null,"Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML\u002FCSS layouts, or when styling\u002Fbeautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.","osman-jalloh-lab\u002Fmyos","osman-jalloh-lab","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F197696150?v=4","01M75CAASTD7R8BCGCDJCYFAZG","OSMAN JALLOH","01M75CAATE5G8833499GV57VW0",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fosman-jalloh-lab\u002Fmyos\u002Fblob\u002Fmain\u002Fskills\u002Ffrontend-design\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fosman-jalloh-lab\u002Fmyos\u002Fblob\u002Fmain\u002Fskills\u002Ffrontend-design\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: frontend-design\ndescription: Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML\u002FCSS layouts, or when styling\u002Fbeautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.\nlicense: Complete terms in LICENSE.txt\n---\n\nplatforms: []\nversion: 0.1.0\nThis skill guides creation of distinctive, production-grade frontend interfaces that avoid generic \"AI slop\" aesthetics. Implement real working code with exceptional attention to aesthetic details and creative choices.\n\nThe user provides frontend requirements: a component, page, application, or interface to build. They may include context about the purpose, audience, or technical constraints.\n\n## Design Thinking\n\nBefore coding, understand the context and commit to a BOLD aesthetic direction:\n- **Purpose**: What problem does this interface solve? Who uses it?\n- **Tone**: Pick an extreme: brutally minimal, maximalist chaos, retro-futuristic, organic\u002Fnatural, luxury\u002Frefined, playful\u002Ftoy-like, editorial\u002Fmagazine, brutalist\u002Fraw, art deco\u002Fgeometric, soft\u002Fpastel, industrial\u002Futilitarian, etc. There are so many flavors to choose from. Use these for inspiration but design one that is true to the aesthetic direction.\n- **Constraints**: Technical requirements (framework, performance, accessibility).\n- **Differentiation**: What makes this UNFORGETTABLE? What's the one thing someone will remember?\n\n**CRITICAL**: Choose a clear conceptual direction and execute it with precision. Bold maximalism and refined minimalism both work - the key is intentionality, not intensity.\n\nThen implement working code (HTML\u002FCSS\u002FJS, React, Vue, etc.) that is:\n- Production-grade and functional\n- Visually striking and memorable\n- Cohesive with a clear aesthetic point-of-view\n- Meticulously refined in every detail\n\n## Production-Grade Next.js App Router UI Notes\n\nWhen building self-contained pages under `src\u002Fapp\u002F\u003Croute>\u002Fpage.tsx`, especially for dashboards, keep these pragmatic lessons in mind:\n\n- **Self-contained styling**: Inline styles + a small inline `\u003Cstyle>` block for responsive overrides is often the cleanest path here because existing apps usually don't have an Agreed shared CSS layer per route. Prefer `minmax()` grids and `flexWrap: 'wrap'` for resilience.\n- **Mobile responsiveness**: For task-heavy UIs like Kanban boards, use a base 3-column grid and a max-width media query at 680px to collapse to 1 column. Show 2 columns on small screens only when cards are tiny; otherwise prefer the full single-column board.\n- **State and performance**: Use `useMemo` for derived overview counts when local state drives cards. Batch multiple `setState` calls in event handlers with separate functional updates to avoid stale closures.\n- **Local preview stability**: If `npm run dev` fails after adding a new app route with build-manifest ENOTEMPTY\u002FENOENT errors, prefer `npm run start -H 127.0.0.1 -p \u003Calternate port>` for stable local inspection instead of debugging the dev compaction state.\n- **Accessibility\u002FARIA**: Add `aria-label` to icon buttons with text glyphs, label inputs with `\u003Clabel>`, and use `role=\"dialog\"` plus `aria-modal` for modals.\n\n## Frontend Aesthetics Guidelines\n\nFocus on:\n- **Typography**: Choose fonts that are beautiful, unique, and interesting. Avoid generic fonts like Arial and Inter; opt instead for distinctive choices that elevate the frontend's aesthetics; unexpected, characterful font choices. Pair a distinctive display font with a refined body font.\n- **Color & Theme**: Commit to a cohesive aesthetic. Use CSS variables for consistency. Dominant colors with sharp accents outperform timid, evenly-distributed palettes.\n- **Motion**: Use animations for effects and micro-interactions. Prioritize CSS-only solutions for HTML. Use Motion library for React when available. Focus on high-impact moments: one well-orchestrated page load with staggered reveals (animation-delay) creates more delight than scattered micro-interactions. Use scroll-triggering and hover states that surprise.\n- **Spatial Composition**: Unexpected layouts. Asymmetry. Overlap. Diagonal flow. Grid-breaking elements. Generous negative space OR controlled density.\n- **Backgrounds & Visual Details**: Create atmosphere and depth rather than defaulting to solid colors. Add contextual effects and textures that match the overall aesthetic. Apply creative forms like gradient meshes, noise textures, geometric patterns, layered transparencies, dramatic shadows, decorative borders, custom cursors, and grain overlays.\n\nNEVER use generic AI-generated aesthetics like overused font families (Inter, Roboto, Arial, system fonts), cliched color schemes (particularly purple gradients on white backgrounds), predictable layouts and component patterns, and cookie-cutter design that lacks context-specific character.\n\nInterpret creatively and make unexpected choices that feel genuinely designed for the context. No design should be the same. Vary between light and dark themes, different fonts, different aesthetics. NEVER converge on common choices (Space Grotesk, for example) across generations.\n\n**IMPORTANT**: Match implementation complexity to the aesthetic vision. Maximalist designs need elaborate code with extensive animations and effects. Minimalist or refined designs need restraint, precision, and careful attention to spacing, typography, and subtle details. Elegance comes from executing the vision well.\n\nRemember: Claude is capable of extraordinary creative work. Don't hold back, show what can truly be created when thinking outside the box and committing fully to a distinctive vision.\n","platforms: []\nversion: 0.1.0\nThis skill guides creation of distinctive, production-grade frontend interfaces that avoid generic \"AI slop\" aesthetics. Implement real working code with exceptional attention to aesthetic details and creative choices.\n\nThe user provides frontend requirements: a component, page, application, or interface to build. They may include context about the purpose, audience, or technical constraints.\n\n## Design Thinking\n\nBefore coding, understand the context and commit to a BOLD aesthetic direction:\n- **Purpose**: What problem does this interface solve? Who uses it?\n- **Tone**: Pick an extreme: brutally minimal, maximalist chaos, retro-futuristic, organic\u002Fnatural, luxury\u002Frefined, playful\u002Ftoy-like, editorial\u002Fmagazine, brutalist\u002Fraw, art deco\u002Fgeometric, soft\u002Fpastel, industrial\u002Futilitarian, etc. There are so many flavors to choose from. Use these for inspiration but design one that is true to the aesthetic direction.\n- **Constraints**: Technical requirements (framework, performance, accessibility).\n- **Differentiation**: What makes this UNFORGETTABLE? What's the one thing someone will remember?\n\n**CRITICAL**: Choose a clear conceptual direction and execute it with precision. Bold maximalism and refined minimalism both work - the key is intentionality, not intensity.\n\nThen implement working code (HTML\u002FCSS\u002FJS, React, Vue, etc.) that is:\n- Production-grade and functional\n- Visually striking and memorable\n- Cohesive with a clear aesthetic point-of-view\n- Meticulously refined in every detail\n\n## Production-Grade Next.js App Router UI Notes\n\nWhen building self-contained pages under `src\u002Fapp\u002F\u003Croute>\u002Fpage.tsx`, especially for dashboards, keep these pragmatic lessons in mind:\n\n- **Self-contained styling**: Inline styles + a small inline `\u003Cstyle>` block for responsive overrides is often the cleanest path here because existing apps usually don't have an Agreed shared CSS layer per route. Prefer `minmax()` grids and `flexWrap: 'wrap'` for resilience.\n- **Mobile responsiveness**: For task-heavy UIs like Kanban boards, use a base 3-column grid and a max-width media query at 680px to collapse to 1 column. Show 2 columns on small screens only when cards are tiny; otherwise prefer the full single-column board.\n- **State and performance**: Use `useMemo` for derived overview counts when local state drives cards. Batch multiple `setState` calls in event handlers with separate functional updates to avoid stale closures.\n- **Local preview stability**: If `npm run dev` fails after adding a new app route with build-manifest ENOTEMPTY\u002FENOENT errors, prefer `npm run start -H 127.0.0.1 -p \u003Calternate port>` for stable local inspection instead of debugging the dev compaction state.\n- **Accessibility\u002FARIA**: Add `aria-label` to icon buttons with text glyphs, label inputs with `\u003Clabel>`, and use `role=\"dialog\"` plus `aria-modal` for modals.\n\n## Frontend Aesthetics Guidelines\n\nFocus on:\n- **Typography**: Choose fonts that are beautiful, unique, and interesting. Avoid generic fonts like Arial and Inter; opt instead for distinctive choices that elevate the frontend's aesthetics; unexpected, characterful font choices. Pair a distinctive display font with a refined body font.\n- **Color & Theme**: Commit to a cohesive aesthetic. Use CSS variables for consistency. Dominant colors with sharp accents outperform timid, evenly-distributed palettes.\n- **Motion**: Use animations for effects and micro-interactions. Prioritize CSS-only solutions for HTML. Use Motion library for React when available. Focus on high-impact moments: one well-orchestrated page load with staggered reveals (animation-delay) creates more delight than scattered micro-interactions. Use scroll-triggering and hover states that surprise.\n- **Spatial Composition**: Unexpected layouts. Asymmetry. Overlap. Diagonal flow. Grid-breaking elements. Generous negative space OR controlled density.\n- **Backgrounds & Visual Details**: Create atmosphere and depth rather than defaulting to solid colors. Add contextual effects and textures that match the overall aesthetic. Apply creative forms like gradient meshes, noise textures, geometric patterns, layered transparencies, dramatic shadows, decorative borders, custom cursors, and grain overlays.\n\nNEVER use generic AI-generated aesthetics like overused font families (Inter, Roboto, Arial, system fonts), cliched color schemes (particularly purple gradients on white backgrounds), predictable layouts and component patterns, and cookie-cutter design that lacks context-specific character.\n\nInterpret creatively and make unexpected choices that feel genuinely designed for the context. No design should be the same. Vary between light and dark themes, different fonts, different aesthetics. NEVER converge on common choices (Space Grotesk, for example) across generations.\n\n**IMPORTANT**: Match implementation complexity to the aesthetic vision. Maximalist designs need elaborate code with extensive animations and effects. Minimalist or refined designs need restraint, precision, and careful attention to spacing, typography, and subtle details. Elegance comes from executing the vision well.\n\nRemember: Claude is capable of extraordinary creative work. Don't hold back, show what can truly be created when thinking outside the box and committing fully to a distinctive vision.\n",{"name":5,"license":25,"description":7},"Complete terms in LICENSE.txt","main","c2b5af98407b1ad3ee4c27fc5bbb56ce09328af6","skills\u002Ffrontend-design","https:\u002F\u002Fgithub.com\u002Fosman-jalloh-lab\u002Fmyos","https:\u002F\u002Fgithub.com\u002Fosman-jalloh-lab","2026-11-04 05:17:57",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add osman-jalloh-lab\u002Fmyos --skill frontend-design",{"tool":38,"command":39},"bunx","bunx skills add osman-jalloh-lab\u002Fmyos --skill frontend-design",{"tool":41,"command":42},"pnpm","pnpm dlx skills add osman-jalloh-lab\u002Fmyos --skill frontend-design","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fosman-jalloh-lab\u002Fmyos\u002Fblob\u002Fmain\u002Fskills\u002Ffrontend-design\u002FSKILL.md",true,[46],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":16},"LICENSE.txt","LICENSE","许可证",10174,[52,60,67,74,81,88],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":56,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":20},"01M75CPVE5M6GXZ39PW5CPKCPK","xurl","X\u002FTwitter via xurl CLI: post, search, DM, media, v2 API.","MIT","https:\u002F\u002Fgithub.com\u002Fosman-jalloh-lab\u002Fmyos\u002Fblob\u002Fmain\u002Fskills\u002Fxurl\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":56,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":20},"01M75CPQ57MF6AM46MXYSGKJ6W","writing-plans","Write implementation plans: bite-sized tasks, paths, code.","https:\u002F\u002Fgithub.com\u002Fosman-jalloh-lab\u002Fmyos\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-plans\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":56,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":20},"01M75CPFNZFXN7FT6NTF21BX5M","touchdesigner-mcp","Control a running TouchDesigner instance via twozero MCP — create operators, set parameters, wire connections, execute Python, build real-time visuals. 36 native tools.","https:\u002F\u002Fgithub.com\u002Fosman-jalloh-lab\u002Fmyos\u002Fblob\u002Fmain\u002Fskills\u002Ftouchdesigner-mcp\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":56,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":20},"01M75CPCKM3C9SN622Z7K5DZX2","test-driven-development","TDD: enforce RED-GREEN-REFACTOR, tests before code.","https:\u002F\u002Fgithub.com\u002Fosman-jalloh-lab\u002Fmyos\u002Fblob\u002Fmain\u002Fskills\u002Ftest-driven-development\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":56,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":20},"01M75CP9C4EWMY810CY1SW231T","teams-meeting-pipeline","Operate the Teams meeting summary pipeline via Hermes CLI — summarize meetings, inspect pipeline status, replay jobs, manage Microsoft Graph subscriptions.","https:\u002F\u002Fgithub.com\u002Fosman-jalloh-lab\u002Fmyos\u002Fblob\u002Fmain\u002Fskills\u002Fteams-meeting-pipeline\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":56,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":20},"01M75CP4K49H7QZQ0Z7HAXKQJR","systematic-debugging","4-phase root cause debugging: understand bugs before fixing.","https:\u002F\u002Fgithub.com\u002Fosman-jalloh-lab\u002Fmyos\u002Fblob\u002Fmain\u002Fskills\u002Fsystematic-debugging\u002FSKILL.md",[],[]]