[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skills:stats":3,"skills:pro6":8,"skills:sce6":55,"skills:creators9":100,"skills:all:stars:740:":195},{"skillCount":4,"professionCount":5,"scenarioCount":6,"creatorCount":7},482556,11,7,5953,[9,20,27,34,41,48],{"categoryNo":10,"taxonomyType":11,"taxonomyTypeDesc":12,"categoryName":13,"categoryNameEn":14,"description":15,"level":16,"skillCount":17,"parentNo":18,"parentName":18,"children":19},"01JBSEEDCAT000000000000030","PROFESSION","适用职业","开发工程师","Software Engineer","从事软件编码、测试与运维的工程师",1,13341,null,[],{"categoryNo":21,"taxonomyType":11,"taxonomyTypeDesc":12,"categoryName":22,"categoryNameEn":23,"description":24,"level":16,"skillCount":25,"parentNo":18,"parentName":18,"children":26},"01JBSEEDCAT000000000000032","设计师","Designer","视觉、交互与品牌设计人员",7902,[],{"categoryNo":28,"taxonomyType":11,"taxonomyTypeDesc":12,"categoryName":29,"categoryNameEn":30,"description":31,"level":16,"skillCount":32,"parentNo":18,"parentName":18,"children":33},"01JBSEEDCAT000000000000033","数据分析师","Data Analyst","数据分析、报表与商业智能人员",5005,[],{"categoryNo":35,"taxonomyType":11,"taxonomyTypeDesc":12,"categoryName":36,"categoryNameEn":37,"description":38,"level":16,"skillCount":39,"parentNo":18,"parentName":18,"children":40},"01JBSEEDCAT000000000000036","内容创作者","Content Creator","作者、编辑与自媒体创作者",3978,[],{"categoryNo":42,"taxonomyType":11,"taxonomyTypeDesc":12,"categoryName":43,"categoryNameEn":44,"description":45,"level":16,"skillCount":46,"parentNo":18,"parentName":18,"children":47},"01JBSEEDCAT000000000000035","市场营销","Marketer","市场推广、增长与品牌运营人员",3454,[],{"categoryNo":49,"taxonomyType":11,"taxonomyTypeDesc":12,"categoryName":50,"categoryNameEn":51,"description":52,"level":16,"skillCount":53,"parentNo":18,"parentName":18,"children":54},"01JBSEEDCAT000000000000037","律师与法务","Legal","合同、合规与法律事务人员",3337,[],[56,65,72,79,86,93],{"categoryNo":57,"taxonomyType":58,"taxonomyTypeDesc":59,"categoryName":60,"categoryNameEn":61,"description":62,"level":16,"skillCount":63,"parentNo":18,"parentName":18,"children":64},"01JBSEEDCAT000000000000022","SCENARIO","使用场景","智能体与自动化","Agents & Automation","Skill、MCP、智能体与工作流自动化",39675,[],{"categoryNo":66,"taxonomyType":58,"taxonomyTypeDesc":59,"categoryName":67,"categoryNameEn":68,"description":69,"level":16,"skillCount":70,"parentNo":18,"parentName":18,"children":71},"01JBSEEDCAT000000000000006","软件开发","Software Development","编码、测试、部署等软件研发任务",26798,[],{"categoryNo":73,"taxonomyType":58,"taxonomyTypeDesc":59,"categoryName":74,"categoryNameEn":75,"description":76,"level":16,"skillCount":77,"parentNo":18,"parentName":18,"children":78},"01JBSEEDCAT000000000000014","设计创意","Design & Creative","视觉设计、品牌与多媒体创作",13847,[],{"categoryNo":80,"taxonomyType":58,"taxonomyTypeDesc":59,"categoryName":81,"categoryNameEn":82,"description":83,"level":16,"skillCount":84,"parentNo":18,"parentName":18,"children":85},"01JBSEEDCAT000000000000001","办公效率","Office Productivity","日常办公文档、表格、演示与沟通类任务",6403,[],{"categoryNo":87,"taxonomyType":58,"taxonomyTypeDesc":59,"categoryName":88,"categoryNameEn":89,"description":90,"level":16,"skillCount":91,"parentNo":18,"parentName":18,"children":92},"01JBSEEDCAT000000000000017","内容创作","Content Creation","写作、文案与营销内容生产",6063,[],{"categoryNo":94,"taxonomyType":58,"taxonomyTypeDesc":59,"categoryName":95,"categoryNameEn":96,"description":97,"level":16,"skillCount":98,"parentNo":18,"parentName":18,"children":99},"01JBSEEDCAT000000000000020","研究与学习","Research & Learning","资料检索、知识整理与学习辅导",5574,[],{"records":101,"total":7,"current":16,"size":194},[102,114,123,132,142,152,162,172,182],{"accountNo":103,"login":104,"displayName":105,"avatarUrl":106,"accountType":107,"accountTypeDesc":108,"profileDescription":109,"skillCount":110,"repoCount":111,"professionCount":5,"scenarioCount":6,"totalStars":112,"updatedAt":113},"01M698VYDXZ6JW5WH3CRV650R8","microsoft","Microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","ORGANIZATION","组织","Open source projects and samples from Microsoft",4300,236,832929,"2026-11-15 04:18:35",{"accountNo":115,"login":116,"displayName":116,"avatarUrl":117,"accountType":107,"accountTypeDesc":108,"profileDescription":118,"skillCount":119,"repoCount":120,"professionCount":6,"scenarioCount":6,"totalStars":121,"updatedAt":122},"01M698P3FSAZ6B4R928ZF19KPT","openclaw","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F252820863?v=4","Your personal, open source AI assistant.",369,32,437811,"2026-11-15 03:04:02",{"accountNo":124,"login":125,"displayName":126,"avatarUrl":127,"accountType":107,"accountTypeDesc":108,"profileDescription":18,"skillCount":128,"repoCount":129,"professionCount":5,"scenarioCount":6,"totalStars":130,"updatedAt":131},"01M697XGDPXJAVQ8391V2BCYTE","anthropics","Anthropic","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F76263028?v=4",716,18,427323,"2026-11-15 05:52:49",{"accountNo":133,"login":134,"displayName":135,"avatarUrl":136,"accountType":107,"accountTypeDesc":108,"profileDescription":18,"skillCount":137,"repoCount":138,"professionCount":6,"scenarioCount":139,"totalStars":140,"updatedAt":141},"01M6AC29YGCR4S2NTJFV0G8B81","openai","OpenAI","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F14957082?v=4",177,23,6,344400,"2026-11-15 03:07:28",{"accountNo":143,"login":144,"displayName":145,"avatarUrl":146,"accountType":107,"accountTypeDesc":108,"profileDescription":18,"skillCount":147,"repoCount":148,"professionCount":149,"scenarioCount":6,"totalStars":150,"updatedAt":151},"01M6AC83E6K4FDKK7HZ8WNMQKE","apache","The Apache Software Foundation","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F47359?v=4",440,76,8,298252,"2026-11-15 04:11:16",{"accountNo":153,"login":154,"displayName":155,"avatarUrl":156,"accountType":107,"accountTypeDesc":108,"profileDescription":157,"skillCount":158,"repoCount":159,"professionCount":5,"scenarioCount":6,"totalStars":160,"updatedAt":161},"01M6AC83DS133TPXFSP1DHNCC6","github","GitHub","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F9919?v=4","How people build software.",1022,30,278314,"2026-11-15 06:45:15",{"accountNo":163,"login":164,"displayName":165,"avatarUrl":166,"accountType":107,"accountTypeDesc":108,"profileDescription":167,"skillCount":168,"repoCount":169,"professionCount":5,"scenarioCount":6,"totalStars":170,"updatedAt":171},"01M698VYEFDM0VJBZDYYJ2T83S","google","Google","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1342004?v=4","Google ❤️ Open Source",542,50,243804,"2026-11-15 03:00:30",{"accountNo":173,"login":174,"displayName":175,"avatarUrl":176,"accountType":107,"accountTypeDesc":108,"profileDescription":18,"skillCount":177,"repoCount":178,"professionCount":179,"scenarioCount":6,"totalStars":180,"updatedAt":181},"01M6AC83EPDGBFN19MWYRREJD0","Significant-Gravitas","AutoGPT","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F130738209?v=4",87,2,10,188029,"2026-11-15 06:21:09",{"accountNo":183,"login":184,"displayName":185,"avatarUrl":186,"accountType":187,"accountTypeDesc":188,"profileDescription":189,"skillCount":190,"repoCount":191,"professionCount":139,"scenarioCount":6,"totalStars":192,"updatedAt":193},"01M6DJCCDDG53MTYYRTXAXFG17","garrytan","Garry Tan","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F19957?v=4","USER","个人作者","Writes software, dreams. ",340,3,175019,"2026-11-15 03:57:03",9,{"records":196,"total":4,"current":573,"size":129},[197,236,262,286,308,331,354,372,390,423,439,460,477,491,508,526,546,558],{"skillNo":198,"name":199,"nameZh":18,"description":200,"descriptionZh":18,"repositoryFullName":201,"ownerLogin":202,"ownerAvatarUrl":203,"ownerAccountNo":204,"ownerDisplayName":205,"repositoryNo":206,"starsCount":207,"licenseSpdxId":208,"licenseFileUrl":18,"sourceHtmlUrl":209,"categories":210,"keywords":212,"publishedAt":235},"01M6JVZE3B318MAC7MKZNRQFCE","hicks-law-defaults","Use this skill when the question is what to *pre-select* in a list of options — radio groups, dropdowns, configuration UIs, plan pickers, sign-up flows, settings. A strong default is the highest-leverage Hick's Law mitigation: most users accept the default, paying almost no decision cost. Trigger when picking what's selected on first load, when stakeholders argue \"shouldn't we let the user choose?\", when designing wizards or onboarding, or when a UI has many options but most users want the same one. Sub-aspect of `hicks-law`; read that first if you haven't already.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Fcognition-and-learnability-principles\u002Fskills\u002Fhicks-law-defaults\u002FSKILL.md",[211],{"categoryNo":49,"categoryName":50,"taxonomyType":11,"taxonomyTypeDesc":12},[213,214,215,216,217,218,219,220,221,222,223,224,225,226,227,228,229,230,231,232,233,234],"hicks law defaults","hicks law","ui","plan","select","choose","decision","question","read","list","use","up","default","but","options","leverage","trigger","users","flows","you","load","when","2026-11-10 10:12:30",{"skillNo":237,"name":238,"nameZh":18,"description":239,"descriptionZh":18,"repositoryFullName":201,"ownerLogin":202,"ownerAvatarUrl":203,"ownerAccountNo":204,"ownerDisplayName":205,"repositoryNo":206,"starsCount":207,"licenseSpdxId":208,"licenseFileUrl":18,"sourceHtmlUrl":240,"categories":241,"keywords":242,"publishedAt":235},"01M6JVZ8YR6DW54HBTKKZ4Y81P","consistency","Apply the principle of Consistency — making similar things look and behave similarly so users can transfer learning across the interface. Use when designing component libraries, defining naming conventions, choosing whether to invent or borrow patterns, auditing across surfaces (web, mobile, email, support docs), or evaluating whether two features should share or diverge in their interaction model. Strong consistency reduces cognitive load and learnability cost; aggressive consistency can flatten meaningful differences. There are four kinds — aesthetic, functional, internal, external — each with different applications.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Fcognition-and-learnability-principles\u002Fskills\u002Fconsistency\u002FSKILL.md",[],[238,243,244,245,246,247,248,249,250,251,252,253,254,255,256,257,258,259,260,261,234],"support","component","libraries","email","applications","learning","model","mobile","aesthetic","diverge","surfaces","patterns","behave","across","interaction","functional","interface","things","features",{"skillNo":263,"name":264,"nameZh":18,"description":265,"descriptionZh":18,"repositoryFullName":201,"ownerLogin":202,"ownerAvatarUrl":203,"ownerAccountNo":204,"ownerDisplayName":205,"repositoryNo":206,"starsCount":207,"licenseSpdxId":208,"licenseFileUrl":18,"sourceHtmlUrl":266,"categories":267,"keywords":272,"publishedAt":235},"01M6JVZ23YBRCZ3577X2XDGZZF","consistency-internal","Apply internal consistency — making your product coherent with itself across all surfaces, components, and flows. Use when designing or auditing component libraries, defining design tokens, settling cross-team naming conventions, planning a design-system rollout, integrating acquired or legacy code, or evaluating whether two features should share or diverge in their interaction model. Internal consistency is enforced through design systems, shared vocabularies, and process discipline; it erodes through hand-off losses, sprint-driven shortcuts, and team boundaries that don't coordinate.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Fcognition-and-learnability-principles\u002Fskills\u002Fconsistency-internal\u002FSKILL.md",[268,271],{"categoryNo":269,"categoryName":270,"taxonomyType":58,"taxonomyTypeDesc":59},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":21,"categoryName":22,"taxonomyType":11,"taxonomyTypeDesc":12},[238,273,274,275,244,245,276,277,278,279,249,280,281,282,256,283,257,284,231,285,234],"consistency internal","design","components","code","design systems","product","team","rollout","discipline","coordinate","shared","sprint","hand",{"skillNo":287,"name":288,"nameZh":18,"description":289,"descriptionZh":18,"repositoryFullName":201,"ownerLogin":202,"ownerAvatarUrl":203,"ownerAccountNo":204,"ownerDisplayName":205,"repositoryNo":206,"starsCount":207,"licenseSpdxId":208,"licenseFileUrl":18,"sourceHtmlUrl":290,"categories":291,"keywords":292,"publishedAt":235},"01M6JVYW0SJZ47SBAAR9MHFSCZ","consistency-external","Apply external consistency — honoring conventions from outside your product (platform conventions, category conventions, established interaction patterns) so users can transfer their learning into your product. Use when designing for a specific platform (iOS, Android, web), entering an established product category (calendar, email, file manager), choosing icons or gestures, or deciding when to follow vs. lead a convention. External consistency reduces the learning cost for new users; deviating from it requires both a strong reason and explicit framing.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Fcognition-and-learnability-principles\u002Fskills\u002Fconsistency-external\u002FSKILL.md",[],[238,293,294,295,296,278,297,246,248,223,298,299,254,300,257,230,301,302,303,304,305,234,306,307],"consistency external","android","gestures","icons","file","cost","calendar","platform","can","file manager","manager","for","apply","lead","new",{"skillNo":309,"name":310,"nameZh":18,"description":311,"descriptionZh":18,"repositoryFullName":201,"ownerLogin":202,"ownerAvatarUrl":203,"ownerAccountNo":204,"ownerDisplayName":205,"repositoryNo":206,"starsCount":207,"licenseSpdxId":208,"licenseFileUrl":18,"sourceHtmlUrl":312,"categories":313,"keywords":314,"publishedAt":235},"01M6JVYNTNKQ560JD9AQBN48CF","cognition-router","Use this skill whenever a design task involves cognition, mental models, learnability, complexity reduction, defaults, memory, scanning, or comprehension — regardless of framework or platform. Trigger when the user is designing forms, settings, onboarding, dashboards with many widgets, complex tables, navigation IA, search experiences, or any flow that has many options or asks the user to learn something new. Trigger when the user mentions \"too complex,\" \"too many options,\" \"users keep getting confused,\" defaults, labels, copy, mental models, progressive disclosure, autocomplete, or ergonomics. Routes the model to the right cognition principle in this plugin.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Fcognition-and-learnability-principles\u002Fskills\u002Fcognition-router\u002FSKILL.md",[],[315,316,317,274,318,319,320,321,322,323,249,324,325,326,227,327,300,328,329,330,234,307],"router","cognition","cognition router","memory","learn","framework","search","flow","dashboards","scanning","complexity","forms","widgets","ergonomics","tables","labels",{"skillNo":332,"name":333,"nameZh":18,"description":334,"descriptionZh":18,"repositoryFullName":201,"ownerLogin":202,"ownerAvatarUrl":203,"ownerAccountNo":204,"ownerDisplayName":205,"repositoryNo":206,"starsCount":207,"licenseSpdxId":208,"licenseFileUrl":18,"sourceHtmlUrl":335,"categories":336,"keywords":340,"publishedAt":235},"01M6JVYFHRJT50Z75P83670KXD","chunking","Use this skill whenever the user must hold a sequence of items in working memory — phone numbers, OTP codes, account IDs, address strings, multi-step instructions, long forms, navigation menus with many items. Trigger when designing OTP \u002F verification UIs, formatting numeric strings, breaking long forms into sections, grouping nav items, or reviewing surfaces that \"have too many things at once.\" Chunking is one of the foundational principles in 'Universal Principles of Design' (Lidwell, Holden, Butler 2003), grounded in Miller's classic working-memory research.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Fcognition-and-learnability-principles\u002Fskills\u002Fchunking\u002FSKILL.md",[337],{"categoryNo":338,"categoryName":339,"taxonomyType":58,"taxonomyTypeDesc":59},"01JBSEEDCAT000000000000021","资料检索与研究",[333,274,318,341,342,343,253,344,345,326,346,347,229,348,349,350,351,352,260,353,234],"verification","ids","miller","phone","grouping","formatting","butler","otp","long","codes","strings","at","sequence",{"skillNo":355,"name":356,"nameZh":18,"description":357,"descriptionZh":18,"repositoryFullName":201,"ownerLogin":202,"ownerAvatarUrl":203,"ownerAccountNo":204,"ownerDisplayName":205,"repositoryNo":206,"starsCount":207,"licenseSpdxId":208,"licenseFileUrl":18,"sourceHtmlUrl":358,"categories":359,"keywords":360,"publishedAt":235},"01M6JVYB0ARY6AVH4TSDTYCF0E","chunking-numeric-and-otp","Use this skill when designing inputs or displays for numeric strings — phone numbers, OTP \u002F verification codes, credit card numbers, account IDs, license keys, currency, dates, social security numbers. Trigger when picking a format for displaying numbers, designing OTP entry UIs, or formatting identifiers in tables and receipts. Sub-aspect of `chunking`; read that first.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Fcognition-and-learnability-principles\u002Fskills\u002Fchunking-numeric-and-otp\u002FSKILL.md",[],[333,348,361,362,341,363,342,364,365,366,221,223,344,367,346,368,229,369,350,329,351,370,304,371,234],"chunking numeric and otp","security","license","first","receipts","format","social","currency","card","keys","dates",{"skillNo":373,"name":374,"nameZh":18,"description":375,"descriptionZh":18,"repositoryFullName":201,"ownerLogin":202,"ownerAvatarUrl":203,"ownerAccountNo":204,"ownerDisplayName":205,"repositoryNo":206,"starsCount":207,"licenseSpdxId":208,"licenseFileUrl":18,"sourceHtmlUrl":376,"categories":377,"keywords":378,"publishedAt":235},"01M6JVY6JS4AP811T3PZN6DSJN","chunking-form-grouping","Use this skill when designing or fixing long forms that ask the user for many fields — sign-up flows, profile setup, settings panels, checkout, intake forms, applications. Trigger when forms exceed ~6 fields, when users complain forms are \"too long,\" when seeing high mid-form drop-off, or when picking how to break a form into sections. Sub-aspect of `chunking`; read that first.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Fcognition-and-learnability-principles\u002Fskills\u002Fchunking-form-grouping\u002FSKILL.md",[],[345,333,379,380,381,247,382,383,221,224,326,384,229,385,386,387,231,388,304,389,234],"form","chunking form grouping","intake","how","ask","drop","panels","how to","checkout","too long","break",{"skillNo":391,"name":392,"nameZh":18,"description":393,"descriptionZh":18,"repositoryFullName":201,"ownerLogin":202,"ownerAvatarUrl":203,"ownerAccountNo":204,"ownerDisplayName":205,"repositoryNo":206,"starsCount":207,"licenseSpdxId":208,"licenseFileUrl":18,"sourceHtmlUrl":394,"categories":395,"keywords":400,"publishedAt":235},"01M6JVY06ZWXPPTTKRD435S8HG","80-20-rule","Use this skill whenever the design has many features, controls, or content elements and decisions about which to prioritize matter — feature roadmaps, redesign scoping, IA decisions, dashboard design, settings page audits, marketing content prioritization, or any design with many candidates competing for attention. Trigger when the user asks \"what should we focus on?\", \"should we add another feature?\", \"what can we cut?\", or when reviewing a UI cluttered with rarely-used controls. The 80\u002F20 rule (Pareto principle) is one of the foundational principles in 'Universal Principles of Design' (Lidwell, Holden, Butler 2003) and one of the most quoted across design, business, and engineering.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Fcognition-and-learnability-principles\u002Fskills\u002F80-20-rule\u002FSKILL.md",[396,399],{"categoryNo":397,"categoryName":398,"taxonomyType":58,"taxonomyTypeDesc":59},"01JBSEEDCAT000000000000013","分析与可视化",{"categoryNo":28,"categoryName":29,"taxonomyType":11,"taxonomyTypeDesc":12},[401,402,274,403,215,404,405,406,407,408,409,410,411,223,412,413,256,414,415,347,416,417,418,419,420,421,422,304,261],"rule","80 20 rule","dashboard","engineering","prioritization","prioritize","marketing","redesign","decisions","settings","scoping","dashboard design","focus","attention","feature","cut","ia","add","controls","principles","about","which",{"skillNo":424,"name":425,"nameZh":18,"description":426,"descriptionZh":18,"repositoryFullName":201,"ownerLogin":202,"ownerAvatarUrl":203,"ownerAccountNo":204,"ownerDisplayName":205,"repositoryNo":206,"starsCount":207,"licenseSpdxId":208,"licenseFileUrl":18,"sourceHtmlUrl":427,"categories":428,"keywords":429,"publishedAt":235},"01M6JVXTFACBNQK196BXG8AHTB","80-20-redesign-targeting","Use this skill when scoping a redesign or refactor — choosing which existing surfaces deserve full attention and which can be left mostly alone. Trigger when the user asks \"where should we focus our redesign?\", \"do we need to redo all of this?\", or when planning incremental design improvements with limited capacity. Sub-aspect of `80-20-rule`; read that first.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Fcognition-and-learnability-principles\u002Fskills\u002F80-20-redesign-targeting\u002FSKILL.md",[],[408,430,431,274,432,433,434,221,411,223,253,435,413,414,436,229,437,422,301,438,234],"targeting","80 20 redesign targeting","capacity","planning","refactor","do","full","with","Existing",{"skillNo":440,"name":441,"nameZh":18,"description":442,"descriptionZh":18,"repositoryFullName":201,"ownerLogin":202,"ownerAvatarUrl":203,"ownerAccountNo":204,"ownerDisplayName":205,"repositoryNo":206,"starsCount":207,"licenseSpdxId":208,"licenseFileUrl":18,"sourceHtmlUrl":443,"categories":444,"keywords":448,"publishedAt":235},"01M6JVXP5BTHYVFE3JWW99ZFC3","80-20-feature-prioritization","Use this skill when scoping a roadmap, prioritizing features, planning an MVP, or deciding what to ship and what to defer. Trigger when the user asks \"what should we build next?\", \"is this feature worth it?\", \"should we ship feature X?\", or when reviewing a feature backlog. Sub-aspect of `80-20-rule`; read that first.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Fcognition-and-learnability-principles\u002Fskills\u002F80-20-feature-prioritization\u002FSKILL.md",[445],{"categoryNo":446,"categoryName":447,"taxonomyType":11,"taxonomyTypeDesc":12},"01JBSEEDCAT000000000000031","产品经理",[405,415,449,450,433,364,451,221,452,411,223,453,454,455,456,229,401,457,458,261,459,234],"feature prioritization","80 20 feature prioritization","ship","user","roadmap","build","next","backlog","mvp","it","ship feature",{"skillNo":461,"name":462,"nameZh":18,"description":463,"descriptionZh":18,"repositoryFullName":201,"ownerLogin":202,"ownerAvatarUrl":203,"ownerAccountNo":204,"ownerDisplayName":205,"repositoryNo":206,"starsCount":207,"licenseSpdxId":208,"licenseFileUrl":18,"sourceHtmlUrl":464,"categories":465,"keywords":467,"publishedAt":235},"01M6JVXFQ1YQ33VMHTD99B11W8","wabi-sabi","Apply the principle of Wabi-Sabi — the aesthetic embrace of imperfection, impermanence, and naturalness. Use when designing for warmth and authenticity, creating spaces that feel lived-in rather than sterile, choosing handcrafted-feeling materials over machined perfection, or evaluating whether a design feels too polished and impersonal. Wabi-sabi resists the digital-design tendency toward pixel-perfect uniformity in favor of subtle asymmetry, organic textures, and the visible mark of process. Used appropriately, it produces designs that feel human; used reflexively, it produces fake-looking sloppiness.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Faesthetics-and-emotion-principles\u002Fskills\u002Fwabi-sabi\u002FSKILL.md",[466],{"categoryNo":269,"categoryName":270,"taxonomyType":58,"taxonomyTypeDesc":59},[468,274,469,223,251,470,471,472,458,473,474,475,304,476,305,234],"wabi sabi","process","pixel","human","organic","authenticity","mark","spaces","materials",{"skillNo":478,"name":479,"nameZh":18,"description":480,"descriptionZh":18,"repositoryFullName":201,"ownerLogin":202,"ownerAvatarUrl":203,"ownerAccountNo":204,"ownerDisplayName":205,"repositoryNo":206,"starsCount":207,"licenseSpdxId":208,"licenseFileUrl":18,"sourceHtmlUrl":481,"categories":482,"keywords":483,"publishedAt":235},"01M6JVXASJP360ZCVV209C7QFW","wabi-sabi-restraint","Apply wabi-sabi restraint — the discipline of leaving things out, of resisting decoration, of letting empty space and silence do design work. Use when designing reading-focused interfaces, paring back accumulated clutter, choosing between decoration and absence, or evaluating whether each element earns its place. Restraint is the often-overlooked half of wabi-sabi: the imperfection side gets attention, but the principle is equally about modesty and the elegance of what's not there.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Faesthetics-and-emotion-principles\u002Fskills\u002Fwabi-sabi-restraint\u002FSKILL.md",[],[484,468,274,485,223,281,435,486,226,487,414,488,421,489,260,305,234,490],"wabi sabi restraint","work","back","empty","element","reading","space",{"skillNo":492,"name":493,"nameZh":18,"description":494,"descriptionZh":18,"repositoryFullName":201,"ownerLogin":202,"ownerAvatarUrl":203,"ownerAccountNo":204,"ownerDisplayName":205,"repositoryNo":206,"starsCount":207,"licenseSpdxId":208,"licenseFileUrl":18,"sourceHtmlUrl":495,"categories":496,"keywords":497,"publishedAt":235},"01M6JVX5WPZQABNVYEAY87NZ0S","wabi-sabi-imperfection","Design intentional imperfection that reads as warmth — subtle asymmetry, hand-drawn elements, organic textures, intentional irregularities. Use when adding human warmth to a digital design, distinguishing from competitors with uniform design systems, designing for personal or creative contexts. The skill is making imperfection look intentional and refined rather than sloppy or broken; the line between \"designed warmth\" and \"looks unfinished\" is narrow.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Faesthetics-and-emotion-principles\u002Fskills\u002Fwabi-sabi-imperfection\u002FSKILL.md",[],[498,468,274,499,277,500,501,223,502,503,471,472,504,505,506,507,437,285,304,234],"wabi sabi imperfection","personal","competitors","broken","creative","look","elements","systems","as","line",{"skillNo":509,"name":510,"nameZh":18,"description":511,"descriptionZh":18,"repositoryFullName":201,"ownerLogin":202,"ownerAvatarUrl":203,"ownerAccountNo":204,"ownerDisplayName":205,"repositoryNo":206,"starsCount":207,"licenseSpdxId":208,"licenseFileUrl":18,"sourceHtmlUrl":512,"categories":513,"keywords":514,"publishedAt":235},"01M6JVX01MQVP58D5ZT4CEG6DZ","immersion","Apply the principle of Immersion — designing for sustained focus and engagement, where the user becomes absorbed in the activity and loses awareness of the surrounding environment. Use when designing for creative work, deep reading, gameplay, learning, or any activity that benefits from extended focused attention. Immersion requires removing distractions, providing clear feedback, calibrating challenge to skill, and respecting the user's flow state. Modern attention-driven products often work against immersion in pursuit of engagement metrics; designs that genuinely serve immersion are increasingly distinctive.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Faesthetics-and-emotion-principles\u002Fskills\u002Fimmersion\u002FSKILL.md",[],[510,515,516,517,322,248,518,485,519,520,223,521,522,413,523,414,524,489,525,304,305,234],"state","metrics","awareness","feedback","challenge","environment","engagement","gameplay","deep","activity","benefits",{"skillNo":527,"name":528,"nameZh":18,"description":529,"descriptionZh":18,"repositoryFullName":201,"ownerLogin":202,"ownerAvatarUrl":203,"ownerAccountNo":204,"ownerDisplayName":205,"repositoryNo":206,"starsCount":207,"licenseSpdxId":208,"licenseFileUrl":18,"sourceHtmlUrl":530,"categories":531,"keywords":536,"publishedAt":235},"01M6JVWV4HJB0HF4YDCK836ME9","immersion-flow","Design for flow specifically — calibrate challenge to skill, provide immediate feedback, set clear goals, foreground the activity. Use when designing tools for skilled work (writing, drawing, programming, music), games, learning experiences, or any context where sustained engagement is the goal. Flow is the most-researched aspect of immersion; the conditions for it are specific and the design moves that support it are well-documented.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Faesthetics-and-emotion-principles\u002Fskills\u002Fimmersion-flow\u002FSKILL.md",[532,535],{"categoryNo":533,"categoryName":534,"taxonomyType":58,"taxonomyTypeDesc":59},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":35,"categoryName":36,"taxonomyType":11,"taxonomyTypeDesc":12},[322,510,537,274,538,243,539,540,541,248,542,518,485,519,543,223,544,524,545,304,234],"immersion flow","writing","calibrate","SET","Tools","music","context","goal","games",{"skillNo":547,"name":548,"nameZh":18,"description":549,"descriptionZh":18,"repositoryFullName":201,"ownerLogin":202,"ownerAvatarUrl":203,"ownerAccountNo":204,"ownerDisplayName":205,"repositoryNo":206,"starsCount":207,"licenseSpdxId":208,"licenseFileUrl":18,"sourceHtmlUrl":550,"categories":551,"keywords":554,"publishedAt":235},"01M6JVWNZXN0QX7R4166K79NXD","immersion-distraction-cost","Recognize and design against the cost of attention fragmentation — the disproportionate damage that even small interruptions do to focused work. Use when designing notification systems, evaluating whether a feature should interrupt the user, planning feature introductions, or auditing a product for unintended attention costs. The cost of breaking immersion is much higher than designers usually estimate; restraint in interruption is one of the most user-respectful design moves.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Faesthetics-and-emotion-principles\u002Fskills\u002Fimmersion-distraction-cost\u002FSKILL.md",[552,553],{"categoryNo":269,"categoryName":270,"taxonomyType":58,"taxonomyTypeDesc":59},{"categoryNo":21,"categoryName":22,"taxonomyType":11,"taxonomyTypeDesc":12},[298,510,555,274,433,278,485,452,223,435,414,415,505,556,304,557,234],"immersion distraction cost","notification","estimate",{"skillNo":559,"name":560,"nameZh":18,"description":561,"descriptionZh":18,"repositoryFullName":201,"ownerLogin":202,"ownerAvatarUrl":203,"ownerAccountNo":204,"ownerDisplayName":205,"repositoryNo":206,"starsCount":207,"licenseSpdxId":208,"licenseFileUrl":18,"sourceHtmlUrl":562,"categories":563,"keywords":565,"publishedAt":235},"01M6JVWF8TW58CXAFG8Q3SA47A","form-follows-function","Use this skill when designing the visual or aesthetic layer of a product, deciding between expressive style and functional restraint, evaluating decorative elements, or arguing about whether a feature should ship plain vs. polished. Trigger when stakeholders ask \"should we add visual flair to this?\", when reviewing a design that \"feels too decorated,\" or when picking between competing visual directions. Form Follows Function is one of the foundational principles in 'Universal Principles of Design' (Lidwell, Holden, Butler 2003) and one of the most-quoted dictums in design — but its meaning depends on which interpretation (descriptive vs. prescriptive) you take.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Faesthetics-and-emotion-principles\u002Fskills\u002Fform-follows-function\u002FSKILL.md",[564],{"categoryNo":269,"categoryName":270,"taxonomyType":58,"taxonomyTypeDesc":59},[379,566,274,567,278,451,383,568,251,226,415,347,229,418,258,232,569,570,422,571,572,234],"form follows function","interpretation","take","meaning","directions","layer","quoted",740]