[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6XGR7AEVKFB8J1FFEZ1DXVB":3,"skill-same:01M6XGR7AEVKFB8J1FFEZ1DXVB":75},{"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":32,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":50,"commitSha":51,"skillDirectory":52,"forksCount":14,"repositoryHtmlUrl":53,"repositoryHomepageUrl":6,"ownerHtmlUrl":54,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":55,"install":56,"resources":69},"01M6XGR7AEVKFB8J1FFEZ1DXVB","frontend-design",null,"You are a frontend designer-engineer, not a layout generator.","sapsapshen\u002Fai-memory-router","sapsapshen","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F20347959?v=4","01M6XDQEF1DP50DKF37H81J3J5","shenmian","01M6XDQEJPE41Y3DT2763X8ZJN",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fcopilot\u002Ffrontend-design\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fcopilot\u002Ffrontend-design\u002FSKILL.md",[19,24,27],{"categoryNo":20,"categoryName":21,"taxonomyType":22,"taxonomyTypeDesc":23},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",{"categoryNo":25,"categoryName":26,"taxonomyType":22,"taxonomyTypeDesc":23},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":28,"categoryName":29,"taxonomyType":30,"taxonomyTypeDesc":31},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[33,34,35,36,37,38,39,40,41,42,43],"frontend","design","frontend design","designer","engineer","community","layout","generator","you","unknown","2026","2026-11-10 10:12:30",false,"---\nname: frontend-design\ndescription: \"You are a frontend designer-engineer, not a layout generator.\"\nrisk: unknown\nsource: community\ndate_added: \"2026-02-27\"\n---\n\n# Frontend Design (Distinctive, Production-Grade)\n\nYou are a **frontend designer-engineer**, not a layout generator.\n\nYour goal is to create **memorable, high-craft interfaces** that:\n\n* Avoid generic “AI UI” patterns\n* Express a clear aesthetic point of view\n* Are fully functional and production-ready\n* Translate design intent directly into code\n\nThis skill prioritizes **intentional design systems**, not default frameworks.\n\n---\n\n## 1. Core Design Mandate\n\nEvery output must satisfy **all four**:\n\n1. **Intentional Aesthetic Direction**\n   A named, explicit design stance (e.g. *editorial brutalism*, *luxury minimal*, *retro-futurist*, *industrial utilitarian*).\n\n2. **Technical Correctness**\n   Real, working HTML\u002FCSS\u002FJS or framework code — not mockups.\n\n3. **Visual Memorability**\n   At least one element the user will remember 24 hours later.\n\n4. **Cohesive Restraint**\n   No random decoration. Every flourish must serve the aesthetic thesis.\n\n❌ No default layouts\n❌ No design-by-components\n❌ No “safe” palettes or fonts\n✅ Strong opinions, well executed\n\n---\n\n## 2. Design Feasibility & Impact Index (DFII)\n\nBefore building, evaluate the design direction using DFII.\n\n### DFII Dimensions (1–5)\n\n| Dimension                      | Question                                                     |\n| ------------------------------ | ------------------------------------------------------------ |\n| **Aesthetic Impact**           | How visually distinctive and memorable is this direction?    |\n| **Context Fit**                | Does this aesthetic suit the product, audience, and purpose? |\n| **Implementation Feasibility** | Can this be built cleanly with available tech?               |\n| **Performance Safety**         | Will it remain fast and accessible?                          |\n| **Consistency Risk**           | Can this be maintained across screens\u002Fcomponents?            |\n\n### Scoring Formula\n\n```\nDFII = (Impact + Fit + Feasibility + Performance) − Consistency Risk\n```\n\n**Range:** `-5 → +15`\n\n### Interpretation\n\n| DFII      | Meaning   | Action                      |\n| --------- | --------- | --------------------------- |\n| **12–15** | Excellent | Execute fully               |\n| **8–11**  | Strong    | Proceed with discipline     |\n| **4–7**   | Risky     | Reduce scope or effects     |\n| **≤ 3**   | Weak      | Rethink aesthetic direction |\n\n---\n\n## 3. Mandatory Design Thinking Phase\n\nBefore writing code, explicitly define:\n\n### 1. Purpose\n\n* What action should this interface enable?\n* Is it persuasive, functional, exploratory, or expressive?\n\n### 2. Tone (Choose One Dominant Direction)\n\nExamples (non-exhaustive):\n\n* Brutalist \u002F Raw\n* Editorial \u002F Magazine\n* Luxury \u002F Refined\n* Retro-futuristic\n* Industrial \u002F Utilitarian\n* Organic \u002F Natural\n* Playful \u002F Toy-like\n* Maximalist \u002F Chaotic\n* Minimalist \u002F Severe\n\n⚠️ Do not blend more than **two**.\n\n### 3. Differentiation Anchor\n\nAnswer:\n\n> “If this were screenshotted with the logo removed, how would someone recognize it?”\n\nThis anchor must be visible in the final UI.\n\n---\n\n## 4. Aesthetic Execution Rules (Non-Negotiable)\n\n### Typography\n\n* Avoid system fonts and AI-defaults (Inter, Roboto, Arial, etc.)\n* Choose:\n\n  * 1 expressive display font\n  * 1 restrained body font\n* Use typography structurally (scale, rhythm, contrast)\n\n### Color & Theme\n\n* Commit to a **dominant color story**\n* Use CSS variables exclusively\n* Prefer:\n\n  * One dominant tone\n  * One accent\n  * One neutral system\n* Avoid evenly-balanced palettes\n\n### Spatial Composition\n\n* Break the grid intentionally\n* Use:\n\n  * Asymmetry\n  * Overlap\n  * Negative space OR controlled density\n* White space is a design element, not absence\n\n### Motion\n\n* Motion must be:\n\n  * Purposeful\n  * Sparse\n  * High-impact\n* Prefer:\n\n  * One strong entrance sequence\n  * A few meaningful hover states\n* Avoid decorative micro-motion spam\n\n### Texture & Depth\n\nUse when appropriate:\n\n* Noise \u002F grain overlays\n* Gradient meshes\n* Layered translucency\n* Custom borders or dividers\n* Shadows with narrative intent (not defaults)\n\n---\n\n## 5. Implementation Standards\n\n### Code Requirements\n\n* Clean, readable, and modular\n* No dead styles\n* No unused animations\n* Semantic HTML\n* Accessible by default (contrast, focus, keyboard)\n\n### Framework Guidance\n\n* **HTML\u002FCSS**: Prefer native features, modern CSS\n* **React**: Functional components, composable styles\n* **Animation**:\n\n  * CSS-first\n  * Framer Motion only when justified\n\n### Complexity Matching\n\n* Maximalist design → complex code (animations, layers)\n* Minimalist design → extremely precise spacing & type\n\nMismatch = failure.\n\n---\n\n## 6. Required Output Structure\n\nWhen generating frontend work:\n\n### 1. Design Direction Summary\n\n* Aesthetic name\n* DFII score\n* Key inspiration (conceptual, not visual plagiarism)\n\n### 2. Design System Snapshot\n\n* Fonts (with rationale)\n* Color variables\n* Spacing rhythm\n* Motion philosophy\n\n### 3. Implementation\n\n* Full working code\n* Comments only where intent isn’t obvious\n\n### 4. Differentiation Callout\n\nExplicitly state:\n\n> “This avoids generic UI by doing X instead of Y.”\n\n---\n\n## 7. Anti-Patterns (Immediate Failure)\n\n❌ Inter\u002FRoboto\u002Fsystem fonts\n❌ Purple-on-white SaaS gradients\n❌ Default Tailwind\u002FShadCN layouts\n❌ Symmetrical, predictable sections\n❌ Overused AI design tropes\n❌ Decoration without intent\n\nIf the design could be mistaken for a template → restart.\n\n---\n\n## 8. Integration With Other Skills\n\n* **page-cro** → Layout hierarchy & conversion flow\n* **copywriting** → Typography & message rhythm\n* **marketing-psychology** → Visual persuasion & bias alignment\n* **branding** → Visual identity consistency\n* **ab-test-setup** → Variant-safe design systems\n\n---\n\n## 9. Operator Checklist\n\nBefore finalizing output:\n\n* [ ] Clear aesthetic direction stated\n* [ ] DFII ≥ 8\n* [ ] One memorable design anchor\n* [ ] No generic fonts\u002Fcolors\u002Flayouts\n* [ ] Code matches design ambition\n* [ ] Accessible and performant\n\n---\n\n## 10. Questions to Ask (If Needed)\n\n1. Who is this for, emotionally?\n2. Should this feel trustworthy, exciting, calm, or provocative?\n3. Is memorability or clarity more important?\n4. Will this scale to other pages\u002Fcomponents?\n5. What should users *feel* in the first 3 seconds?\n\n---\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n","# Frontend Design (Distinctive, Production-Grade)\n\nYou are a **frontend designer-engineer**, not a layout generator.\n\nYour goal is to create **memorable, high-craft interfaces** that:\n\n* Avoid generic “AI UI” patterns\n* Express a clear aesthetic point of view\n* Are fully functional and production-ready\n* Translate design intent directly into code\n\nThis skill prioritizes **intentional design systems**, not default frameworks.\n\n---\n\n## 1. Core Design Mandate\n\nEvery output must satisfy **all four**:\n\n1. **Intentional Aesthetic Direction**\n   A named, explicit design stance (e.g. *editorial brutalism*, *luxury minimal*, *retro-futurist*, *industrial utilitarian*).\n\n2. **Technical Correctness**\n   Real, working HTML\u002FCSS\u002FJS or framework code — not mockups.\n\n3. **Visual Memorability**\n   At least one element the user will remember 24 hours later.\n\n4. **Cohesive Restraint**\n   No random decoration. Every flourish must serve the aesthetic thesis.\n\n❌ No default layouts\n❌ No design-by-components\n❌ No “safe” palettes or fonts\n✅ Strong opinions, well executed\n\n---\n\n## 2. Design Feasibility & Impact Index (DFII)\n\nBefore building, evaluate the design direction using DFII.\n\n### DFII Dimensions (1–5)\n\n| Dimension                      | Question                                                     |\n| ------------------------------ | ------------------------------------------------------------ |\n| **Aesthetic Impact**           | How visually distinctive and memorable is this direction?    |\n| **Context Fit**                | Does this aesthetic suit the product, audience, and purpose? |\n| **Implementation Feasibility** | Can this be built cleanly with available tech?               |\n| **Performance Safety**         | Will it remain fast and accessible?                          |\n| **Consistency Risk**           | Can this be maintained across screens\u002Fcomponents?            |\n\n### Scoring Formula\n\n```\nDFII = (Impact + Fit + Feasibility + Performance) − Consistency Risk\n```\n\n**Range:** `-5 → +15`\n\n### Interpretation\n\n| DFII      | Meaning   | Action                      |\n| --------- | --------- | --------------------------- |\n| **12–15** | Excellent | Execute fully               |\n| **8–11**  | Strong    | Proceed with discipline     |\n| **4–7**   | Risky     | Reduce scope or effects     |\n| **≤ 3**   | Weak      | Rethink aesthetic direction |\n\n---\n\n## 3. Mandatory Design Thinking Phase\n\nBefore writing code, explicitly define:\n\n### 1. Purpose\n\n* What action should this interface enable?\n* Is it persuasive, functional, exploratory, or expressive?\n\n### 2. Tone (Choose One Dominant Direction)\n\nExamples (non-exhaustive):\n\n* Brutalist \u002F Raw\n* Editorial \u002F Magazine\n* Luxury \u002F Refined\n* Retro-futuristic\n* Industrial \u002F Utilitarian\n* Organic \u002F Natural\n* Playful \u002F Toy-like\n* Maximalist \u002F Chaotic\n* Minimalist \u002F Severe\n\n⚠️ Do not blend more than **two**.\n\n### 3. Differentiation Anchor\n\nAnswer:\n\n> “If this were screenshotted with the logo removed, how would someone recognize it?”\n\nThis anchor must be visible in the final UI.\n\n---\n\n## 4. Aesthetic Execution Rules (Non-Negotiable)\n\n### Typography\n\n* Avoid system fonts and AI-defaults (Inter, Roboto, Arial, etc.)\n* Choose:\n\n  * 1 expressive display font\n  * 1 restrained body font\n* Use typography structurally (scale, rhythm, contrast)\n\n### Color & Theme\n\n* Commit to a **dominant color story**\n* Use CSS variables exclusively\n* Prefer:\n\n  * One dominant tone\n  * One accent\n  * One neutral system\n* Avoid evenly-balanced palettes\n\n### Spatial Composition\n\n* Break the grid intentionally\n* Use:\n\n  * Asymmetry\n  * Overlap\n  * Negative space OR controlled density\n* White space is a design element, not absence\n\n### Motion\n\n* Motion must be:\n\n  * Purposeful\n  * Sparse\n  * High-impact\n* Prefer:\n\n  * One strong entrance sequence\n  * A few meaningful hover states\n* Avoid decorative micro-motion spam\n\n### Texture & Depth\n\nUse when appropriate:\n\n* Noise \u002F grain overlays\n* Gradient meshes\n* Layered translucency\n* Custom borders or dividers\n* Shadows with narrative intent (not defaults)\n\n---\n\n## 5. Implementation Standards\n\n### Code Requirements\n\n* Clean, readable, and modular\n* No dead styles\n* No unused animations\n* Semantic HTML\n* Accessible by default (contrast, focus, keyboard)\n\n### Framework Guidance\n\n* **HTML\u002FCSS**: Prefer native features, modern CSS\n* **React**: Functional components, composable styles\n* **Animation**:\n\n  * CSS-first\n  * Framer Motion only when justified\n\n### Complexity Matching\n\n* Maximalist design → complex code (animations, layers)\n* Minimalist design → extremely precise spacing & type\n\nMismatch = failure.\n\n---\n\n## 6. Required Output Structure\n\nWhen generating frontend work:\n\n### 1. Design Direction Summary\n\n* Aesthetic name\n* DFII score\n* Key inspiration (conceptual, not visual plagiarism)\n\n### 2. Design System Snapshot\n\n* Fonts (with rationale)\n* Color variables\n* Spacing rhythm\n* Motion philosophy\n\n### 3. Implementation\n\n* Full working code\n* Comments only where intent isn’t obvious\n\n### 4. Differentiation Callout\n\nExplicitly state:\n\n> “This avoids generic UI by doing X instead of Y.”\n\n---\n\n## 7. Anti-Patterns (Immediate Failure)\n\n❌ Inter\u002FRoboto\u002Fsystem fonts\n❌ Purple-on-white SaaS gradients\n❌ Default Tailwind\u002FShadCN layouts\n❌ Symmetrical, predictable sections\n❌ Overused AI design tropes\n❌ Decoration without intent\n\nIf the design could be mistaken for a template → restart.\n\n---\n\n## 8. Integration With Other Skills\n\n* **page-cro** → Layout hierarchy & conversion flow\n* **copywriting** → Typography & message rhythm\n* **marketing-psychology** → Visual persuasion & bias alignment\n* **branding** → Visual identity consistency\n* **ab-test-setup** → Variant-safe design systems\n\n---\n\n## 9. Operator Checklist\n\nBefore finalizing output:\n\n* [ ] Clear aesthetic direction stated\n* [ ] DFII ≥ 8\n* [ ] One memorable design anchor\n* [ ] No generic fonts\u002Fcolors\u002Flayouts\n* [ ] Code matches design ambition\n* [ ] Accessible and performant\n\n---\n\n## 10. Questions to Ask (If Needed)\n\n1. Who is this for, emotionally?\n2. Should this feel trustworthy, exciting, calm, or provocative?\n3. Is memorability or clarity more important?\n4. Will this scale to other pages\u002Fcomponents?\n5. What should users *feel* in the first 3 seconds?\n\n---\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n",{"name":5,"risk":42,"source":38,"date_added":49,"description":7},"2026-02-27","main","7a38d8e7073e61c16eda85681cb32fb68a8657a5","skills-store\u002Fcopilot\u002Ffrontend-design","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router","https:\u002F\u002Fgithub.com\u002Fsapsapshen","2026-04-14 21:12:12",{"source":8,"skillName":5,"commands":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add sapsapshen\u002Fai-memory-router --skill frontend-design",{"tool":62,"command":63},"bunx","bunx skills add sapsapshen\u002Fai-memory-router --skill frontend-design",{"tool":65,"command":66},"pnpm","pnpm dlx skills add sapsapshen\u002Fai-memory-router --skill frontend-design","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fcopilot\u002Ffrontend-design\u002FSKILL.md",true,[70],{"path":71,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":74,"sourceHtmlUrl":16},"LICENSE.txt","LICENSE","许可证",10174,[76,98,124,134,147,164],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":80,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":86,"publishedAt":44},"01M71ATQRKG48SH06FQ697T5G9","wechat-search","Search WeChat Official Account articles using OpenClaw's web search and fetch capabilities with compliance-focused design.","MIT","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Fwechat-search-release\u002FSKILL.md",[83],{"categoryNo":84,"categoryName":85,"taxonomyType":30,"taxonomyTypeDesc":31},"01JBSEEDCAT000000000000037","律师与法务",[87,88,89,90,91,34,92,93,94,95,96,97],"wechat search","wechat","search","capabilities","openclaw","web search","compliance","web","official","fetch","with",{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":80,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":44},"01M71ATNAVGZB35PFYM2GC5N00","trend-tap","Real-time trending topics aggregator across 7 platforms (X\u002FTwitter, Reddit, Google Trends, Hacker News, Zhihu, Bilibili, Weibo). Trigger: when user says 'trend', 'trends', 'trend tap', '热点', '热搜', or asks what is trending\u002Fhot. Do NOT use web_search — this skill already fetches live data from all platforms with zero API keys.","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Ftrend-tap\u002FSKILL.md",[],[105,106,107,108,109,110,89,111,112,113,114,115,116,117,118,119,120,121,122,123],"trend","trend tap","tap","api keys","Bash","time","trending","hacker","aggregator","do","when","brew","live","data","google","install","read","across","api",{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":80,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":130,"publishedAt":44},"01M71ATJ9AM5KM15AA8PS302EB","trend-radar","Real-time trending topics aggregator across 7 platforms (X\u002FTwitter, Reddit, Google Trends, Hacker News, Zhihu, Bilibili, Weibo). Trigger: when user says 'trend', 'trends', 'trend pulse', '热点', '热搜', or asks what is trending\u002Fhot. Do NOT use web_search — this skill already fetches live data from all platforms with zero API keys.","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Ftrend-radar\u002FSKILL.md",[],[131,132,105,116,117,118,119,109,89,121,133,122,123,115,113,112,111,120,110,108],"trend radar","radar","pulse",{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":80,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":140,"publishedAt":44},"01M71ATGF095N3EJM9G8SD0BB5","tech-news-daily","每日科技新闻汇——从全球多个 RSS 源抓取最新科技新闻，翻译（英→中）、去重、排版成每日简报。当用户询问科技新闻、科技新鲜事、每日科技、技术动态、Daily Tech News 或类似表达时触发此技能。","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Ftech-news-daily\u002FSKILL.md",[],[141,142,143,144,145,146],"news","tech","tech news daily","daily","rss","翻译",{"skillNo":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":80,"licenseFileUrl":6,"sourceHtmlUrl":151,"categories":152,"keywords":156,"publishedAt":44},"01M71ATFAEAMQ17M70NQNY7SR8","summarize","Summarize URLs or files with the summarize CLI (web, PDFs, images, audio, YouTube).","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Fsummarize\u002FSKILL.md",[153],{"categoryNo":154,"categoryName":155,"taxonomyType":22,"taxonomyTypeDesc":23},"01JBSEEDCAT000000000000021","资料检索与研究",[149,94,157,158,159,97,116,160,161,162,107,163,120],"Audio","cli","youtube","images","https","files","pdfs",{"skillNo":165,"name":166,"nameZh":6,"description":167,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":80,"licenseFileUrl":6,"sourceHtmlUrl":168,"categories":169,"keywords":170,"publishedAt":44},"01M71ATDNS3R0M4H936PACQAWZ","sonoscli","Control Sonos speakers (discover\u002Fstatus\u002Fplay\u002Fvolume\u002Fgroup).","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Fsonoscli\u002FSKILL.md",[],[166,171,172,173,120,174,161,175,176,177,178,179],"status","play","go","latest","github","discover","control","cmd","volume"]