[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7B2P4KXWZJS317GMF0Z2QEJ":3,"skill-same:01M7B2P4KXWZJS317GMF0Z2QEJ":60},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":14,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":45},"01M7B2P4KXWZJS317GMF0Z2QEJ","critique-visual-hierarchy",null,"Critique a rendered screen's hierarchy — entry point, eye flow, weight distribution, and emphasis. Use when attention lands in the wrong place. For establishing hierarchy in new work, use `visual-hierarchy` (ui-design).","jorgesolerrr\u002Fskills","jorgesolerrr","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F92542744?v=4","01M7B2B710R5NTAHS08MWZJXB0","Jorge Soler","01M7B2B721D4CAZJH7E6ZM4ZQ5",0,"MIT","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fowl-listener\u002Fcritique-visual-hierarchy\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fowl-listener\u002Fcritique-visual-hierarchy\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: critique-visual-hierarchy\ndescription: Critique a rendered screen's hierarchy — entry point, eye flow, weight distribution, and emphasis. Use when attention lands in the wrong place. For establishing hierarchy in new work, use `visual-hierarchy` (ui-design).\ndisable-model-invocation: true\n---\n# Critique Visual Hierarchy\nYou are an expert in visual hierarchy and screen-level design critique.\n## What You Do\nYou analyse a screen to identify whether hierarchy is clear, intentional, and aligned with user goals. You flag problems and suggest targeted fixes.\n## Critique Dimensions\n### Entry Point\nThe first element that captures the eye. Evaluate whether it is the *most important* thing on screen.\n- Is there a single dominant element, or does attention scatter?\n- Does size, contrast, or position establish the entry point clearly?\n- Does the entry point match the primary user goal for this screen?\n### Eye Flow\nThe path a user's eye travels after landing. Evaluate whether the path is deliberate and efficient.\n- Does the layout follow an F-pattern, Z-pattern, or intentional reading order?\n- Are there dead ends, loops, or confusing jumps?\n- Does flow lead naturally to the primary call-to-action?\n### Weight\nThe relative visual importance of each element. Evaluate whether weight is distributed purposefully.\n- Are size differentials at least 1.5× between hierarchy levels?\n- Is bold\u002Fheavy type used sparingly so it retains signal value?\n- Do background fill, stroke weight, and iconography add or fight the hierarchy?\n### Emphasis\nSpecific elements that demand extra attention. Evaluate whether emphasis is earned and singular.\n- Is there exactly one primary emphasis zone per view?\n- Are colour, contrast, or motion used to emphasise — or overused so they cancel out?\n- Does the highest-emphasis element match stakeholder and user priority?\n## Output Format\nFor each dimension — Entry Point, Eye Flow, Weight, Emphasis — provide:\n1. **Observation** — what you see (neutral, factual)\n2. **Problem** — what is broken and why it matters\n3. **Fix** — a specific, actionable change\nRate each dimension: `pass` \u002F `minor issue` \u002F `major issue`.\n## Common Failure Patterns\n- Multiple competing primaries — nothing reads as most important\n- Hierarchy flattening — too similar in size, weight, or colour across levels\n- False emphasis — decorative elements outweigh functional ones\n- Buried CTA — the action is visually quieter than surrounding content\n","# Critique Visual Hierarchy\nYou are an expert in visual hierarchy and screen-level design critique.\n## What You Do\nYou analyse a screen to identify whether hierarchy is clear, intentional, and aligned with user goals. You flag problems and suggest targeted fixes.\n## Critique Dimensions\n### Entry Point\nThe first element that captures the eye. Evaluate whether it is the *most important* thing on screen.\n- Is there a single dominant element, or does attention scatter?\n- Does size, contrast, or position establish the entry point clearly?\n- Does the entry point match the primary user goal for this screen?\n### Eye Flow\nThe path a user's eye travels after landing. Evaluate whether the path is deliberate and efficient.\n- Does the layout follow an F-pattern, Z-pattern, or intentional reading order?\n- Are there dead ends, loops, or confusing jumps?\n- Does flow lead naturally to the primary call-to-action?\n### Weight\nThe relative visual importance of each element. Evaluate whether weight is distributed purposefully.\n- Are size differentials at least 1.5× between hierarchy levels?\n- Is bold\u002Fheavy type used sparingly so it retains signal value?\n- Do background fill, stroke weight, and iconography add or fight the hierarchy?\n### Emphasis\nSpecific elements that demand extra attention. Evaluate whether emphasis is earned and singular.\n- Is there exactly one primary emphasis zone per view?\n- Are colour, contrast, or motion used to emphasise — or overused so they cancel out?\n- Does the highest-emphasis element match stakeholder and user priority?\n## Output Format\nFor each dimension — Entry Point, Eye Flow, Weight, Emphasis — provide:\n1. **Observation** — what you see (neutral, factual)\n2. **Problem** — what is broken and why it matters\n3. **Fix** — a specific, actionable change\nRate each dimension: `pass` \u002F `minor issue` \u002F `major issue`.\n## Common Failure Patterns\n- Multiple competing primaries — nothing reads as most important\n- Hierarchy flattening — too similar in size, weight, or colour across levels\n- False emphasis — decorative elements outweigh functional ones\n- Buried CTA — the action is visually quieter than surrounding content\n",{"name":5,"description":7,"disable-model-invocation":25},true,"main","5affa1dd6283cecc37579e77a6de9288f5a4177f","skills\u002Fowl-listener\u002Fcritique-visual-hierarchy","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr","Computer Scientist | Backend developer | Python developer","2026-11-04 06:49:16",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":25},[35,38,41],{"tool":36,"command":37},"npx","npx skills add jorgesolerrr\u002Fskills --skill critique-visual-hierarchy",{"tool":39,"command":40},"bunx","bunx skills add jorgesolerrr\u002Fskills --skill critique-visual-hierarchy",{"tool":42,"command":43},"pnpm","pnpm dlx skills add jorgesolerrr\u002Fskills --skill critique-visual-hierarchy","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fowl-listener\u002Fcritique-visual-hierarchy\u002FSKILL.md",[46,52,56],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"agents\u002Fopenai.yaml","REFERENCE","参考文档",43,"https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fowl-listener\u002Fcritique-visual-hierarchy\u002Fagents\u002Fopenai.yaml",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"CREDITS.md",355,"https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fowl-listener\u002Fcritique-visual-hierarchy\u002FCREDITS.md",{"path":57,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":59,"sourceHtmlUrl":16},"LICENSE","许可证",1064,[61,69,77,85,93,101],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":65,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":20},"01M7B31X3JCSHDXNTNZ0VH2773","explainroo","Make an explainer video (MP4) with a voice-over using explainroo. The voice is made on this computer and no API key is needed. Use when the user asks for an explainer, how-to, walkthrough, launch or tutorial video, an animated diagram with a voice-over, or a short for YouTube, Reels or TikTok.","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fvincentsch\u002Fexplainroo\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fvincentsch\u002Fexplainroo\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":73,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":20},"01M7B31SZRHNV2M04YW4WR5EJZ","unslop","Cut AI tells from prose a human will read. Use when drafting or editing docs, READMEs, PR descriptions, commit messages, emails or posts, or when the user says unslop or \"sounds like AI\".","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Funslop\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Funslop\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":81,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":20},"01M7B31PBF1VQ9VHDDSS6WMBJ6","technical-writing","Layered technical-writing standard (Diátaxis, Google style, STE, Global English) for docs, RFCs, READMEs, PR descriptions and commit messages.","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Ftechnical-writing\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Ftechnical-writing\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":89,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":20},"01M7B31KHS6P377SZT8SD1RTHW","no-comments","Spawn Comment Sicko, fix accepted findings, and offer encodings for claimed constraints.","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Fno-comments\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Fno-comments\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":97,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":20},"01M7B31FAY1MDAQ6RDXCFJH2P3","ponytail","Lazy senior dev mode: the smallest change that fully solves the task, and a reply a busy human understands in one read. Use on any coding task (writing, fixing, refactoring, reviewing, choosing dependencies) and when the user says \"ponytail\", \"be lazy\", \"simplest solution\", \"yagni\", or complains about over-engineering or bloat. Levels: lite, full (default), ultra.","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fponytail\u002Fponytail\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fponytail\u002Fponytail\u002FSKILL.md",[],[],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":105,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":20},"01M7B31AXF7VDH9NFSRXBN6FAM","ponytail-review","Quality review of a change: is the logic right, is it safe, does it hold under real load, is risky code tested, is it fast enough, and is every line needed. Reads the connected code, not only the diff. Each finding is explained in plain English. Use for \"review this\", \"code review\", \"review the last commit\", \"review my PR\", \"is this over-engineered\", \u002Fponytail-review.","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fponytail\u002Fponytail-review\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjorgesolerrr\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fponytail\u002Fponytail-review\u002FSKILL.md",[],[]]