frontend-engineering

Implements component architecture, state management, API integration, responsive layouts, and frontend testing patterns.

10|2|Updated May 6, 2026
One-click install
npx skills add https://github.com/jcrabapple/hermes-skills --skill frontend-engineering-jcrabapple
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: frontend-engineering
Source: https://github.com/jcrabapple/hermes-skills/tree/main/frontend-engineering
Command: npx skills add https://github.com/jcrabapple/hermes-skills --skill frontend-engineering-jcrabapple

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Building the user-facing layer of web applications requires consistent decisions across components, state, data fetching, layout, performance, and testing. This Skill provides a framework-agnostic frontend engineering methodology with concrete patterns and decision matrices so implementation choices are deliberate rather than ad hoc. ## Core Features & Use Cases - Component Architecture: Composition patterns (atomic design, compound components, render props), props/state interface design, and accessibility fundamentals for every component. - State & API Integration: State classification (local, shared, server, URL, form), data fetching patterns, caching strategy, auth token flows, and real-time updates via WebSocket or SSE. - Responsive Layout & Testing: Grid vs Flexbox vs Container Queries decision matrix, content-driven breakpoints, cross-device testing with Playwright emulation, component testing with Vitest and Testing Library, visual regression, and axe-core accessibility testing. - Use Case: When building a dashboard page, use this Skill to design the component tree, choose React Query for server state, implement a responsive card grid with container queries, and add Playwright integration tests with axe-core accessibility checks. ## Quick Start Use the frontend-engineering skill to design the component architecture and state management approach for a responsive product listing page with integration tests.

Frequently Asked Questions about frontend-engineering

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I choose between CSS Grid and Flexbox for layout?▼

Use CSS Grid for two-dimensional page-level layouts where rows and columns matter simultaneously, and Flexbox for one-dimensional component alignment like navbars and toolbars. Container queries handle component-level responsiveness independent of the viewport.

How to manage state in a frontend application?▼

Classify state first: local UI state stays in the component, server state belongs in a cache layer like React Query or SWR, URL state lives in search params, and only truly shared state goes in a global store. Co-locate state with the components that need it.

Playwright vs Cypress for frontend integration testing?▼

Playwright supports Chromium, Firefox, and WebKit with native multi-tab handling, device emulation, and parallel sharding, making it the default for new projects. Cypress runs inside the browser and remains viable for teams already invested in its ecosystem.

Does automated accessibility testing catch all WCAG violations?▼

Automated tools like axe-core and Lighthouse catch roughly 30-40% of WCAG violations, such as missing alt text, labels, and contrast issues. Logical reading order, keyboard flow, and screen reader behavior still require manual testing.

What are good Core Web Vitals targets for frontend performance?▼

Target LCP at or below 2.5 seconds, INP at or below 100 milliseconds, and CLS at or below 0.1. Achieve these with route-level code splitting, dynamic imports, image optimization, memoization, and list virtualization.