Skip to content
Skills Library
Programming · Building & coding

frontend-patterns

/frontend-patterns

Frontend development patterns and best practices. Use for component architecture, state management, CSS patterns, accessibility, performance optimization, and design system integration.

Licence
MIT
Last repository change
16.10.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 16.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Frontend development patterns and best practices. Use for component architecture, state management, CSS patterns, accessibility, performance optimization, and design system integration.

Original author description

Frontend development patterns and best practices. Use for component architecture, state management, CSS patterns, accessibility, performance optimization, and design system integration.

How it works

  1. 1. Component Architecture
  2. 2. State Management
  3. 3. CSS Patterns
  4. 4. Performance Optimization
  5. 5. Accessibility (A11y)
  6. 6. Testing
  7. 7. Design System Integration
  8. 8. SEO
Original SKILL.md headings · 44 lines, 382 words
SKILL.md preview
---
name: frontend-patterns
description: >
  Frontend development patterns and best practices. Use for component architecture, state management, CSS patterns, accessibility, performance optimization, and design system integration.
---

# Frontend Patterns

## 1. Component Architecture
- **Atomic Design**: Organize components into Atoms, Molecules, Organisms, Templates, and Pages.
- **Compound Components**: Use context to share implicit state between parent and child components (e.g., `<Select>`, `<Select.Option>`).
- **Render Props**: Share code between React components using a prop whose value is a function.
- **Custom Hooks**: Extract stateful logic from a component so it can be tested independently and reused.

## 2. State Management
- **Local State**: Use `useState` or `useReducer` for state that is isolated to a single component or small subtree.
- **Global State**: Use context API, Redux, Zustand, or Jotai for application-wide state.
- **Server State**: Use React Query, SWR, or Apollo Client to manage asynchronous data fetching, caching, synchronization, and error handling.
- **Form State**: Use libraries like React Hook Form or Formik for complex forms.

## 3. CSS Patterns
- **Utility-first CSS**: Tailwind CSS conventions for rapid styling and consistency.
- **CSS Modules**: Scope CSS locally by default to avoid class name collisions.
- **Styled-components**: Write actual CSS in JavaScript, leveraging tagged template literals.

## 4. Performance Optimization
- **Code Splitting**: Use `React.lazy` and Suspense to lazy load components.
- **Memoization**: Use `React.memo`, `useMemo`, and `useCallback` to prevent unnecessary re-renders.
- **Virtual Scrolling**: Render only the visible items in a long list to save memory and processing time.

## 5. Accessibility (A11y)
- **WCAG 2.1 Checklist**: Follow guidelines for contrast, text resizing, and keyboard navigability.
- **ARIA Patterns**: Use ARIA attributes appropriately to enhance semantics for screen readers.
- **Focus Management**: Ensure logical tab order and visible focus states.

## 6. Testing
- **Component Testing**: Use React Testing Library to test components from the user's perspective.
- **Visual Regression**: Compare screenshots of components to detect unintended visual changes (e.g., Chromatic, Percy).
- **E2E Testing**: Automate browser actions to test critical user flows (e.g., Playwright, Cypress).

## 7. Design System Integration
- **Token Consumption**: Map design tokens (colors, typography, spacing) to CSS variables or a theme provider.
- **Component Composition**: Build complex UIs by composing simpler, reusable design system components.

## 8. SEO
- **Meta Tags**: Use next/head or react-helmet for dynamic meta tags.
- **Structured Data**: Inject JSON-LD to help search engines understand page content.
- **SSR/SSG**: Leverage Next.js or Remix for server-side rendering or static site generation.

Versions

RepositoryScoreLicence
This page · andersonlimahw/lemon-ai-hub90MIT
Sanit-mann/The-Insectoids100MIT
rommapp/romm100AGPL-3.0
tadokoro-ryusuke/cc-plugins100MIT
pekral/cursor-rules100MIT
bybren-llc/safe-agentic-workflow100MIT
bybren-llc/safe-agentic-workflow100MIT
tranhieutt/software_development_department100MIT
affaan-m/ECC95MIT

Database snapshot: 13.11.2026 · package version ea62a847f470 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90frontend
    Frontend patterns: component design, state management, performance, accessibility. Use when building web frontends, components, or client-side apps.
  • 100frontend-web
    Modern web development patterns for React, Vue, and vanilla JS including component architecture, state management, and performance. Use when building web UIs, optimizing frontend performance, or implementing accessibility.
  • 100react-patterns
    Frontend development patterns for React, Next.js, state management, performance optimization, and UI best practices. Use when building or reviewing React or Next.js components, state, or render performance.
  • 100react-code-review
    Provides comprehensive code review capability for React applications, validates component architecture, hooks usage, React 19 patterns, state management, performance optimization, accessibility compliance, and TypeScript integration. Use when reviewing React code changes, before…
  • 100component-design
    Create or restructure a UI component — architecture, component patterns, accessibility, design-system rules. Use when adding a new component, splitting a large one, or making one reusable. App-level work belongs to frontend-ui-engineering.
  • 100react-frontend-patterns
    React 19+, TypeScript, Tailwind CSS, shadcn/ui component patterns, accessibility, forms, state management. Use when building or reviewing React components, pages, or frontend architecture.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.