[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71GEC3S7F15CYREE3TNHJNH":3,"skill-same:01M71GEC3S7F15CYREE3TNHJNH":102},{"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":15,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":54,"repositoryHtmlUrl":55,"repositoryHomepageUrl":56,"ownerHtmlUrl":57,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":58,"install":59,"resources":71},"01M71GEC3S7F15CYREE3TNHJNH","simplify-codebase",null,"Simplification audit or authorized codebase simplification whose stated objective is to remove accidental complexity. Use for evidence-backed deletion or consolidation of dead code, duplicate state, redundant APIs or layers, ownerless abstractions, obsolete compatibility or design records, and over-engineering in any language; also use for 代码简化 or 熵回收. Do not use for general code review, onboarding, style-only refactoring, or performance tuning.","marshadgani\u002FArshad.AI","marshadgani","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F275367399?v=4","01M71G2BP4YMZ4AX5YY0QBHAZH","01M71G2BPPHHFRMHQAKJTZPGK4",1,"MIT","https:\u002F\u002Fgithub.com\u002Fmarshadgani\u002FArshad.AI\u002Fblob\u002Fclaude\u002Fai-personal-assistant-main\u002F.claude\u002Fskills\u002Farchify\u002Fsimplify-codebase\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fmarshadgani\u002FArshad.AI\u002Fblob\u002Fclaude\u002Fai-personal-assistant-main\u002F.claude\u002Fskills\u002Farchify\u002Fsimplify-codebase\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000007","代码审查","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"simplify codebase","codebase","simplify","use","deletion","only","design","true","general","records","code review","performance","remove","layers","for","consolidation","evidence","do","complexity","simplification","2026-11-10 10:12:30",false,"---\nname: simplify-codebase\ndescription: Simplification audit or authorized codebase simplification whose stated objective is to remove accidental complexity. Use for evidence-backed deletion or consolidation of dead code, duplicate state, redundant APIs or layers, ownerless abstractions, obsolete compatibility or design records, and over-engineering in any language; also use for 代码简化 or 熵回收. Do not use for general code review, onboarding, style-only refactoring, or performance tuning.\nmetadata:\n  internal: true\n---\n\n# Simplify Codebase\n\nReduce the number of concepts and obligations a codebase must keep coherent. Line-count reduction is supporting evidence, not the objective. A successful run may conclude that the inspected surface is already justified.\n\n## Select mode and scope\n\nFirst choose the authority mode:\n\n- **Survey** for simplification audit, investigation, or candidate-finding requests. Remain read-only and return ranked evidence.\n- **Change** for explicit simplify, remove, consolidate, refactor, or repository-documentation edit requests. Prove each cut, implement it within the authorized scope, and validate the surviving contract.\n\nThen choose the coverage scope:\n\n- **Focused** when the user names a subsystem, symbol, state machine, dependency, or suspected duplication. Cover that boundary thoroughly before expanding outward.\n- **Broad** when the request spans the repository or asks for multiple candidates. Partition the system and account for every in-scope domain.\n\nDeleting a reachable capability, supported interface, stored representation, or compatibility path is a product decision. Describe the consequence and obtain direction unless the user has already chosen it.\n\n## Establish the contract\n\n1. Read the repository's instructions, architecture and decision records, manifests, test guidance, and generated-file conventions.\n2. Inspect version-control state and preserve unrelated work. Identify vendored, generated, migration, fixture, and public-package surfaces before classifying them.\n3. Trace the runtime path from entrypoints through configuration, registration, dispatch, persistence, processes, and wire boundaries. Record public, dynamic, persisted, generated, and compatibility-sensitive contracts.\n4. In Change mode, discover the repository's real verification commands and capture a proportional baseline when feasible. A failing baseline narrows what the final checks can prove.\n\nPreserve authorization, trust-boundary validation, security isolation, accessibility essentials, data-loss prevention, stored-format compatibility, and cleanup that establishes quiescence. Treat changes to these protections as their own explicitly authorized objective, not an incidental simplification.\n\nThe contract map is complete when all in-scope entrypoints and authority boundaries are enumerated, each is traced far enough to name its owner and observable contract, and every uninspected or externally unknowable surface is recorded as a blind spot.\n\n## Cover the relevant surface\n\nFor every Broad engagement, and for Focused work involving dynamic architecture or dependency substitution, read [investigation.md](references\u002Finvestigation.md). Build a coverage map before ranking findings; the first plausible deletion must not end the survey.\n\nFor concurrency, cancellation, readiness, cleanup, defensive copies, validation, authorization, security isolation, accessibility, data-loss prevention, or cross-process data, also read [boundaries-and-lifecycle.md](references\u002Fboundaries-and-lifecycle.md).\n\nUse repository-native search, compiler and linter output, dependency metadata, and history as discovery instruments. Treat their findings as leads until runtime consumers and contracts have been examined.\n\n## Build a proof record\n\nFor every in-scope lead that reaches consumer-map evidence or could retire a meaningful contract, record:\n\n```text\nCandidate: the exact contract, representation, or layer to remove or merge\nBurden: the concepts, synchronization, publication, or testing cost it creates\nReachability: production, non-production, dynamic, external, and persisted consumers\nRationale: why it exists and whether that reason remains current\nCut: declarations, implementations, branches, artifacts, docs, and dependencies affected\nConsequence: observable capability or compatibility behavior surrendered\nConfidence \u002F risk: evidence strength, uncertainty, blast radius, and reversibility\nProof: the smallest check that would expose an incorrect cut\nNet effect: maintenance concepts removed minus replacement or migration machinery added\n```\n\nProve cut boundaries below file granularity when the candidate shares an artifact with surviving consumers. Account for candidate-exclusive selectors, members, fields, keys, registry entries, generated fragments, and fixtures without disturbing the surviving owners.\n\nKeep or downgrade the candidate when a real consumer exists, dynamic reachability remains unresolved, a current decision still owns the design, the change merely relocates complexity, the result is outside scope or retires no meaningful obligation, or the available check cannot distinguish success from accidental breakage.\n\nRank confidence separately from benefit. A high-value guess does not outrank a smaller proved cut.\n\nCandidate proof is complete when every qualifying lead is classified as ranked, rejected, or unresolved, and every unresolved lead names the fact required to decide it.\n\n## Decide and act\n\nIn Survey mode, stop after reporting the ranked evidence. Include important rejected candidates when the rejection teaches something or identifies a concrete missing fact.\n\nIn Change mode, read [execution-and-recovery.md](references\u002Fexecution-and-recovery.md) and select the strongest authorized cut. One ownership boundary is the default batch size, not a run limit: for an explicitly requested set of cuts, finish and validate each boundary before starting the next.\n\nIf the user requests a simplification proposal, local cleanup annotation, or design-record consolidation, or if a selected change invalidates an ADR, RFC, design note, or architectural inventory, read [decision-records.md](references\u002Fdecision-records.md). Do not turn an ordinary code audit into a repository-wide documentation purge.\n\nIf the user asks to combine findings from another branch, pull request, task, or agent run, read [integrating-findings.md](references\u002Fintegrating-findings.md). Preserve evidence, not finding counts.\n\n## Deliver the result\n\nFor a survey, report coverage, ranked proof records, rejected or unresolved high-value leads, and the next fact needed for each uncertainty.\n\nFor a change, complete the validation and operation receipt defined in [execution-and-recovery.md](references\u002Fexecution-and-recovery.md). Report each validation layer separately; a narrow green check does not establish broader runtime, deployment, or user acceptance.\n","# Simplify Codebase\n\nReduce the number of concepts and obligations a codebase must keep coherent. Line-count reduction is supporting evidence, not the objective. A successful run may conclude that the inspected surface is already justified.\n\n## Select mode and scope\n\nFirst choose the authority mode:\n\n- **Survey** for simplification audit, investigation, or candidate-finding requests. Remain read-only and return ranked evidence.\n- **Change** for explicit simplify, remove, consolidate, refactor, or repository-documentation edit requests. Prove each cut, implement it within the authorized scope, and validate the surviving contract.\n\nThen choose the coverage scope:\n\n- **Focused** when the user names a subsystem, symbol, state machine, dependency, or suspected duplication. Cover that boundary thoroughly before expanding outward.\n- **Broad** when the request spans the repository or asks for multiple candidates. Partition the system and account for every in-scope domain.\n\nDeleting a reachable capability, supported interface, stored representation, or compatibility path is a product decision. Describe the consequence and obtain direction unless the user has already chosen it.\n\n## Establish the contract\n\n1. Read the repository's instructions, architecture and decision records, manifests, test guidance, and generated-file conventions.\n2. Inspect version-control state and preserve unrelated work. Identify vendored, generated, migration, fixture, and public-package surfaces before classifying them.\n3. Trace the runtime path from entrypoints through configuration, registration, dispatch, persistence, processes, and wire boundaries. Record public, dynamic, persisted, generated, and compatibility-sensitive contracts.\n4. In Change mode, discover the repository's real verification commands and capture a proportional baseline when feasible. A failing baseline narrows what the final checks can prove.\n\nPreserve authorization, trust-boundary validation, security isolation, accessibility essentials, data-loss prevention, stored-format compatibility, and cleanup that establishes quiescence. Treat changes to these protections as their own explicitly authorized objective, not an incidental simplification.\n\nThe contract map is complete when all in-scope entrypoints and authority boundaries are enumerated, each is traced far enough to name its owner and observable contract, and every uninspected or externally unknowable surface is recorded as a blind spot.\n\n## Cover the relevant surface\n\nFor every Broad engagement, and for Focused work involving dynamic architecture or dependency substitution, read [investigation.md](references\u002Finvestigation.md). Build a coverage map before ranking findings; the first plausible deletion must not end the survey.\n\nFor concurrency, cancellation, readiness, cleanup, defensive copies, validation, authorization, security isolation, accessibility, data-loss prevention, or cross-process data, also read [boundaries-and-lifecycle.md](references\u002Fboundaries-and-lifecycle.md).\n\nUse repository-native search, compiler and linter output, dependency metadata, and history as discovery instruments. Treat their findings as leads until runtime consumers and contracts have been examined.\n\n## Build a proof record\n\nFor every in-scope lead that reaches consumer-map evidence or could retire a meaningful contract, record:\n\n```text\nCandidate: the exact contract, representation, or layer to remove or merge\nBurden: the concepts, synchronization, publication, or testing cost it creates\nReachability: production, non-production, dynamic, external, and persisted consumers\nRationale: why it exists and whether that reason remains current\nCut: declarations, implementations, branches, artifacts, docs, and dependencies affected\nConsequence: observable capability or compatibility behavior surrendered\nConfidence \u002F risk: evidence strength, uncertainty, blast radius, and reversibility\nProof: the smallest check that would expose an incorrect cut\nNet effect: maintenance concepts removed minus replacement or migration machinery added\n```\n\nProve cut boundaries below file granularity when the candidate shares an artifact with surviving consumers. Account for candidate-exclusive selectors, members, fields, keys, registry entries, generated fragments, and fixtures without disturbing the surviving owners.\n\nKeep or downgrade the candidate when a real consumer exists, dynamic reachability remains unresolved, a current decision still owns the design, the change merely relocates complexity, the result is outside scope or retires no meaningful obligation, or the available check cannot distinguish success from accidental breakage.\n\nRank confidence separately from benefit. A high-value guess does not outrank a smaller proved cut.\n\nCandidate proof is complete when every qualifying lead is classified as ranked, rejected, or unresolved, and every unresolved lead names the fact required to decide it.\n\n## Decide and act\n\nIn Survey mode, stop after reporting the ranked evidence. Include important rejected candidates when the rejection teaches something or identifies a concrete missing fact.\n\nIn Change mode, read [execution-and-recovery.md](references\u002Fexecution-and-recovery.md) and select the strongest authorized cut. One ownership boundary is the default batch size, not a run limit: for an explicitly requested set of cuts, finish and validate each boundary before starting the next.\n\nIf the user requests a simplification proposal, local cleanup annotation, or design-record consolidation, or if a selected change invalidates an ADR, RFC, design note, or architectural inventory, read [decision-records.md](references\u002Fdecision-records.md). Do not turn an ordinary code audit into a repository-wide documentation purge.\n\nIf the user asks to combine findings from another branch, pull request, task, or agent run, read [integrating-findings.md](references\u002Fintegrating-findings.md). Preserve evidence, not finding counts.\n\n## Deliver the result\n\nFor a survey, report coverage, ranked proof records, rejected or unresolved high-value leads, and the next fact needed for each uncertainty.\n\nFor a change, complete the validation and operation receipt defined in [execution-and-recovery.md](references\u002Fexecution-and-recovery.md). Report each validation layer separately; a narrow green check does not establish broader runtime, deployment, or user acceptance.\n",{"name":5,"metadata":49,"description":7},{"internal":50},true,"claude\u002Fai-personal-assistant-main","fb33f7f5b3a206eb019c788e3c48e91c02ccb1f9",".claude\u002Fskills\u002Farchify\u002Fsimplify-codebase",0,"https:\u002F\u002Fgithub.com\u002Fmarshadgani\u002FArshad.AI","https:\u002F\u002Farshad-ai-seven.vercel.app","https:\u002F\u002Fgithub.com\u002Fmarshadgani","2026-11-02 00:51:35",{"source":8,"skillName":5,"commands":60,"prompt":70,"zipAvailable":50},[61,64,67],{"tool":62,"command":63},"npx","npx skills add marshadgani\u002FArshad.AI --skill simplify-codebase",{"tool":65,"command":66},"bunx","bunx skills add marshadgani\u002FArshad.AI --skill simplify-codebase",{"tool":68,"command":69},"pnpm","pnpm dlx skills add marshadgani\u002FArshad.AI --skill simplify-codebase","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmarshadgani\u002FArshad.AI\u002Fblob\u002Fclaude\u002Fai-personal-assistant-main\u002F.claude\u002Fskills\u002Farchify\u002Fsimplify-codebase\u002FSKILL.md",[72,78,82,86,90,94,98],{"path":73,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":76,"sourceHtmlUrl":77},"agents\u002Fopenai.yaml","REFERENCE","参考文档",301,"https:\u002F\u002Fgithub.com\u002Fmarshadgani\u002FArshad.AI\u002Fblob\u002Fclaude\u002Fai-personal-assistant-main\u002F.claude\u002Fskills\u002Farchify\u002Fsimplify-codebase\u002Fagents\u002Fopenai.yaml",{"path":79,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":81,"sourceHtmlUrl":15},"LICENSE","许可证",1087,{"path":83,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":84,"sourceHtmlUrl":85},"references\u002Fboundaries-and-lifecycle.md",3651,"https:\u002F\u002Fgithub.com\u002Fmarshadgani\u002FArshad.AI\u002Fblob\u002Fclaude\u002Fai-personal-assistant-main\u002F.claude\u002Fskills\u002Farchify\u002Fsimplify-codebase\u002Freferences\u002Fboundaries-and-lifecycle.md",{"path":87,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":88,"sourceHtmlUrl":89},"references\u002Fdecision-records.md",3098,"https:\u002F\u002Fgithub.com\u002Fmarshadgani\u002FArshad.AI\u002Fblob\u002Fclaude\u002Fai-personal-assistant-main\u002F.claude\u002Fskills\u002Farchify\u002Fsimplify-codebase\u002Freferences\u002Fdecision-records.md",{"path":91,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":92,"sourceHtmlUrl":93},"references\u002Fexecution-and-recovery.md",4662,"https:\u002F\u002Fgithub.com\u002Fmarshadgani\u002FArshad.AI\u002Fblob\u002Fclaude\u002Fai-personal-assistant-main\u002F.claude\u002Fskills\u002Farchify\u002Fsimplify-codebase\u002Freferences\u002Fexecution-and-recovery.md",{"path":95,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":96,"sourceHtmlUrl":97},"references\u002Fintegrating-findings.md",1964,"https:\u002F\u002Fgithub.com\u002Fmarshadgani\u002FArshad.AI\u002Fblob\u002Fclaude\u002Fai-personal-assistant-main\u002F.claude\u002Fskills\u002Farchify\u002Fsimplify-codebase\u002Freferences\u002Fintegrating-findings.md",{"path":99,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":100,"sourceHtmlUrl":101},"references\u002Finvestigation.md",6374,"https:\u002F\u002Fgithub.com\u002Fmarshadgani\u002FArshad.AI\u002Fblob\u002Fclaude\u002Fai-personal-assistant-main\u002F.claude\u002Fskills\u002Farchify\u002Fsimplify-codebase\u002Freferences\u002Finvestigation.md",[103,135,160,191,221,245],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":107,"licenseFileUrl":108,"sourceHtmlUrl":109,"categories":110,"keywords":117,"publishedAt":134},"01M71MVWH15PQRS9KT3J24D7WV","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmarshadgani\u002FArshad.AI\u002Fblob\u002Fclaude\u002Fai-personal-assistant-main\u002F.claude\u002Fskills\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmarshadgani\u002FArshad.AI\u002Fblob\u002Fclaude\u002Fai-personal-assistant-main\u002F.claude\u002Fskills\u002Fwebapp-testing\u002FSKILL.md",[111,114],{"categoryNo":112,"categoryName":113,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":115,"categoryName":116,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[118,119,120,38,121,122,123,124,125,126,127,128,129,130,131,132,133],"webapp","testing","webapp testing","applications","local","frontend","debugging","toolkit","logs","browser","with","playwright","web","behavior","ui","screenshots","2026-11-10 10:56:23",{"skillNo":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":107,"licenseFileUrl":139,"sourceHtmlUrl":140,"categories":141,"keywords":143,"publishedAt":134},"01M71MVMAZ1J606SGA4JPHRDAZ","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","https:\u002F\u002Fgithub.com\u002Fmarshadgani\u002FArshad.AI\u002Fblob\u002Fclaude\u002Fai-personal-assistant-main\u002F.claude\u002Fskills\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmarshadgani\u002FArshad.AI\u002Fblob\u002Fclaude\u002Fai-personal-assistant-main\u002F.claude\u002Fskills\u002Fweb-artifacts-builder\u002FSKILL.md",[142],{"categoryNo":115,"categoryName":116,"taxonomyType":21,"taxonomyTypeDesc":22},[144,145,146,130,147,148,149,38,150,151,123,152,27,153,154,155,156,157,158,159],"builder","artifacts builder","artifacts","web artifacts builder","single-file","css","Tailwind","ui components","single","file","components","react","multi","state","routing","state management",{"skillNo":161,"name":162,"nameZh":6,"description":163,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":164,"sourceHtmlUrl":165,"categories":166,"keywords":175,"publishedAt":134},"01M71MSTFAEYT9J9GA587SP3RB","ui-styling","Create beautiful, accessible user interfaces with shadcn\u002Fui components (built on Radix UI + Tailwind), Tailwind CSS utility-first styling, and canvas-based visual designs. Use when building user interfaces, implementing design systems, creating responsive layouts, adding accessible components (dialogs, dropdowns, forms, tables), customizing themes and colors, implementing dark mode, generating visual designs and posters, or establishing consistent styling patterns across applications.","https:\u002F\u002Fgithub.com\u002Fmarshadgani\u002FArshad.AI\u002Fblob\u002Fclaude\u002Fai-personal-assistant-main\u002F.claude\u002Fskills\u002Fui-ux-pro-max\u002Fui-styling\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmarshadgani\u002FArshad.AI\u002Fblob\u002Fclaude\u002Fai-personal-assistant-main\u002F.claude\u002Fskills\u002Fui-ux-pro-max\u002Fui-styling\u002FSKILL.md",[167,170],{"categoryNo":168,"categoryName":169,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":171,"categoryName":172,"taxonomyType":173,"taxonomyTypeDesc":174},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[176,177,132,149,150,178,179,180,30,181,182,183,184,154,185,186,187,188,189,190],"ui styling","styling","mode","canvas","implementing","themes","utility","design systems","when","across","create","component","layout","forms","patterns",{"skillNo":192,"name":30,"nameZh":6,"description":193,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":194,"categories":195,"keywords":204,"publishedAt":134},"01M71MSM72HXKQRCY5D45WYPNP","Comprehensive design skill: brand identity, design tokens, UI styling, logo generation (55 styles, Gemini, Atlas Cloud, or MuAPI AI), corporate identity program (50 deliverables, CIP mockups), HTML presentations (Chart.js), banner design (22 styles, social\u002Fads\u002Fweb\u002Fprint), icon design (15 styles, SVG, Gemini 3.1 Pro), social photos (HTML→screenshot, multi-platform). Actions: design logo, create CIP, generate mockups, build slides, design banner, generate icon, create social photos, social media images, brand identity, design system. Platforms: Facebook, Twitter, LinkedIn, YouTube, Instagram, Pinterest, TikTok, Threads, Google Ads.","https:\u002F\u002Fgithub.com\u002Fmarshadgani\u002FArshad.AI\u002Fblob\u002Fclaude\u002Fai-personal-assistant-main\u002F.claude\u002Fskills\u002Fui-ux-pro-max\u002Fdesign\u002FSKILL.md",[196,199,200,203],{"categoryNo":197,"categoryName":198,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000003","演示文稿",{"categoryNo":168,"categoryName":169,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":201,"categoryName":202,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":171,"categoryName":172,"taxonomyType":173,"taxonomyTypeDesc":174},[30,205,206,207,176,208,209,210,211,186,212,213,214,215,216,217,218,219,132,220],"Media","tiktok","actions","logo","logo generation","chart","multi-platform","ads","youtube","generate","presentations","google","atlas cloud","screenshot","muapi","identity",{"skillNo":222,"name":223,"nameZh":6,"description":224,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":225,"categories":226,"keywords":229,"publishedAt":134},"01M71MSH9T7S227MN2YSYB2EP5","design-system","Token architecture, component specifications, and slide generation. Three-layer tokens (primitive→semantic→component), CSS variables, spacing\u002Ftypography scales, component specs, strategic slide creation. Use for design tokens, systematic design, brand-compliant presentations.","https:\u002F\u002Fgithub.com\u002Fmarshadgani\u002FArshad.AI\u002Fblob\u002Fclaude\u002Fai-personal-assistant-main\u002F.claude\u002Fskills\u002Fui-ux-pro-max\u002Fdesign-system\u002FSKILL.md",[227,228],{"categoryNo":168,"categoryName":169,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":171,"categoryName":172,"taxonomyType":173,"taxonomyTypeDesc":174},[30,230,231,149,232,233,234,235,187,215,236,237,238,239,240,241,242,38,243,244],"design system","system","css variables","creation","Variables","architecture","systematic","token","spacing","layer","typography","brand","three","tokens","slide generation",{"skillNo":246,"name":247,"nameZh":6,"description":248,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":249,"categories":250,"keywords":253,"publishedAt":134},"01M71MSCFZ1HFMNBDMAFXDZV92","banner-design","Design banners for social media, ads, website heroes, creative assets, and print. Multiple art direction options with optional generated or supplied visuals. Actions: design, create, generate banner. Platforms: Facebook, Twitter\u002FX, LinkedIn, YouTube, Instagram, Google Display, website hero, print. Styles: minimalist, gradient, bold typography, photo-based, illustrated, geometric, retro, glassmorphism, 3D, neon, duotone, editorial, collage.","https:\u002F\u002Fgithub.com\u002Fmarshadgani\u002FArshad.AI\u002Fblob\u002Fclaude\u002Fai-personal-assistant-main\u002F.claude\u002Fskills\u002Fui-ux-pro-max\u002Fbanner-design\u002FSKILL.md",[251,252],{"categoryNo":168,"categoryName":169,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":171,"categoryName":172,"taxonomyType":173,"taxonomyTypeDesc":174},[30,254,255,205,256,257,258,207,259,260,261,262,263,264,186,212,213,214,265,266],"banner","banner design","3D","direction","neon","Art","social","generated","hero","dimensions","display","options","website"]