frontend
starsforks
How to install frontend?
rlaope/oh-my-hermes/frontend
$npx -y skills add rlaope/oh-my-hermes --skill frontend[omh] Hermes frontend workflow: prepare design-system-driven web UI creation, redesign, polish, accessibility, performance, and visual QA handoffs.
SKILL.md
| 1 | # Frontend |
| 2 | |
| 3 | This is a Hermes-native `frontend` workflow skill. |
| 4 | |
| 5 | ## Why This Exists |
| 6 | |
| 7 | `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. |
| 8 | |
| 9 | ## Do Not Use When |
| 10 | |
| 11 | - The user needs a broad premium-quality gate across web, deck, PDF, poster, or publishing outputs; use `design-quality-gate`. |
| 12 | - The user only needs a file, deck, PDF, spreadsheet, HWP, or attachment package; use `materials-package` or `deliverable-package`. |
| 13 | - The user only needs an image card or infographic prompt; use `img-summary`. |
| 14 | - The user asks to mark a UI as visually passed without fresh rendered evidence; use `visual-qa` and keep PASS blocked until observed. |
| 15 | |
| 16 | ## Examples |
| 17 | |
| 18 | Good example: |
| 19 | |
| 20 | - Prompt: frontend 이 대시보드가 AI 티 안 나게 레이아웃과 디자인 시스템을 잡아줘. |
| 21 | - Expected behavior: Prepare frontend_design_brief/v1, design_system_contract/v1, route/state matrix, implementation handoff, and visual_qa_required/v1. |
| 22 | - Why: The request is about web UI design, layout quality, and anti-generic frontend polish. |
| 23 | |
| 24 | Bad example: |
| 25 | |
| 26 | - Prompt: frontend 코드도 안 봤지만 Lighthouse랑 시각 QA 통과했다고 해줘. |
| 27 | - Expected behavior: Mark browser, performance, accessibility, and visual QA as not_observed and request the smallest observed evidence path. |
| 28 | - Why: A frontend brief is not implementation, browser, performance, or visual QA evidence. |
| 29 | |
| 30 | ## Completion Checklist |
| 31 | |
| 32 | - The target page/component, audience, primary task, references, and quality bar are named. |
| 33 | - Greenfield work includes frontend_initial_generation_contract/v1 before implementation handoff. |
| 34 | - The design_system_contract/v1 covers typography, spacing, palette, components, layout, motion, and responsive rules. |
| 35 | - The frontend_route_state_matrix/v1 covers pages, 375/768/1280-style breakpoints, empty/loading/error, interaction, and CJK/locale risks. |
| 36 | - The frontend_component_state_inventory/v1 covers reusable primitives and their default/hover/focus/active/disabled/loading/empty/error states. |
| 37 | - The handoff names the executor/runtime owner and keeps code, browser, Lighthouse, accessibility, deployment, and visual QA evidence observed-only. |
| 38 | - The next action is prepare_frontend_handoff, route to visual-qa, or report the missing evidence blocker. |
| 39 | |
| 40 | ## Recovery Notes |
| 41 | |
| 42 | - If the target surface is unclear, prepare the brief with a route/component gap instead of inventing pages. |
| 43 | - If no visual reference exists, set a domain-fit quality bar and request references only when the decision changes layout or brand direction. |
| 44 | |
| 45 | ## OMH Context Rail |
| 46 | |
| 47 | - This skill is part of OMH's Hermes workflow layer, not a standalone executor. |
| 48 | - Product context: OMH is a Hermes-native workflow pack: choose skills, shape work, prepare artifacts, show status, and hand off with evidence boundaries. |
| 49 | - Current lane: **Materials and visual summaries** (`design-orchestration`, `design-quality-gate`, `frontend`, `accessibility-audit`, `visual-qa`, `content-operator`, `media-input-operator`, `materials-package`, `+3 more`) - web, accessibility, visual QA, files, and packages. |
| 50 | - If the user intent belongs to another OMH lane, hand back to `oh-my-hermes` or name the adjacent workflow instead of force-fitting this skill. |
| 51 | - Cross-skill context: every OMH skill: match lane; generic tool can render or execute. |
| 52 | - Generic-tool checkpoint: image->img-summary; frontend->frontend/a11y/visual-qa; paper->paper-learning; content->content-operator; media->media-input-operator; file->materials-package; search->web-research; live->live-info-operator; audit->workspace/production/security; failures->build-failure; verify->verification-gate; code->codegraph/onboarding/ultraprocess. |
| 53 | - Coverage: Every generated workflow skill carries this rail. |
| 54 | - Normal users talk to Hermes; OMH CLI is infra. |
| 55 | - Boundary: Prepared OMH routing, cards, handoffs, or artifacts are not observed execution, image generation, delivery, review, CI, merge-readiness, or merge evidence. |
| 56 | |
| 57 | ## Use When |
| 58 | |
| 59 | Use when Hermes should shape or improve a web/frontend surface before implementation: layout, design system, responsive states, accessibility, performance, motion, and anti-generic visual quality. |
| 60 | |
| 61 | Strong routing signals: `frontend`, `front-end`, `front end`, `frontend skill`, `web ui`, `ui ux`, `ui/ux`, `landing page`, `web app layout`, `responsive layout`, `responsive design`, `design system`, `component polish`, `layout polish`, `visual polish`, `styling`, `animation`, `motion design`, `accessibility`, `wcag`, `lighthouse`, `core web vitals`, `make it beautiful`, `make it premium`, `make it less ai`, |
People who liked this also viewed
6 picksType
- web-design-guidelinesReview UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".SkillsJul 2026
- lark-slides飞书幻灯片：创建和编辑幻灯片。创建演示文稿、读取幻灯片内容、管理幻灯片页面（创建、删除、读取、局部替换）。当用户需要创建或编辑幻灯片、读取或修改单个页面时使用。当用户给出 doubao.com 的 /slides/ URL/token 时，也应直接使用本 skill，不要因为域名不是飞书而回退到 WebFetch；路由依据是 URL 路径模式和 token，而不是域名。不负责：云文档内容编辑（走 SkillsJul 2026
- design-taste-frontendTaste-Skill - gives your AI good taste. stops the AI from generating boring, generic slop SkillsJul 2026
- ui-ux-pro-maxUI/UX design intelligence for web and mobile. Searchable local database with 84 styles, 192 color palettes, 74 font pairings, 192 product types, 98 UX guidelines, 104 icon entries, 16 GSAP motion presSkillsJul 2026
- caveman-helpQuick-reference card for all caveman modes, skills, and commands. One-shot display, not a persistent mode. Trigger: /caveman-help, "caveman help", "what caveman commands", "how do I use caveman".SkillsJul 2026
- codebase-designShared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-nSkillsJul 2026
