Automated summary
Guides the building and refining of web interfaces: component structure, responsive layout, design tokens, state handling, and baseline accessibility.
Strengths
- Runs a seven-step workflow from inventorying existing components through verification at multiple viewports
- Enforces a concrete checklist (loading/empty/error states, touch targets, focus order, 320px floor)
- Pushes reuse of design tokens instead of scattered magic numbers in styling
- Draws a clear boundary with the accessibility-audit-only skill and defers to it explicitly
Limitations
- Allowed tools are only Read, Glob, and Grep, so the skill cannot write or edit files; implementation output stays advisory
- Does not cover full visual redesign exploration, which it explicitly routes elsewhere
- Assumes an existing design system or tokens and offers little guidance on creating one from scratch
Use it when adding a new page or interactive component, or when refactoring existing UI for consistency and responsiveness.
Skip it for backend-only changes or for a standalone accessibility audit, which belongs to the frontend-ui-accessibility skill.
Security analysis
SafeThe skill declares only read-only tools (Read, Glob, Grep) and consistent with that, its body is pure guidance: a workflow, checklist, and output description for UI engineering. There are no bash/docker/network instructions, no file mutations, no credential handling, and no obfuscated or destructive commands. Listing it carries no meaningful execution risk.
No concerns found
How this analysis is madeExamples
Build a responsive account settings form with email, password, and notification toggles. Reuse our existing input and button components, define loading/empty/error states, and make sure it works down to 320px with proper labels and focus order.Our dashboard cards each use different hardcoded spacing and colors. Inventory the existing components and tokens, then refactor the cards into reusable primitives that rely on design tokens instead of magic numbers.Extend our design system to the new reports page: semantic HTML structure, a mobile-first grid layout, and a short note listing any new tokens or patterns you had to introduce.name: frontend-ui-engineering description: "Build and refine web UI—component structure, responsive layout, design tokens, state, and accessibility. Use for feature UI work beyond WCAG checks alone." allowed-tools: Read, Glob, Grep
Frontend UI Engineering
End-to-end UI implementation: structure, styling, responsive behavior, state, and accessibility. Extends frontend-ui-accessibility with architecture and design-system discipline.
When to use
- New page, form, or interactive component
- Refactoring UI for consistency or responsiveness
- Applying or extending a design system
When not to use
- Backend-only change
- Accessibility audit only (use
frontend-ui-accessibility) - Full visual redesign exploration (consider design consultation workflows)
Workflow
- Inventory — existing components, tokens, patterns to reuse
- Structure — semantic HTML; split presentational vs container components
- Layout — mobile-first breakpoints; avoid fixed widths that break small screens
- State — local vs shared; minimize prop drilling; document async/loading/error UI
- Styling — tokens (color, spacing, type); no magic numbers scattered
- A11y — keyboard, focus, labels, contrast (see
frontend-ui-accessibility) - Verify — key viewports; critical user paths; no console errors
Checklist
| Area | Check | |------|-------| | Components | Single responsibility; reusable primitives | | Responsive | Works at 320px and desktop; touch targets adequate | | Loading/empty/error | All three states designed | | Performance | Avoid unnecessary re-renders; lazy-load heavy assets | | A11y | Focus order, ARIA only when needed, form labels |
Output
- Implemented components with consistent patterns
- Brief note on new tokens or patterns added to the design system
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/frontend-ui-engineering-mrwak9ab/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/frontend-ui-engineering-mrwak9ab' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/frontend-ui-engineering-mrwak9ab/download' --output '.skill-downloads/frontend-ui-engineering-mrwak9ab/SKILL.md.part' && mv '.skill-downloads/frontend-ui-engineering-mrwak9ab/SKILL.md.part' '.skill-downloads/frontend-ui-engineering-mrwak9ab/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
Tools declared by the author (check availability in your agent): Read, Glob, Grep
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/frontend-ui-engineering-mrwak9ab/SKILL.md' && test -s '.skill-downloads/frontend-ui-engineering-mrwak9ab/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/frontend-ui-engineering' && cp -R '.skill-downloads/frontend-ui-engineering-mrwak9ab' '.claude/skills/frontend-ui-engineering'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/frontend-ui-engineering-mrwak9ab'openskills read 'frontend-ui-engineering-mrwak9ab'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/frontend-ui-engineering-mrwak9ab/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.