원클릭으로
frontend-engineering
Build UIs that are fast, accessible, maintainable, and tested
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Build UIs that are fast, accessible, maintainable, and tested
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Build UIs that work for all users including keyboard navigation, screen readers, and WCAG 2.2
Design multi-agent systems with robust tool interfaces, state management, and failure handling
Build ML systems with disciplined training, evaluation, deployment, and safety practices
Design APIs that are stable, ergonomic, and evolvable
Design systems at the right scale with explicit trade-off documentation
Design services that are reliable, observable, secure, and maintainable
| name | frontend-engineering |
| description | Build UIs that are fast, accessible, maintainable, and tested |
| difficulty | senior |
| domains | ["web"] |
Frontend engineering is full-stack engineering from the network edge to the pixel. Performance, accessibility, maintainability, and security are all first-class concerns — not features to add later.
/review workflow for frontend PRsEvery component has states: loading, empty, error, populated, and edge cases. Define and implement all of them before calling it done.
See accessibility-engineering skill. Apply before visual polish.
Define before building:
Measure with Lighthouse on a representative device.
Prefer: local state → lifted state → context → global store (in that order). Only reach for global state when local state genuinely doesn't work.
Wrap sections of the UI in error boundaries. A crash in one section should not take down the whole page.