preact_ui

Create accessible Preact UI components with JSX/TSX patterns and automated accessibility checks.

1|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/caraya/agent-skills --skill preact-ui-caraya
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: preact_ui
Source: https://github.com/caraya/agent-skills/tree/main/skills/preact-ui
Command: npx skills add https://github.com/caraya/agent-skills --skill preact-ui-caraya

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines building accessible Preact UI components, eliminating guesswork in creating consistent, usable interfaces.

Core Features & Use Cases

  • Provides patterns for functional components, hooks, and state management in Preact.
  • Enforces accessibility considerations via the ui-accessibility workflow.
  • Supports scalable UI architecture with a clean file structure and design-system alignment.

Quick Start

Scaffold a new Preact component under src/components and validate accessibility using the ui-accessibility flow.

Frequently Asked Questions about preact_ui

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

FAQPage Schema
How do I create accessible Preact UI components?

Create accessible Preact UI components by applying functional component patterns, preact/hooks, and JSX/TSX syntax while running automated accessibility checks via the ui-accessibility workflow to ensure usable interfaces.

What is the best way to structure Preact hooks and state management for a design system?

Structure Preact hooks and state management by applying scalable component patterns and clean file architecture, ensuring your UI components conform to design-system alignment and accessibility requirements.

Can I use this approach to refactor existing Preact components for accessibility?

Refactor existing Preact components for accessibility by applying functional component patterns and validating them with automated accessibility checks to ensure modern frontend conformance.

Does this workflow support TypeScript and TSX patterns for Preact?

Yes, the workflow supports TypeScript and TSX patterns for Preact, satisfying requirements for functional components, preact/hooks usage, and integration with the ui-accessibility workflow.

When do I need automated accessibility checks for Preact interfaces?

You need automated accessibility checks for Preact interfaces during new component development, refactors, and design-system conformance to eliminate guesswork in creating consistent, usable interfaces.

Why does my Preact UI component fail design-system conformance?

Preact UI components may fail design-system conformance if they lack proper functional component patterns, preact/hooks usage, or fail automated accessibility validation within the ui-accessibility workflow.