[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6G9GRAZ6EVCX14FYWP3QDQ9":3,"skill-same:01M6G9GRAZ6EVCX14FYWP3QDQ9":98},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":33,"publishedAt":54,"linkOnly":55,"markdownContent":56,"markdownBody":57,"frontMatter":58,"refName":44,"commitSha":61,"skillDirectory":62,"forksCount":13,"repositoryHtmlUrl":63,"repositoryHomepageUrl":6,"ownerHtmlUrl":64,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":65,"install":66,"resources":79},"01M6G9GRAZ6EVCX14FYWP3QDQ9","frontend-design-review",null,"Review and create distinctive, production-grade frontend interfaces with high design quality and design system compliance. Evaluates using three pillars: frictionless insight-to-action, quality craft, and trustworthy building. USE FOR: PR reviews, design reviews, accessibility audits, design system compliance checks, creative frontend design, UI code review, component reviews, responsive design checks, theme testing, and creating memorable UI. DO NOT USE FOR: Backend API reviews, database schema reviews, infrastructure or DevOps work, pure business logic without UI, or non-frontend code.","ricardoaevt\u002Fnexus-roms","ricardoaevt","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F164531880?v=4","01M6DGFGSV6CF9AKPHABBREC79","01M6DGFGYNNPJVDFQA05TDPSBN",0,"AGPL-3.0","https:\u002F\u002Fgithub.com\u002Fricardoaevt\u002Fnexus-roms\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fmicrosoft_skills\u002F.github\u002Fskills\u002Ffrontend-design-review\u002FSKILL.md",[17,22,25,28],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":26,"categoryName":27,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":29,"categoryName":30,"taxonomyType":31,"taxonomyTypeDesc":32},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53],"frontend","design","frontend design","review","design review","frontend design review","code","reviews","database schema","backend api","main","responsive design","craft","work","api","database","code review","create","component","testing","2026-11-10 10:12:30",false,"---\nname: frontend-design-review\ndescription: >\n  Review and create distinctive, production-grade frontend interfaces with high design quality and design system compliance.\n  Evaluates using three pillars: frictionless insight-to-action, quality craft, and trustworthy building.\n  USE FOR: PR reviews, design reviews, accessibility audits, design system compliance checks, creative frontend design,\n  UI code review, component reviews, responsive design checks, theme testing, and creating memorable UI.\n  DO NOT USE FOR: Backend API reviews, database schema reviews, infrastructure or DevOps work, pure business logic\n  without UI, or non-frontend code.\nacknowledgments: |\n  Design review principles and quality pillar framework created by @Quirinevwm (https:\u002F\u002Fgithub.com\u002FQuirinevwm).\n  Creative frontend guidance inspired by Anthropic's frontend-design skill\n  (https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fskills\u002Ftree\u002Fmain\u002Fskills\u002Ffrontend-design). Licensed under respective terms.\n---\n\n# Frontend Design Review\n\nReview UI implementations against design quality standards and your design system **OR** create distinctive, production-grade frontend interfaces from scratch.\n\n## Two Modes\n\n### Mode 1: Design Review\nEvaluate existing UI for design system compliance, three quality pillars (Frictionless, Quality Craft, Trustworthy), accessibility, and code quality.\n\n### Mode 2: Creative Frontend Design\nCreate distinctive interfaces that avoid generic \"AI slop\" aesthetics, have clear conceptual direction, and execute with precision.\n\n---\n\n## Creative Frontend Design\n\nBefore coding, commit to an aesthetic direction:\n- **Purpose**: What problem does this solve? Who uses it?\n- **Tone**: minimal, maximalist, retro-futuristic, organic, luxury, playful, editorial, brutalist, art deco, soft\u002Fpastel, industrial, etc.\n- **Constraints**: Framework, performance, accessibility requirements.\n- **Differentiation**: What makes this distinctive and context-appropriate?\n\n### Aesthetics Guidelines\n\n- **Typography**: Distinctive fonts that elevate aesthetics. Pair a display font with a refined body font. Avoid Inter, Roboto, Arial, Space Grotesk.\n- **Color & Theme**: Cohesive palette with CSS variables. Dominant colors + sharp accents > timid, evenly-distributed palettes.\n- **Motion**: CSS-only preferred. One well-orchestrated page load with staggered reveals > scattered micro-interactions.\n- **Spatial Composition**: Asymmetry, overlap, diagonal flow, grid-breaking elements, generous negative space OR controlled density.\n- **Backgrounds**: Gradient meshes, noise textures, geometric patterns, layered transparencies, dramatic shadows, grain overlays.\n\n**AVOID**: Overused fonts, cliched color schemes, predictable layouts, cookie-cutter design without context-specific character.\n\nMatch implementation complexity to vision. Maximalist = elaborate code. Minimalist = restraint and precision.\n\n---\n\n## Design Review\n\n### Design System Workflow\n\n**Before implementing:**\n1. Review component in your Storybook \u002F component library for API and usage\n2. Use Figma Dev Mode to get exact specs (spacing, tokens, properties)\n3. Implement using design system components + design tokens\n\n**During review:**\n1. Compare implementation to Figma design\n2. Verify design tokens are used (not hardcoded values)\n3. Check all variants\u002Fstates are implemented correctly\n4. Flag deviations (needs design approval)\n\n**If component doesn't exist:**\n1. Check if existing component can be adapted\n2. Reach out to design for new component creation\n3. Document exception and rationale in code\n\n### Review Process\n\n1. Identify user task\n2. Check design system for matching patterns\n3. Evaluate aesthetic direction\n4. Identify scope (component, feature, or flow)\n5. Evaluate each pillar\n6. Score and prioritize issues (blocking\u002Fmajor\u002Fminor)\n7. Provide recommendations with design system examples\n\n### Core Principles\n\n- **Task completion**: Minimum clicks. Every screen answers \"What can I do?\" and \"What happens next?\"\n- **Action hierarchy**: 1-2 primary actions per view. Progressive disclosure for secondary.\n- **Onboarding**: Explain features on introduction. Smart defaults over configuration.\n- **Navigation**: Clear entry\u002Fexit points. Back\u002Fcancel always available. Breadcrumbs for deep flows.\n\n---\n\n## Quality Pillars\n\n### 1. Frictionless Insight to Action\n\n**Evaluate:** Task completable in ≤3 interactions? Primary action obvious and singular?\n\n**Red flags:** Excessive clicks, multiple competing primary buttons, buried actions, dead ends.\n\n### 2. Quality is Craft\n\n**Evaluate:**\n- Design system compliance: matches Figma specs, uses design tokens\n- Aesthetic direction: distinctive typography, cohesive colors, intentional motion\n- Accessibility: Grade C minimum (WCAG 2.1 A), Grade B ideal (WCAG 2.1 AA)\n\n**Red flags:** Generic AI aesthetics, hardcoded values, implementation doesn't match Figma, broken reflow, missing focus indicators.\n\n### 3. Trustworthy Building\n\n**Evaluate:**\n- AI transparency: disclaimer on AI-generated content\n- Error transparency: actionable error messages\n\n**Red flags:** Missing AI disclaimers, opaque errors without guidance.\n\n---\n\n## Review Output Format\n\nSee [references\u002Freview-output-format.md](references\u002Freview-output-format.md) for the full review template.\n\n## Review Type Modifiers\n\nSee [references\u002Freview-type-modifiers.md](references\u002Freview-type-modifiers.md) for context-specific review focus areas (PR, Creative, Design, Accessibility).\n\n## Quick Checklist\n\nSee [references\u002Fquick-checklist.md](references\u002Fquick-checklist.md) for the pre-approval checklist covering design system compliance, aesthetic quality, frictionless, quality craft, and trustworthy pillars.\n\n## Pattern Examples\n\nSee [references\u002Fpattern-examples.md](references\u002Fpattern-examples.md) for good\u002Fbad examples of creative frontend and design system review work.\n\n---\n\n## Acknowledgments\n\nCreative frontend principles inspired by [Anthropic's frontend-design skill](https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fskills\u002Ftree\u002Fmain\u002Fskills\u002Ffrontend-design). Design review principles and quality pillar framework created by [@Quirinevwm](https:\u002F\u002Fgithub.com\u002FQuirinevwm) for systematic UI evaluation.\n","# Frontend Design Review\n\nReview UI implementations against design quality standards and your design system **OR** create distinctive, production-grade frontend interfaces from scratch.\n\n## Two Modes\n\n### Mode 1: Design Review\nEvaluate existing UI for design system compliance, three quality pillars (Frictionless, Quality Craft, Trustworthy), accessibility, and code quality.\n\n### Mode 2: Creative Frontend Design\nCreate distinctive interfaces that avoid generic \"AI slop\" aesthetics, have clear conceptual direction, and execute with precision.\n\n---\n\n## Creative Frontend Design\n\nBefore coding, commit to an aesthetic direction:\n- **Purpose**: What problem does this solve? Who uses it?\n- **Tone**: minimal, maximalist, retro-futuristic, organic, luxury, playful, editorial, brutalist, art deco, soft\u002Fpastel, industrial, etc.\n- **Constraints**: Framework, performance, accessibility requirements.\n- **Differentiation**: What makes this distinctive and context-appropriate?\n\n### Aesthetics Guidelines\n\n- **Typography**: Distinctive fonts that elevate aesthetics. Pair a display font with a refined body font. Avoid Inter, Roboto, Arial, Space Grotesk.\n- **Color & Theme**: Cohesive palette with CSS variables. Dominant colors + sharp accents > timid, evenly-distributed palettes.\n- **Motion**: CSS-only preferred. One well-orchestrated page load with staggered reveals > scattered micro-interactions.\n- **Spatial Composition**: Asymmetry, overlap, diagonal flow, grid-breaking elements, generous negative space OR controlled density.\n- **Backgrounds**: Gradient meshes, noise textures, geometric patterns, layered transparencies, dramatic shadows, grain overlays.\n\n**AVOID**: Overused fonts, cliched color schemes, predictable layouts, cookie-cutter design without context-specific character.\n\nMatch implementation complexity to vision. Maximalist = elaborate code. Minimalist = restraint and precision.\n\n---\n\n## Design Review\n\n### Design System Workflow\n\n**Before implementing:**\n1. Review component in your Storybook \u002F component library for API and usage\n2. Use Figma Dev Mode to get exact specs (spacing, tokens, properties)\n3. Implement using design system components + design tokens\n\n**During review:**\n1. Compare implementation to Figma design\n2. Verify design tokens are used (not hardcoded values)\n3. Check all variants\u002Fstates are implemented correctly\n4. Flag deviations (needs design approval)\n\n**If component doesn't exist:**\n1. Check if existing component can be adapted\n2. Reach out to design for new component creation\n3. Document exception and rationale in code\n\n### Review Process\n\n1. Identify user task\n2. Check design system for matching patterns\n3. Evaluate aesthetic direction\n4. Identify scope (component, feature, or flow)\n5. Evaluate each pillar\n6. Score and prioritize issues (blocking\u002Fmajor\u002Fminor)\n7. Provide recommendations with design system examples\n\n### Core Principles\n\n- **Task completion**: Minimum clicks. Every screen answers \"What can I do?\" and \"What happens next?\"\n- **Action hierarchy**: 1-2 primary actions per view. Progressive disclosure for secondary.\n- **Onboarding**: Explain features on introduction. Smart defaults over configuration.\n- **Navigation**: Clear entry\u002Fexit points. Back\u002Fcancel always available. Breadcrumbs for deep flows.\n\n---\n\n## Quality Pillars\n\n### 1. Frictionless Insight to Action\n\n**Evaluate:** Task completable in ≤3 interactions? Primary action obvious and singular?\n\n**Red flags:** Excessive clicks, multiple competing primary buttons, buried actions, dead ends.\n\n### 2. Quality is Craft\n\n**Evaluate:**\n- Design system compliance: matches Figma specs, uses design tokens\n- Aesthetic direction: distinctive typography, cohesive colors, intentional motion\n- Accessibility: Grade C minimum (WCAG 2.1 A), Grade B ideal (WCAG 2.1 AA)\n\n**Red flags:** Generic AI aesthetics, hardcoded values, implementation doesn't match Figma, broken reflow, missing focus indicators.\n\n### 3. Trustworthy Building\n\n**Evaluate:**\n- AI transparency: disclaimer on AI-generated content\n- Error transparency: actionable error messages\n\n**Red flags:** Missing AI disclaimers, opaque errors without guidance.\n\n---\n\n## Review Output Format\n\nSee [references\u002Freview-output-format.md](references\u002Freview-output-format.md) for the full review template.\n\n## Review Type Modifiers\n\nSee [references\u002Freview-type-modifiers.md](references\u002Freview-type-modifiers.md) for context-specific review focus areas (PR, Creative, Design, Accessibility).\n\n## Quick Checklist\n\nSee [references\u002Fquick-checklist.md](references\u002Fquick-checklist.md) for the pre-approval checklist covering design system compliance, aesthetic quality, frictionless, quality craft, and trustworthy pillars.\n\n## Pattern Examples\n\nSee [references\u002Fpattern-examples.md](references\u002Fpattern-examples.md) for good\u002Fbad examples of creative frontend and design system review work.\n\n---\n\n## Acknowledgments\n\nCreative frontend principles inspired by [Anthropic's frontend-design skill](https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fskills\u002Ftree\u002Fmain\u002Fskills\u002Ffrontend-design). Design review principles and quality pillar framework created by [@Quirinevwm](https:\u002F\u002Fgithub.com\u002FQuirinevwm) for systematic UI evaluation.\n",{"name":5,"description":59,"acknowledgments":60},"Review and create distinctive, production-grade frontend interfaces with high design quality and design system compliance. Evaluates using three pillars: frictionless insight-to-action, quality craft, and trustworthy building. USE FOR: PR reviews, design reviews, accessibility audits, design system compliance checks, creative frontend design, UI code review, component reviews, responsive design checks, theme testing, and creating memorable UI. DO NOT USE FOR: Backend API reviews, database schema reviews, infrastructure or DevOps work, pure business logic without UI, or non-frontend code.\n","Design review principles and quality pillar framework created by @Quirinevwm (https:\u002F\u002Fgithub.com\u002FQuirinevwm).\nCreative frontend guidance inspired by Anthropic's frontend-design skill\n(https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fskills\u002Ftree\u002Fmain\u002Fskills\u002Ffrontend-design). Licensed under respective terms.","d41309588593cee5c2fb44062474efc3a99fbcb6",".agent\u002Fskills\u002Fmicrosoft_skills\u002F.github\u002Fskills\u002Ffrontend-design-review","https:\u002F\u002Fgithub.com\u002Fricardoaevt\u002Fnexus-roms","https:\u002F\u002Fgithub.com\u002Fricardoaevt","2026-03-23 00:05:03",{"source":8,"skillName":5,"commands":67,"prompt":77,"zipAvailable":78},[68,71,74],{"tool":69,"command":70},"npx","npx skills add ricardoaevt\u002Fnexus-roms --skill frontend-design-review",{"tool":72,"command":73},"bunx","bunx skills add ricardoaevt\u002Fnexus-roms --skill frontend-design-review",{"tool":75,"command":76},"pnpm","pnpm dlx skills add ricardoaevt\u002Fnexus-roms --skill frontend-design-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fricardoaevt\u002Fnexus-roms\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fmicrosoft_skills\u002F.github\u002Fskills\u002Ffrontend-design-review\u002FSKILL.md",true,[80,86,90,94],{"path":81,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":84,"sourceHtmlUrl":85},"references\u002Fpattern-examples.md","REFERENCE","参考文档",759,"https:\u002F\u002Fgithub.com\u002Fricardoaevt\u002Fnexus-roms\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fmicrosoft_skills\u002F.github\u002Fskills\u002Ffrontend-design-review\u002Freferences\u002Fpattern-examples.md",{"path":87,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":88,"sourceHtmlUrl":89},"references\u002Fquick-checklist.md",1556,"https:\u002F\u002Fgithub.com\u002Fricardoaevt\u002Fnexus-roms\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fmicrosoft_skills\u002F.github\u002Fskills\u002Ffrontend-design-review\u002Freferences\u002Fquick-checklist.md",{"path":91,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":92,"sourceHtmlUrl":93},"references\u002Freview-output-format.md",2790,"https:\u002F\u002Fgithub.com\u002Fricardoaevt\u002Fnexus-roms\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fmicrosoft_skills\u002F.github\u002Fskills\u002Ffrontend-design-review\u002Freferences\u002Freview-output-format.md",{"path":95,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":96,"sourceHtmlUrl":97},"references\u002Freview-type-modifiers.md",1644,"https:\u002F\u002Fgithub.com\u002Fricardoaevt\u002Fnexus-roms\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fmicrosoft_skills\u002F.github\u002Fskills\u002Ffrontend-design-review\u002Freferences\u002Freview-type-modifiers.md",[99,123,138,153,164,173],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":103,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":54},"01M6G9HYKQRK6HBKVTZM3258M3","openspec-propose","Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.","MIT","https:\u002F\u002Fgithub.com\u002Fricardoaevt\u002Fnexus-roms\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fopenspec-propose\u002FSKILL.md",[],[107,108,109,110,111,112,113,114,115,116,117,118,119,120,121,122,35],"openspec propose","openspec","cli","generated","with","proposal","complete","get","build","implementation","ready","use","user","artifacts","tasks","change",{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":103,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":54},"01M6G9HV9V20WFCHYVSDNQMJVK","openspec-new-change","Start a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach.","https:\u002F\u002Fgithub.com\u002Fricardoaevt\u002Fnexus-roms\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fopenspec-new-change\u002FSKILL.md",[],[108,130,122,131,109,132,133,134,118,119,51,135,136,137,111],"openspec new change","new feature","structured","artifact","workflow","start","fix","feature",{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":103,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":144,"publishedAt":54},"01M6G9HRF6R89QZXGSFC9DRQW3","openspec-explore","Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.","https:\u002F\u002Fgithub.com\u002Fricardoaevt\u002Fnexus-roms\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fopenspec-explore\u002FSKILL.md",[],[145,146,108,118,147,109,122,119,148,149,150,151,152],"openspec explore","explore","partner","think","thinking partner","thinking","ideas","requirements",{"skillNo":154,"name":155,"nameZh":6,"description":156,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":103,"licenseFileUrl":6,"sourceHtmlUrl":157,"categories":158,"keywords":159,"publishedAt":54},"01M6G9HP3APFCXZG7XRWBMM524","openspec-continue-change","Continue working on an OpenSpec change by creating the next artifact. Use when the user wants to progress their change, create the next artifact, or continue their workflow.","https:\u002F\u002Fgithub.com\u002Fricardoaevt\u002Fnexus-roms\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fopenspec-continue-change\u002FSKILL.md",[],[108,160,161,122,134,109,51,119,118,162,133,163],"continue","openspec continue change","next","progress",{"skillNo":165,"name":166,"nameZh":6,"description":167,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":103,"licenseFileUrl":6,"sourceHtmlUrl":168,"categories":169,"keywords":170,"publishedAt":54},"01M6G9HKT3WMSDBSKA7YM4MSSQ","openspec-archive-change","Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.","https:\u002F\u002Fgithub.com\u002Fricardoaevt\u002Fnexus-roms\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fopenspec-archive-change\u002FSKILL.md",[],[171,108,172,122,109,134,119,118,116,113],"openspec archive change","archive",{"skillNo":174,"name":175,"nameZh":6,"description":176,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":103,"licenseFileUrl":6,"sourceHtmlUrl":177,"categories":178,"keywords":179,"publishedAt":54},"01M6G9HHEG0RJK4E0YTVZZ6A8T","openspec-apply-change","Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.","https:\u002F\u002Fgithub.com\u002Fricardoaevt\u002Fnexus-roms\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fopenspec-apply-change\u002FSKILL.md",[],[108,122,180,181,121,135,160,47,119,118,116,109],"openspec apply change","implement"]