[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ETWD1GF0CM8T1DB53WZ1WN":3,"skill-same:01M7ETWD1GF0CM8T1DB53WZ1WN":95},{"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":33,"commitSha":34,"skillDirectory":35,"forksCount":13,"repositoryHtmlUrl":36,"repositoryHomepageUrl":6,"ownerHtmlUrl":37,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":38,"install":39,"resources":52},"01M7ETWD1GF0CM8T1DB53WZ1WN","omh-frontend",null,"[omh] Building or polishing a web or terminal UI: prepare design-system-driven web and terminal (TUI) UI creation, redesign, polish, accessibility, performance, and visual QA handoffs. Use when the user says: frontend, front-end, front end, frontend skill, in the frontend, on the frontend, to the frontend, web ui.","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-frontend\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: \"omh-frontend\"\ndescription: \"[omh] Building or polishing a web or terminal UI: prepare design-system-driven web and terminal (TUI) UI creation, redesign, polish, accessibility, performance, and visual QA handoffs. Use when the user says: frontend, front-end, front end, frontend skill, in the frontend, on the frontend, to the frontend, web ui.\"\nlicense: MIT\ncompatibility: \"Requires the omh CLI on PATH (pip install oh-my-hermes).\"\nmetadata:\n  hermes:\n    tags: [workflow, oh-my-hermes, materials]\n    category: materials\n    phase: frontend-design\n    role: operator\n    quality_tier: frontend-design-gated\n---\n\n# Frontend\n\nThis is an OMH `frontend` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).\n\n## Why This Exists\n\n`frontend` gives OMH a first-class web UI creation and polishing workflow so Hermes can prepare high-quality layout, design-system, accessibility, performance, and visual-QA handoffs without becoming the hidden coding or browser runtime.\n\n## Do Not Use When\n\n- The user needs a broad premium-quality gate across web, deck, PDF, poster, or publishing outputs; use `omh-design-quality-gate`.\n- The user wants a disposable wireframe or mocked interaction to settle one interaction question before planning; use `omh-decision-prototype`.\n- The user only needs a file, deck, PDF, spreadsheet, HWP, or attachment package; use `omh-materials-package` or `omh-deliverable-package`.\n- The user only needs an image card or infographic prompt; use `omh-image-cards`.\n- The user asks to mark a UI as visually passed without fresh rendered evidence; use `omh-visual-qa` and keep PASS blocked until observed.\n\n## Examples\n\nGood example:\n\n- Prompt: frontend 이 대시보드가 AI 티 안 나게 레이아웃과 디자인 시스템을 잡아줘.\n- Expected behavior: Prepare frontend_design_brief\u002Fv1, design_system_contract\u002Fv1, route\u002Fstate matrix, implementation handoff, and visual_qa_required\u002Fv1.\n- Why: The request is about web UI design, layout quality, and anti-generic frontend polish.\n\nBad example:\n\n- Prompt: frontend 코드도 안 봤지만 Lighthouse랑 시각 QA 통과했다고 해줘.\n- Expected behavior: Mark browser, performance, accessibility, and visual QA as not_observed and request the smallest observed evidence path.\n- Why: A frontend brief is not implementation, browser, performance, or visual QA evidence.\n\n## Completion Checklist\n\n- The target page\u002Fcomponent, audience, primary task, references, and quality bar are named.\n- Greenfield work includes frontend_initial_generation_contract\u002Fv1 before implementation handoff.\n- The design_system_contract\u002Fv1 covers typography, spacing, palette, components, layout, motion, and responsive rules.\n- The frontend_route_state_matrix\u002Fv1 covers pages, 375\u002F768\u002F1280-style breakpoints, empty\u002Floading\u002Ferror, interaction, and CJK\u002Flocale risks.\n- The frontend_component_state_inventory\u002Fv1 covers reusable primitives and their default\u002Fhover\u002Ffocus\u002Factive\u002Fdisabled\u002Floading\u002Fempty\u002Ferror states.\n- The handoff names the executor\u002Fruntime owner and keeps code, browser, Lighthouse, accessibility, deployment, and visual QA evidence observed-only.\n- The next action is prepare_frontend_handoff, route to visual-qa, or report the missing evidence blocker.\n\n## Recovery Notes\n\n- If the target surface is unclear, prepare the brief with a route\u002Fcomponent gap instead of inventing pages.\n- If no visual reference exists, set a domain-fit quality bar and request references only when the decision changes layout or brand direction.\n\n\n\n## When to Use\n\nUse when Hermes should shape or improve a web\u002Ffrontend or terminal (TUI) surface before implementation: layout, design system, responsive states, accessibility, performance, motion, and anti-generic visual quality.\n\n    Strong routing signals: `frontend`, `front-end`, `front end`, `frontend skill`, `in the frontend`, `on the frontend`, `to the frontend`, `web ui`, `ui ux`, `ui\u002Fux`, `landing page`, `web app layout`, `responsive layout`, `responsive design`, `design system`, `component polish`, `layout polish`, `visual polish`, `styling`, `animation`, `motion design`, `smooth scroll`, `smooth scrolling`, `scroll animation`, `scroll animations`, `parallax scroll`, `parallax hero`, `parallax effect`, `chart styling`, `chart theming`, `chart colors`, `dashboard charts`, `style the charts`, `theme the charts`, `tooltip`, `footer design`, `better footer`, `site footer`, `website footer`, `neobrutalism`, `neobrutalism style`, `neobrutalist`, `neo brutalism`, `neo-brutalism`, `logo marquee`, `marquee animation`, `scrolling marquee`, `split text animation`, `split-text animation`, `shadcn`, `component registry`, `three.js scene`, `threejs scene`, `webgl scene`, `voxel scene`, `voxel art scene`, `accessibility`, `wcag`, `lighthouse`, `core web vitals`, `make it beautiful`, `make it premium`, `make it less ai`, `ai-looking ui`, `ai slop ui`, `slop ui`, `looks like ai slop`, `look like ai slop`, `feels like ai slop`, `screams ai slop`, `generic ui`, `broken layout`, `layout broken`, `frontend qa`, `frontend layout`, `tui design`, `terminal ui design`, `tui layout`, `フロントエンド`, `ランディングページ`, `レスポンシブ対応`, `デザインシステム`, `画面のUI実装`, `スムーススクロール`, `スクロールアニメーション`, `パララックス`, `チャートのスタイル`, `チャートスタイル`, `フッターデザイン`, `ネオブルータリズム`, `ロゴマーキー`, `프론트엔드`, `웹 ui`, `웹 화면`, `랜딩페이지`, `레이아웃`, `레이아웃 깨짐`, `깨짐`, `디자인 자연스럽게`, `자연스러운 디자인`, `화려하게`, `고급스럽게`, `부드러운 스크롤`, `스크롤 부드럽게`, `스크롤 애니메이션`, `패럴랙스`, `ai 티`, `ai틱`, `ai 틱`, `반응형`, `접근성`, `차트 스타일`, `차트 스타일링`, `차트 테마`, `푸터 디자인`, `네오브루탈리즘`, `로고 마키`, `마키 애니메이션`, `스플릿 텍스트`, `сделай лендинг`, `одностраничный лендинг`, `свёрстай страницу`, `сделай веб страницу`, `веб интерфейс`, `анимация на сайте`, `сделай сайт`, `анимацию при скролле`, `сделать веб страницу`, `лендинга`, `на лендинге`, `вёрстку сайта`, `сверстать страницу`, `сделай лэндинг`, `前端`, `落地页`, `响应式布局`, `设计系统`, `平滑滚动`, `滚动动画`, `视差滚动`, `图表样式`, `页脚设计`, `新粗野主义`, `跑马灯`, `bangun antarmuka UI frontend`, `bantu bikin landing page`, `rapikan tampilan frontend`, `buat halaman yang responsif`, `implementasikan desain UI`, `rancang antarmuka terminal`, `tambahkan animasi scroll`, `desain ulang tampilan dashboard`, `xây dựng giao diện frontend`, `giúp tạo landing page`, `cải thiện giao diện frontend`, `tạo trang có bố cục responsive`, `thực hiện thiết kế UI`, `thiết kế giao diện terminal`, `thêm hiệu ứng scroll`, `thiết kế lại giao diện dashboard`\n\n## Catalog Metadata\n\nCategory: `materials`\nPhase: `frontend-design`\nQuality tier: `frontend-design-gated`\nReasoning demand: `standard`\n\nQuality bar:\n\n- Name the product goal, audience, target surfaces, routes, states, and visual quality bar.\n- Hold the named bar: what a senior product designer at a top-tier product company (the Linear\u002FStripe\u002FSupabase class) would sign off on — technically clean but flat output fails it. Load `references\u002Ftaste-foundations.md`, name one primary taste direction, and reject the anti-slop patterns it lists.\n- Name the model's own default aesthetic before inheriting it — the editorial prior of cream grounds, serif display faces, and muted terracotta accents suits editorial, portfolio, and hospitality briefs and is a failure mode on dashboards, developer tools, fintech, and data-dense UIs. Treat a generic negation (\"don't make it look AI\", \"make it minimal\") as unactionable: an override counts only when it carries concrete tokens, a hex palette and a typeface stack recorded in DESIGN.md. Run the review prompts in `references\u002Ftaste-foundations.md` over framework blue, glass and gradient surfaces, default UI typefaces, bounce easing, blanket shadows, eyebrow\u002Ftitle\u002Fdescription stuffing, uniform column grids, and CJK body under the 14px Korean floor.\n- When the target surface is a terminal UI (TUI), load `references\u002Ftui-craft.md` and hold the same bar there: default widgets are scaffolding, not finished UI; borders spent sparingly with spacing and a muted-color ladder doing the hierarchy; one named terminal aesthetic; verification rendered at 80x24 and 120x40 minimum with the pasted output as the screenshot-equivalent.\n- Use references and domain fit to avoid generic AI-looking frontend output; when the user supplies a visual reference, load `references\u002Freference-token-extraction.md` and extract tokens into the contract instead of eyeballing.\n- Prepare a concrete design-system contract before implementation handoff: load `references\u002Fdesign-system-contract.md` and write DESIGN.md before the first component — no component code before the contract exists. A new DESIGN.md is Google's DESIGN.md format (YAML token front matter, its sections in its order) plus OMH's own sections; a file in OMH's earlier numbered layout stays valid and is converted only when the user asks. When Hermes' bundled `design-md` skill is available, author, lint, diff, or export a file in the format through it, never a file in the earlier layout; lint is evidence only from a run that executed, otherwise `not_observed`.\n- Query the local design reference data before fixing tokens: `omh design data --kind palette|font|ux --context \u003Cproduct context>` returns curated palettes, font stacks with CJK notes, and UX guidelines offline. Those rows inform DESIGN.md; the contract, not the query, still gates the code.\n- Scroll-driven motion is a decision with a bill: load `references\u002Fscroll-motion-libraries.md`, take the native path (CSS `scroll-behavior`, scroll-driven animations, `IntersectionObserver`, scroll-snap) unless one interpolated scroll position feeds several consumers, and when a library is chosen (Lenis is the reviewed record) name its reduced-motion branch, anchors, nested scroll, teardown, and INP budget in the contract.\n- Copied component source is the project's to fix: before adopting from a shadcn-style registry, load `references\u002Fcomponent-registry-adoption.md` (license, dependencies, reduced motion, ARIA, keyboard\u002Ftouch, token mapping, one hero effect per view). Theme charts through tokens, not config literals: load `references\u002Fchart-styling.md`.\n- A 3D or canvas scene (WebGL, a three.js-style engine, a voxel world) is judged on its first frame: load `references\u002Frendered-scene-craft.md`, boot on the view the scene's own title and copy promise, light it with a warm-or-cool key, a sky fill, explicit tone mapping, shadows, and fog, and make every small animated object read as what it is. A clean console is not a finished scene.\n- For first-time UI creation, name the initial generation branch, reference direction, reusable primitives, state coverage, and required visual QA path.\n- Cover responsive layout, empty\u002Floading\u002Ferror states, hover\u002Ffocus\u002Factive states, CJK text, accessibility, and performance expectations.\n- State performance as a budget, not an adjective: load `references\u002Fweb-vitals-budgets.md`, name one metric with its published bar (LCP, INP, CLS), the device and network class it is judged on, the route and load shape, and the baseline captured under that same profile - before the change. A budget chosen after seeing the result describes what happened instead of gating it.\n- Attribute before optimizing: name the LCP element and its dominant phase, the interaction that produced the worst INP and where the time went, or the node that shifted and what moved above it. A list of optimizations with no attribution is folklore, and a change that improved a different element than the one attributed did not fix the metric.\n- Keep field and lab apart: a p75 claim needs field data, a lab audit is a diagnostic sample on one device profile, and a lab pass is never a statement about real users.\n- After implementation lands on a web surface, load `references\u002Fscreenshot-loop.md` and require the screenshot iteration loop live-environment-first: capture the running UI at 1440\u002F768\u002F375px, compare against the supplied target or DESIGN.md, list every difference triaged Blocker\u002FHigh\u002FMedium\u002FNit with its capture attached, fix, and recapture until the difference list is empty.\n- Prefer native UI controls, stable dimensions, and realistic content over decorative cards, blobs, and placeholder-heavy screens.\n- Keep implementation, browser verification, accessibility\u002Fperformance checks, visual QA, and deployment as observed-only evidence.\n\nRequired inputs:\n\n- target app, page, route, or component\n- audience and primary user task\n- existing design system or missing-system gap\n- style references or quality bar\n- initial generation mode or redesign mode\n- DESIGN.md or design-system source of truth when available\n- framework\u002Fstack when known\n- routes, states, breakpoints, and locale\u002FCJK risks\n- accessibility and performance constraints\n- observed browser evidence for completion claims\n\nExpected outputs:\n\n- frontend_design_brief\u002Fv1\n- frontend_initial_generation_contract\u002Fv1 when greenfield\n- design_system_contract\u002Fv1\n- design_reference_selection\u002Fv1\n- reference_packet\u002Fv1 when supplied\n- frontend_route_state_matrix\u002Fv1\n- frontend_component_state_inventory\u002Fv1\n- frontend_implementation_handoff\u002Fv1\n- accessibility_performance_expectations\u002Fv1\n- visual_qa_required\u002Fv1\n- observed_browser_evidence\u002Fv1 when observed\n\nArtifact expectations:\n\n- frontend_design_brief\u002Fv1 when prepared\n- frontend_initial_generation_contract\u002Fv1 declares DESIGN.md\u002Fdesign-system work, reference lane, token extraction, reusable primitives, and visual QA path before new UI code\n- design_system_contract\u002Fv1 with layout, spacing, typography, color, component, motion, and responsive rules\n- design_reference_selection\u002Fv1 names supplied references or the domain-fit style direction and explicitly avoids copying third-party logos, assets, or brand copy\n- frontend_route_state_matrix\u002Fv1 with pages, states, viewports, CJK\u002Flocale, empty\u002Floading\u002Ferror, and interaction states\n- frontend_component_state_inventory\u002Fv1 with default, hover, focus, active, disabled, loading, empty, and error states for reusable primitives\n- frontend_implementation_handoff\u002Fv1 for the selected executor\u002Fruntime\n- browser screenshots, accessibility reports, Lighthouse\u002FCore Web Vitals, and visual QA only when observed\n\nSafety rules:\n\n- Do not claim implementation, browser verification, deployment, Lighthouse, accessibility pass, or visual QA from a prepared frontend brief.\n- Reject generic AI-looking UI: one-note palettes, weak hierarchy, cramped cards, ungrounded gradients, decorative filler, and placeholder-heavy copy.\n- Require a design-system contract before broad visual changes.\n- For greenfield UI, require an initial generation contract before implementation handoff so the first generated screen has tokens, references, primitives, states, and QA expectations.\n- Require fresh rendered evidence after the last UI edit before PASS.\n- Do not hand off a smooth-scroll integration without its reduced-motion branch, keyboard\u002Fanchor\u002Fnested-scroll behavior, and teardown named; a `respectReducedMotion` option covers the library own scroll, never the animations the project wrote.\n- Do not hand off a copied registry component or text effect without its license read at the source and its reduced-motion branch; decorative duplicates and split characters are `aria-hidden`, and a marquee gets a pause reachable by keyboard and touch.\n- Do not report a Core Web Vitals number without the device class, route, and load shape it was measured under; a figure from a different profile than the baseline is not a comparison.\n- For Korean\u002FCJK text, clipped glyphs, awkward line breaks, orphan particles, tiny copy, and overflow block visual QA.\n- Do not call external design, image, browser, LLM, or network services from OMH core.\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","# Frontend\n\nThis is an OMH `frontend` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).\n\n## Why This Exists\n\n`frontend` gives OMH a first-class web UI creation and polishing workflow so Hermes can prepare high-quality layout, design-system, accessibility, performance, and visual-QA handoffs without becoming the hidden coding or browser runtime.\n\n## Do Not Use When\n\n- The user needs a broad premium-quality gate across web, deck, PDF, poster, or publishing outputs; use `omh-design-quality-gate`.\n- The user wants a disposable wireframe or mocked interaction to settle one interaction question before planning; use `omh-decision-prototype`.\n- The user only needs a file, deck, PDF, spreadsheet, HWP, or attachment package; use `omh-materials-package` or `omh-deliverable-package`.\n- The user only needs an image card or infographic prompt; use `omh-image-cards`.\n- The user asks to mark a UI as visually passed without fresh rendered evidence; use `omh-visual-qa` and keep PASS blocked until observed.\n\n## Examples\n\nGood example:\n\n- Prompt: frontend 이 대시보드가 AI 티 안 나게 레이아웃과 디자인 시스템을 잡아줘.\n- Expected behavior: Prepare frontend_design_brief\u002Fv1, design_system_contract\u002Fv1, route\u002Fstate matrix, implementation handoff, and visual_qa_required\u002Fv1.\n- Why: The request is about web UI design, layout quality, and anti-generic frontend polish.\n\nBad example:\n\n- Prompt: frontend 코드도 안 봤지만 Lighthouse랑 시각 QA 통과했다고 해줘.\n- Expected behavior: Mark browser, performance, accessibility, and visual QA as not_observed and request the smallest observed evidence path.\n- Why: A frontend brief is not implementation, browser, performance, or visual QA evidence.\n\n## Completion Checklist\n\n- The target page\u002Fcomponent, audience, primary task, references, and quality bar are named.\n- Greenfield work includes frontend_initial_generation_contract\u002Fv1 before implementation handoff.\n- The design_system_contract\u002Fv1 covers typography, spacing, palette, components, layout, motion, and responsive rules.\n- The frontend_route_state_matrix\u002Fv1 covers pages, 375\u002F768\u002F1280-style breakpoints, empty\u002Floading\u002Ferror, interaction, and CJK\u002Flocale risks.\n- The frontend_component_state_inventory\u002Fv1 covers reusable primitives and their default\u002Fhover\u002Ffocus\u002Factive\u002Fdisabled\u002Floading\u002Fempty\u002Ferror states.\n- The handoff names the executor\u002Fruntime owner and keeps code, browser, Lighthouse, accessibility, deployment, and visual QA evidence observed-only.\n- The next action is prepare_frontend_handoff, route to visual-qa, or report the missing evidence blocker.\n\n## Recovery Notes\n\n- If the target surface is unclear, prepare the brief with a route\u002Fcomponent gap instead of inventing pages.\n- If no visual reference exists, set a domain-fit quality bar and request references only when the decision changes layout or brand direction.\n\n\n\n## When to Use\n\nUse when Hermes should shape or improve a web\u002Ffrontend or terminal (TUI) surface before implementation: layout, design system, responsive states, accessibility, performance, motion, and anti-generic visual quality.\n\n    Strong routing signals: `frontend`, `front-end`, `front end`, `frontend skill`, `in the frontend`, `on the frontend`, `to the frontend`, `web ui`, `ui ux`, `ui\u002Fux`, `landing page`, `web app layout`, `responsive layout`, `responsive design`, `design system`, `component polish`, `layout polish`, `visual polish`, `styling`, `animation`, `motion design`, `smooth scroll`, `smooth scrolling`, `scroll animation`, `scroll animations`, `parallax scroll`, `parallax hero`, `parallax effect`, `chart styling`, `chart theming`, `chart colors`, `dashboard charts`, `style the charts`, `theme the charts`, `tooltip`, `footer design`, `better footer`, `site footer`, `website footer`, `neobrutalism`, `neobrutalism style`, `neobrutalist`, `neo brutalism`, `neo-brutalism`, `logo marquee`, `marquee animation`, `scrolling marquee`, `split text animation`, `split-text animation`, `shadcn`, `component registry`, `three.js scene`, `threejs scene`, `webgl scene`, `voxel scene`, `voxel art scene`, `accessibility`, `wcag`, `lighthouse`, `core web vitals`, `make it beautiful`, `make it premium`, `make it less ai`, `ai-looking ui`, `ai slop ui`, `slop ui`, `looks like ai slop`, `look like ai slop`, `feels like ai slop`, `screams ai slop`, `generic ui`, `broken layout`, `layout broken`, `frontend qa`, `frontend layout`, `tui design`, `terminal ui design`, `tui layout`, `フロントエンド`, `ランディングページ`, `レスポンシブ対応`, `デザインシステム`, `画面のUI実装`, `スムーススクロール`, `スクロールアニメーション`, `パララックス`, `チャートのスタイル`, `チャートスタイル`, `フッターデザイン`, `ネオブルータリズム`, `ロゴマーキー`, `프론트엔드`, `웹 ui`, `웹 화면`, `랜딩페이지`, `레이아웃`, `레이아웃 깨짐`, `깨짐`, `디자인 자연스럽게`, `자연스러운 디자인`, `화려하게`, `고급스럽게`, `부드러운 스크롤`, `스크롤 부드럽게`, `스크롤 애니메이션`, `패럴랙스`, `ai 티`, `ai틱`, `ai 틱`, `반응형`, `접근성`, `차트 스타일`, `차트 스타일링`, `차트 테마`, `푸터 디자인`, `네오브루탈리즘`, `로고 마키`, `마키 애니메이션`, `스플릿 텍스트`, `сделай лендинг`, `одностраничный лендинг`, `свёрстай страницу`, `сделай веб страницу`, `веб интерфейс`, `анимация на сайте`, `сделай сайт`, `анимацию при скролле`, `сделать веб страницу`, `лендинга`, `на лендинге`, `вёрстку сайта`, `сверстать страницу`, `сделай лэндинг`, `前端`, `落地页`, `响应式布局`, `设计系统`, `平滑滚动`, `滚动动画`, `视差滚动`, `图表样式`, `页脚设计`, `新粗野主义`, `跑马灯`, `bangun antarmuka UI frontend`, `bantu bikin landing page`, `rapikan tampilan frontend`, `buat halaman yang responsif`, `implementasikan desain UI`, `rancang antarmuka terminal`, `tambahkan animasi scroll`, `desain ulang tampilan dashboard`, `xây dựng giao diện frontend`, `giúp tạo landing page`, `cải thiện giao diện frontend`, `tạo trang có bố cục responsive`, `thực hiện thiết kế UI`, `thiết kế giao diện terminal`, `thêm hiệu ứng scroll`, `thiết kế lại giao diện dashboard`\n\n## Catalog Metadata\n\nCategory: `materials`\nPhase: `frontend-design`\nQuality tier: `frontend-design-gated`\nReasoning demand: `standard`\n\nQuality bar:\n\n- Name the product goal, audience, target surfaces, routes, states, and visual quality bar.\n- Hold the named bar: what a senior product designer at a top-tier product company (the Linear\u002FStripe\u002FSupabase class) would sign off on — technically clean but flat output fails it. Load `references\u002Ftaste-foundations.md`, name one primary taste direction, and reject the anti-slop patterns it lists.\n- Name the model's own default aesthetic before inheriting it — the editorial prior of cream grounds, serif display faces, and muted terracotta accents suits editorial, portfolio, and hospitality briefs and is a failure mode on dashboards, developer tools, fintech, and data-dense UIs. Treat a generic negation (\"don't make it look AI\", \"make it minimal\") as unactionable: an override counts only when it carries concrete tokens, a hex palette and a typeface stack recorded in DESIGN.md. Run the review prompts in `references\u002Ftaste-foundations.md` over framework blue, glass and gradient surfaces, default UI typefaces, bounce easing, blanket shadows, eyebrow\u002Ftitle\u002Fdescription stuffing, uniform column grids, and CJK body under the 14px Korean floor.\n- When the target surface is a terminal UI (TUI), load `references\u002Ftui-craft.md` and hold the same bar there: default widgets are scaffolding, not finished UI; borders spent sparingly with spacing and a muted-color ladder doing the hierarchy; one named terminal aesthetic; verification rendered at 80x24 and 120x40 minimum with the pasted output as the screenshot-equivalent.\n- Use references and domain fit to avoid generic AI-looking frontend output; when the user supplies a visual reference, load `references\u002Freference-token-extraction.md` and extract tokens into the contract instead of eyeballing.\n- Prepare a concrete design-system contract before implementation handoff: load `references\u002Fdesign-system-contract.md` and write DESIGN.md before the first component — no component code before the contract exists. A new DESIGN.md is Google's DESIGN.md format (YAML token front matter, its sections in its order) plus OMH's own sections; a file in OMH's earlier numbered layout stays valid and is converted only when the user asks. When Hermes' bundled `design-md` skill is available, author, lint, diff, or export a file in the format through it, never a file in the earlier layout; lint is evidence only from a run that executed, otherwise `not_observed`.\n- Query the local design reference data before fixing tokens: `omh design data --kind palette|font|ux --context \u003Cproduct context>` returns curated palettes, font stacks with CJK notes, and UX guidelines offline. Those rows inform DESIGN.md; the contract, not the query, still gates the code.\n- Scroll-driven motion is a decision with a bill: load `references\u002Fscroll-motion-libraries.md`, take the native path (CSS `scroll-behavior`, scroll-driven animations, `IntersectionObserver`, scroll-snap) unless one interpolated scroll position feeds several consumers, and when a library is chosen (Lenis is the reviewed record) name its reduced-motion branch, anchors, nested scroll, teardown, and INP budget in the contract.\n- Copied component source is the project's to fix: before adopting from a shadcn-style registry, load `references\u002Fcomponent-registry-adoption.md` (license, dependencies, reduced motion, ARIA, keyboard\u002Ftouch, token mapping, one hero effect per view). Theme charts through tokens, not config literals: load `references\u002Fchart-styling.md`.\n- A 3D or canvas scene (WebGL, a three.js-style engine, a voxel world) is judged on its first frame: load `references\u002Frendered-scene-craft.md`, boot on the view the scene's own title and copy promise, light it with a warm-or-cool key, a sky fill, explicit tone mapping, shadows, and fog, and make every small animated object read as what it is. A clean console is not a finished scene.\n- For first-time UI creation, name the initial generation branch, reference direction, reusable primitives, state coverage, and required visual QA path.\n- Cover responsive layout, empty\u002Floading\u002Ferror states, hover\u002Ffocus\u002Factive states, CJK text, accessibility, and performance expectations.\n- State performance as a budget, not an adjective: load `references\u002Fweb-vitals-budgets.md`, name one metric with its published bar (LCP, INP, CLS), the device and network class it is judged on, the route and load shape, and the baseline captured under that same profile - before the change. A budget chosen after seeing the result describes what happened instead of gating it.\n- Attribute before optimizing: name the LCP element and its dominant phase, the interaction that produced the worst INP and where the time went, or the node that shifted and what moved above it. A list of optimizations with no attribution is folklore, and a change that improved a different element than the one attributed did not fix the metric.\n- Keep field and lab apart: a p75 claim needs field data, a lab audit is a diagnostic sample on one device profile, and a lab pass is never a statement about real users.\n- After implementation lands on a web surface, load `references\u002Fscreenshot-loop.md` and require the screenshot iteration loop live-environment-first: capture the running UI at 1440\u002F768\u002F375px, compare against the supplied target or DESIGN.md, list every difference triaged Blocker\u002FHigh\u002FMedium\u002FNit with its capture attached, fix, and recapture until the difference list is empty.\n- Prefer native UI controls, stable dimensions, and realistic content over decorative cards, blobs, and placeholder-heavy screens.\n- Keep implementation, browser verification, accessibility\u002Fperformance checks, visual QA, and deployment as observed-only evidence.\n\nRequired inputs:\n\n- target app, page, route, or component\n- audience and primary user task\n- existing design system or missing-system gap\n- style references or quality bar\n- initial generation mode or redesign mode\n- DESIGN.md or design-system source of truth when available\n- framework\u002Fstack when known\n- routes, states, breakpoints, and locale\u002FCJK risks\n- accessibility and performance constraints\n- observed browser evidence for completion claims\n\nExpected outputs:\n\n- frontend_design_brief\u002Fv1\n- frontend_initial_generation_contract\u002Fv1 when greenfield\n- design_system_contract\u002Fv1\n- design_reference_selection\u002Fv1\n- reference_packet\u002Fv1 when supplied\n- frontend_route_state_matrix\u002Fv1\n- frontend_component_state_inventory\u002Fv1\n- frontend_implementation_handoff\u002Fv1\n- accessibility_performance_expectations\u002Fv1\n- visual_qa_required\u002Fv1\n- observed_browser_evidence\u002Fv1 when observed\n\nArtifact expectations:\n\n- frontend_design_brief\u002Fv1 when prepared\n- frontend_initial_generation_contract\u002Fv1 declares DESIGN.md\u002Fdesign-system work, reference lane, token extraction, reusable primitives, and visual QA path before new UI code\n- design_system_contract\u002Fv1 with layout, spacing, typography, color, component, motion, and responsive rules\n- design_reference_selection\u002Fv1 names supplied references or the domain-fit style direction and explicitly avoids copying third-party logos, assets, or brand copy\n- frontend_route_state_matrix\u002Fv1 with pages, states, viewports, CJK\u002Flocale, empty\u002Floading\u002Ferror, and interaction states\n- frontend_component_state_inventory\u002Fv1 with default, hover, focus, active, disabled, loading, empty, and error states for reusable primitives\n- frontend_implementation_handoff\u002Fv1 for the selected executor\u002Fruntime\n- browser screenshots, accessibility reports, Lighthouse\u002FCore Web Vitals, and visual QA only when observed\n\nSafety rules:\n\n- Do not claim implementation, browser verification, deployment, Lighthouse, accessibility pass, or visual QA from a prepared frontend brief.\n- Reject generic AI-looking UI: one-note palettes, weak hierarchy, cramped cards, ungrounded gradients, decorative filler, and placeholder-heavy copy.\n- Require a design-system contract before broad visual changes.\n- For greenfield UI, require an initial generation contract before implementation handoff so the first generated screen has tokens, references, primitives, states, and QA expectations.\n- Require fresh rendered evidence after the last UI edit before PASS.\n- Do not hand off a smooth-scroll integration without its reduced-motion branch, keyboard\u002Fanchor\u002Fnested-scroll behavior, and teardown named; a `respectReducedMotion` option covers the library own scroll, never the animations the project wrote.\n- Do not hand off a copied registry component or text effect without its license read at the source and its reduced-motion branch; decorative duplicates and split characters are `aria-hidden`, and a marquee gets a pause reachable by keyboard and touch.\n- Do not report a Core Web Vitals number without the device class, route, and load shape it was measured under; a figure from a different profile than the baseline is not a comparison.\n- For Korean\u002FCJK text, clipped glyphs, awkward line breaks, orphan particles, tiny copy, and overflow block visual QA.\n- Do not call external design, image, browser, LLM, or network services from OMH core.\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,"compatibility":32},{"hermes":24},{"role":25,"tags":26,"phase":30,"category":29,"quality_tier":31},"operator",[27,28,29],"workflow","oh-my-hermes","materials","frontend-design","frontend-design-gated","Requires the omh CLI on PATH (pip install oh-my-hermes).","main","4c174e06a831864e98c30f630a7aa6c04738b094","skills\u002F_intake\u002Fgithub\u002Frlaope\u002Foh-my-hermes\u002Fomh-frontend","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":40,"prompt":50,"zipAvailable":51},[41,44,47],{"tool":42,"command":43},"npx","npx skills add mhyahya854\u002FAI-Second-Brain_Universal-Rules --skill omh-frontend",{"tool":45,"command":46},"bunx","bunx skills add mhyahya854\u002FAI-Second-Brain_Universal-Rules --skill omh-frontend",{"tool":48,"command":49},"pnpm","pnpm dlx skills add mhyahya854\u002FAI-Second-Brain_Universal-Rules --skill omh-frontend","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Frlaope\u002Foh-my-hermes\u002Fomh-frontend\u002FSKILL.md",true,[53,59,63,67,71,75,79,83,87,91],{"path":54,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":57,"sourceHtmlUrl":58},"references\u002Fchart-styling.md","REFERENCE","参考文档",5026,"https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Frlaope\u002Foh-my-hermes\u002Fomh-frontend\u002Freferences\u002Fchart-styling.md",{"path":60,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":61,"sourceHtmlUrl":62},"references\u002Fcomponent-registry-adoption.md",8923,"https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Frlaope\u002Foh-my-hermes\u002Fomh-frontend\u002Freferences\u002Fcomponent-registry-adoption.md",{"path":64,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":65,"sourceHtmlUrl":66},"references\u002Fdesign-system-contract.md",12739,"https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Frlaope\u002Foh-my-hermes\u002Fomh-frontend\u002Freferences\u002Fdesign-system-contract.md",{"path":68,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":69,"sourceHtmlUrl":70},"references\u002Freference-token-extraction.md",2835,"https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Frlaope\u002Foh-my-hermes\u002Fomh-frontend\u002Freferences\u002Freference-token-extraction.md",{"path":72,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":73,"sourceHtmlUrl":74},"references\u002Frendered-scene-craft.md",3980,"https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Frlaope\u002Foh-my-hermes\u002Fomh-frontend\u002Freferences\u002Frendered-scene-craft.md",{"path":76,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":77,"sourceHtmlUrl":78},"references\u002Fscreenshot-loop.md",4907,"https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Frlaope\u002Foh-my-hermes\u002Fomh-frontend\u002Freferences\u002Fscreenshot-loop.md",{"path":80,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":81,"sourceHtmlUrl":82},"references\u002Fscroll-motion-libraries.md",7119,"https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Frlaope\u002Foh-my-hermes\u002Fomh-frontend\u002Freferences\u002Fscroll-motion-libraries.md",{"path":84,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":85,"sourceHtmlUrl":86},"references\u002Ftaste-foundations.md",10096,"https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Frlaope\u002Foh-my-hermes\u002Fomh-frontend\u002Freferences\u002Ftaste-foundations.md",{"path":88,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":89,"sourceHtmlUrl":90},"references\u002Ftui-craft.md",6678,"https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Frlaope\u002Foh-my-hermes\u002Fomh-frontend\u002Freferences\u002Ftui-craft.md",{"path":92,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":93,"sourceHtmlUrl":94},"references\u002Fweb-vitals-budgets.md",3688,"https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Frlaope\u002Foh-my-hermes\u002Fomh-frontend\u002Freferences\u002Fweb-vitals-budgets.md",[96,104,112,120,127,134],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":100,"sourceHtmlUrl":101,"categories":102,"keywords":103,"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":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":108,"sourceHtmlUrl":109,"categories":110,"keywords":111,"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":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":116,"sourceHtmlUrl":117,"categories":118,"keywords":119,"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":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":126,"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":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":133,"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":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":140,"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",[],[]]