[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ETMBMA9C3NHJFFC7V2Q5KY":3,"skill-same:01M7ETMBMA9C3NHJFFC7V2Q5KY":58},{"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":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":32,"commitSha":33,"skillDirectory":34,"forksCount":13,"repositoryHtmlUrl":35,"repositoryHomepageUrl":6,"ownerHtmlUrl":36,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":37,"install":38,"resources":51},"01M7ETMBMA9C3NHJFFC7V2Q5KY","omh-agent-instructions",null,"[omh] Agent instruction file for a repo -- AGENTS.md, CLAUDE.md, a Cursor rule: write or update what an agent cannot derive from the code, inside a marked region, with every command verified or marked unverified and no counts that drift. Use when the user says: agent-instructions, agents.md, claude.md, gemini.md, copilot-instructions.md, .cursorrules, cursor rules, cursor rule.","mhyahya854\u002FAI-Second-Brain_Universal-Rules","mhyahya854","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F194078115?v=4","01M7EGSP2M9T858SDHJMXQ257Y","01M7EGSP3N6HN6879SVDPMD4DZ",0,"MIT","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Frlaope\u002Foh-my-hermes\u002Fomh-agent-instructions\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: \"omh-agent-instructions\"\ndescription: \"[omh] Agent instruction file for a repo -- AGENTS.md, CLAUDE.md, a Cursor rule: write or update what an agent cannot derive from the code, inside a marked region, with every command verified or marked unverified and no counts that drift. Use when the user says: agent-instructions, agents.md, claude.md, gemini.md, copilot-instructions.md, .cursorrules, cursor rules, cursor rule.\"\nlicense: MIT\nmetadata:\n  hermes:\n    tags: [workflow, oh-my-hermes, planning]\n    category: planning\n    phase: agent-instructions\n    role: planner\n    quality_tier: verified-command-and-region-gated\n---\n\n# Agent Instructions\n\nThis is an OMH `agent-instructions` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).\n\n## Why This Exists\n\n`agent-instructions` exists because the file every handoff target reads first had no owner: `rules-distill` extracts rule candidates, `codebase-onboarding` builds a human reading path, and `context` aligns terminology, and each reads that file without writing it.\n\n## First Steps\n\n- List every instruction file and which agent reads it before proposing a section.\n- Run or ask for the observed run of each command before marking it verified.\n\n## Do Not Use When\n\n- The ask is distilling repeated lessons into reviewed rule candidates; use `omh-rules-distill`.\n- The ask is a reading path through the codebase for a new engineer; use `omh-codebase-onboarding`.\n- The ask is project terminology alignment -- reviewing the terms this project uses and correcting inconsistent vocabulary; use `ulw-context`.\n- The ask is user-facing product documentation; use `omh-docs`.\n\n## Examples\n\nGood example:\n\n- Prompt: update our CLAUDE.md\n- Expected behavior: Inventory the instruction files, run or collect each build and test command, mark each verified or unverified, and replace only the marked region with the commands, the generated-file map, the gates, and the costed pitfalls, refusing any count or line number.\n- Why: An instruction file that states an unrun command or a stale count sends every later agent the wrong way.\n\nBad example:\n\n- Prompt: add that the suite has 4,100 tests and the router is at line 212 of chat.py\n- Expected behavior: Refuse both values, and write the command that counts the tests and the symbol that locates the router instead.\n- Why: Both numbers were already wrong by the next merge.\n\n## Completion Checklist\n\n- Every instruction file and its reader are listed.\n- Every command is marked verified with an observed run, or unverified.\n- Only the marked region changed, and hand-written text is byte-for-byte.\n- No count, line number, or value the code already states was written.\n- Every generated file names its source, its regenerate command, and its gate.\n\n## Recovery Notes\n\n- If a command cannot be run here, write it marked unverified with what would verify it.\n- If the file has no markers, insert them once around the new section and leave everything else untouched.\n\n\n\n## When to Use\n\nUse when the repository's agent instruction file is being written or kept current: AGENTS.md, CLAUDE.md, GEMINI.md, a Cursor rule, or a Copilot instructions file. The output is the build and test commands each marked verified or unverified, the generated-file map with its regenerate command and gate, the byte-exact gates, and the pitfalls that cost time, written inside a marker-delimited region so hand-written sections survive.\n\n    Strong routing signals: `agent-instructions`, `agents.md`, `claude.md`, `gemini.md`, `copilot-instructions.md`, `.cursorrules`, `cursor rules`, `cursor rule`, `agent instruction file`, `agent instructions file`, `instructions file for agents`, `set up agents.md`, `update our claude.md`, `write an agents.md`\n\n## Catalog Metadata\n\nCategory: `planning`\nPhase: `agent-instructions`\nQuality tier: `verified-command-and-region-gated`\nReasoning demand: `standard`\n\nQuality bar:\n\n- Inventory every instruction file first and respect closest-file-wins nesting.\n- Load `references\u002Finstruction-file-method.md` for the section order, the marker convention, the verified and unverified command form, and the drift rules instead of recalling them.\n- Record each pitfall with what it cost, so a reader can tell a scar from a preference.\n- Pair every generated file with its source, its regenerate command, and the gate that checks it.\n- Keep prepared, verified, and written as separate states for every command and section.\n\nRequired inputs:\n\n- which instruction files exist, where they sit, and which agents read them\n- the build, test, lint, and regenerate commands the repository uses\n- which files are generated, from what source, and which gate checks them\n- the pitfalls that have cost time, each with what it cost\n- observed output for every command written into the file\n\nExpected outputs:\n\n- instruction_file_inventory\u002Fv1\n- command_verification_record\u002Fv1\n- instruction_region_update\u002Fv1\n- drift_refusal_note\u002Fv1 when a requested line would record a count or a line number\n\nArtifact expectations:\n\n- instruction_file_inventory\u002Fv1 lists every instruction file, its path, the agents that read it, and which one is closest to each directory, since the closest file wins\n- command_verification_record\u002Fv1 marks every command verified, with the observed exit status and when, or unverified, and nothing is written as verified without an observed run\n- instruction_region_update\u002Fv1 replaces only the text between `\u003C!-- omh:agent-instructions:begin -->` and `\u003C!-- omh:agent-instructions:end -->`, and inserts the markers once when absent, so every hand-written section outside them is left byte-for-byte\n- drift_refusal_note\u002Fv1 names each requested count, line number, or other value the code already states, and writes the command or the file that derives it instead\n\nSafety rules:\n\n- Never write outside the marker-delimited region: the text before `\u003C!-- omh:agent-instructions:begin -->` and after `\u003C!-- omh:agent-instructions:end -->` is hand-written and stays byte-for-byte.\n- Never write a command as verified without an observed run; mark it unverified instead.\n- Refuse to record counts, line numbers, test totals, or file sizes; they drift, so point at the command or file that derives them.\n- Write only what an agent cannot derive from the code; restating the code is drift waiting to happen.\n- Never copy secrets, tokens, or private hostnames into an instruction file.\n\n## Runtime Evidence\n\nUse the current host's own tools and subagent\u002Ftask mechanism when available;\notherwise run the same lanes sequentially or name the unavailable capability.\nA prepared plan, handoff, checklist, or skill installation is not execution,\nreview, CI, merge-readiness, or merge evidence. Record actual tool results, or\n`not_observed` \u002F `not_available`, in the record; never invent dispatch or host\naccounting.\nTreat supplied context as advisory, not proof of hidden memory reads or writes.\nState scope, constraints, verification, and the stop condition before work.\nReply in the user's own words and the host's own voice: the host's persona owns\nreply language, tone, speech level, and sentence endings, progress updates\nincluded (where it sets no language, use the one the user wrote in), and OMH\nshapes structure and content only; OMH's record terms\n(surface, lane, wrapper, handoff, evidence boundary, not_observed) stay in\nrecords and tool calls, never in the sentence the user reads unless they ask\nabout one; and when a real unresolved user decision or a useful briefing discussion\nremains, offer one specific, content-linked question. Completed work needs no question;\nomit unrelated non-action footers and generic offers to continue.\nSupporting paths are relative to this skill directory; sibling skill paths are\nrelative to its parent. Resolve them from the host-provided skill base directory\n(`{baseDir}` on hosts that provide it), never a hardcoded install location.\nA named workflow not installed here is unavailable, not permission to emulate\nits host-specific capabilities. Verify through the real surface before done.\n","# Agent Instructions\n\nThis is an OMH `agent-instructions` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).\n\n## Why This Exists\n\n`agent-instructions` exists because the file every handoff target reads first had no owner: `rules-distill` extracts rule candidates, `codebase-onboarding` builds a human reading path, and `context` aligns terminology, and each reads that file without writing it.\n\n## First Steps\n\n- List every instruction file and which agent reads it before proposing a section.\n- Run or ask for the observed run of each command before marking it verified.\n\n## Do Not Use When\n\n- The ask is distilling repeated lessons into reviewed rule candidates; use `omh-rules-distill`.\n- The ask is a reading path through the codebase for a new engineer; use `omh-codebase-onboarding`.\n- The ask is project terminology alignment -- reviewing the terms this project uses and correcting inconsistent vocabulary; use `ulw-context`.\n- The ask is user-facing product documentation; use `omh-docs`.\n\n## Examples\n\nGood example:\n\n- Prompt: update our CLAUDE.md\n- Expected behavior: Inventory the instruction files, run or collect each build and test command, mark each verified or unverified, and replace only the marked region with the commands, the generated-file map, the gates, and the costed pitfalls, refusing any count or line number.\n- Why: An instruction file that states an unrun command or a stale count sends every later agent the wrong way.\n\nBad example:\n\n- Prompt: add that the suite has 4,100 tests and the router is at line 212 of chat.py\n- Expected behavior: Refuse both values, and write the command that counts the tests and the symbol that locates the router instead.\n- Why: Both numbers were already wrong by the next merge.\n\n## Completion Checklist\n\n- Every instruction file and its reader are listed.\n- Every command is marked verified with an observed run, or unverified.\n- Only the marked region changed, and hand-written text is byte-for-byte.\n- No count, line number, or value the code already states was written.\n- Every generated file names its source, its regenerate command, and its gate.\n\n## Recovery Notes\n\n- If a command cannot be run here, write it marked unverified with what would verify it.\n- If the file has no markers, insert them once around the new section and leave everything else untouched.\n\n\n\n## When to Use\n\nUse when the repository's agent instruction file is being written or kept current: AGENTS.md, CLAUDE.md, GEMINI.md, a Cursor rule, or a Copilot instructions file. The output is the build and test commands each marked verified or unverified, the generated-file map with its regenerate command and gate, the byte-exact gates, and the pitfalls that cost time, written inside a marker-delimited region so hand-written sections survive.\n\n    Strong routing signals: `agent-instructions`, `agents.md`, `claude.md`, `gemini.md`, `copilot-instructions.md`, `.cursorrules`, `cursor rules`, `cursor rule`, `agent instruction file`, `agent instructions file`, `instructions file for agents`, `set up agents.md`, `update our claude.md`, `write an agents.md`\n\n## Catalog Metadata\n\nCategory: `planning`\nPhase: `agent-instructions`\nQuality tier: `verified-command-and-region-gated`\nReasoning demand: `standard`\n\nQuality bar:\n\n- Inventory every instruction file first and respect closest-file-wins nesting.\n- Load `references\u002Finstruction-file-method.md` for the section order, the marker convention, the verified and unverified command form, and the drift rules instead of recalling them.\n- Record each pitfall with what it cost, so a reader can tell a scar from a preference.\n- Pair every generated file with its source, its regenerate command, and the gate that checks it.\n- Keep prepared, verified, and written as separate states for every command and section.\n\nRequired inputs:\n\n- which instruction files exist, where they sit, and which agents read them\n- the build, test, lint, and regenerate commands the repository uses\n- which files are generated, from what source, and which gate checks them\n- the pitfalls that have cost time, each with what it cost\n- observed output for every command written into the file\n\nExpected outputs:\n\n- instruction_file_inventory\u002Fv1\n- command_verification_record\u002Fv1\n- instruction_region_update\u002Fv1\n- drift_refusal_note\u002Fv1 when a requested line would record a count or a line number\n\nArtifact expectations:\n\n- instruction_file_inventory\u002Fv1 lists every instruction file, its path, the agents that read it, and which one is closest to each directory, since the closest file wins\n- command_verification_record\u002Fv1 marks every command verified, with the observed exit status and when, or unverified, and nothing is written as verified without an observed run\n- instruction_region_update\u002Fv1 replaces only the text between `\u003C!-- omh:agent-instructions:begin -->` and `\u003C!-- omh:agent-instructions:end -->`, and inserts the markers once when absent, so every hand-written section outside them is left byte-for-byte\n- drift_refusal_note\u002Fv1 names each requested count, line number, or other value the code already states, and writes the command or the file that derives it instead\n\nSafety rules:\n\n- Never write outside the marker-delimited region: the text before `\u003C!-- omh:agent-instructions:begin -->` and after `\u003C!-- omh:agent-instructions:end -->` is hand-written and stays byte-for-byte.\n- Never write a command as verified without an observed run; mark it unverified instead.\n- Refuse to record counts, line numbers, test totals, or file sizes; they drift, so point at the command or file that derives them.\n- Write only what an agent cannot derive from the code; restating the code is drift waiting to happen.\n- Never copy secrets, tokens, or private hostnames into an instruction file.\n\n## Runtime Evidence\n\nUse the current host's own tools and subagent\u002Ftask mechanism when available;\notherwise run the same lanes sequentially or name the unavailable capability.\nA prepared plan, handoff, checklist, or skill installation is not execution,\nreview, CI, merge-readiness, or merge evidence. Record actual tool results, or\n`not_observed` \u002F `not_available`, in the record; never invent dispatch or host\naccounting.\nTreat supplied context as advisory, not proof of hidden memory reads or writes.\nState scope, constraints, verification, and the stop condition before work.\nReply in the user's own words and the host's own voice: the host's persona owns\nreply language, tone, speech level, and sentence endings, progress updates\nincluded (where it sets no language, use the one the user wrote in), and OMH\nshapes structure and content only; OMH's record terms\n(surface, lane, wrapper, handoff, evidence boundary, not_observed) stay in\nrecords and tool calls, never in the sentence the user reads unless they ask\nabout one; and when a real unresolved user decision or a useful briefing discussion\nremains, offer one specific, content-linked question. Completed work needs no question;\nomit unrelated non-action footers and generic offers to continue.\nSupporting paths are relative to this skill directory; sibling skill paths are\nrelative to its parent. Resolve them from the host-provided skill base directory\n(`{baseDir}` on hosts that provide it), never a hardcoded install location.\nA named workflow not installed here is unavailable, not permission to emulate\nits host-specific capabilities. Verify through the real surface before done.\n",{"name":5,"license":14,"metadata":23,"description":7},{"hermes":24},{"role":25,"tags":26,"phase":30,"category":29,"quality_tier":31},"planner",[27,28,29],"workflow","oh-my-hermes","planning","agent-instructions","verified-command-and-region-gated","main","4c174e06a831864e98c30f630a7aa6c04738b094","skills\u002F_intake\u002Fgithub\u002Frlaope\u002Foh-my-hermes\u002Fomh-agent-instructions","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules","https:\u002F\u002Fgithub.com\u002Fmhyahya854","2026-11-06 02:03:37",{"source":8,"skillName":5,"commands":39,"prompt":49,"zipAvailable":50},[40,43,46],{"tool":41,"command":42},"npx","npx skills add mhyahya854\u002FAI-Second-Brain_Universal-Rules --skill omh-agent-instructions",{"tool":44,"command":45},"bunx","bunx skills add mhyahya854\u002FAI-Second-Brain_Universal-Rules --skill omh-agent-instructions",{"tool":47,"command":48},"pnpm","pnpm dlx skills add mhyahya854\u002FAI-Second-Brain_Universal-Rules --skill omh-agent-instructions","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Frlaope\u002Foh-my-hermes\u002Fomh-agent-instructions\u002FSKILL.md",true,[52],{"path":53,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002Finstruction-file-method.md","REFERENCE","参考文档",4250,"https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Frlaope\u002Foh-my-hermes\u002Fomh-agent-instructions\u002Freferences\u002Finstruction-file-method.md",[59,67,75,83,90,97],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":63,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":18},"01M7EX4T721AAH60R0239P8WBZ","frontend-slides","Create stunning, animation-rich HTML presentations from scratch or by converting PowerPoint files. Use when the user wants to build a presentation, convert a PPT\u002FPPTX to web, or create slides for a talk\u002Fpitch. Helps non-designers discover their aesthetic through visual exploration rather than abstract choices.","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fzarazhangrui\u002Ffrontend-slides\u002Ffrontend-slides\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fzarazhangrui\u002Ffrontend-slides\u002Ffrontend-slides\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":71,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":18},"01M7EX495RSHTTCEJVX7C83FA3","design-dna","Extract, define, and apply design DNA across three dimensions: design system (tokens), design style (qualitative feel), and visual effects (Canvas, WebGL, 3D, particles, shaders, scroll effects, etc.). Use this skill when: (1) a user wants to see the full 3-dimension design structure\u002Fschema, (2) a user provides images, screenshots, or URLs of reference designs and wants them analyzed into a structured JSON profile covering all three dimensions, (3) a user has a Design DNA JSON and content and wants a design generated from it, or (4) any combination of these phases. Triggers on \"design DNA\", \"extract design style\", \"analyze design\", \"design tokens from reference\", \"generate design from JSON\", \"design system from screenshot\", \"design profile\", \"style guide JSON\", \"visual effects analysis\", \"design with effects\", \"3d design analysis\".","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fzanwei\u002Fdesign-dna\u002Fdesign-dna\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fzanwei\u002Fdesign-dna\u002Fdesign-dna\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":79,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":18},"01M7EX45RF2XZKRC3KDJDTT1PH","wireframe","Generate JSON wireframe with HTML preview","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fyhassy\u002Fwireframe-skill\u002Fwireframe-skill\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fyhassy\u002Fwireframe-skill\u002Fwireframe-skill\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":18},"01M7EWZEM3MHD48AYSYFR2C9JP","social-publishing","Schedule and publish social media posts across 13 platforms (X, LinkedIn, Instagram, Facebook Pages, TikTok, Discord, Telegram, YouTube, Reddit, WordPress, Pinterest) via the SocialClaw API. Use when the user wants to publish, schedule, or manage social media content programmatically. Requires SOCIALCLAW_API_KEY.","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fwshobson\u002Fagents\u002Fsocial-publishing\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":18},"01M7EWKDEK9840C728VXT78EQ9","hermes-tweet","Install and operate Hermes Tweet, a Hermes Agent plugin for X\u002FTwitter research, timeline reading, tweet analysis, and approval-gated private or state-changing operations. Use this skill when installing Hermes Tweet, researching X\u002FTwitter accounts, monitoring launch signals, investigating mentions, auditing giveaways, or preparing gated X operations. Use proactively when a Hermes Agent workflow needs current X\u002FTwitter context. Requires XQUIK_API_KEY for read and action tools.","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fwshobson\u002Fagents\u002Fhermes-tweet\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":18},"01M7EWASXP3NZWW95CJPT2CRWN","refactoring-ui","Audit and fix visual hierarchy, spacing, color, and depth in web UIs. Use when the user mentions \"my UI looks off\" (or amateur\u002Funprofessional), \"fix the design\", \"Tailwind styling\", \"color palette\", \"visual hierarchy\", \"design system\", \"spacing scale\", or \"component styling\". Also trigger when building consistent design tokens, creating dark mode themes, improving data-visualization clarity, or polishing UI details before launch. Covers grayscale-first workflow, constrained design scales, shadows, and component styling. For typeface selection, see web-typography. For usability audits, see ux-heuristics.","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fwondelai\u002Fskills\u002Frefactoring-ui\u002FSKILL.md",[],[]]