component-input

Generate accessible React Input components with ARIA state and validation.

Updated Apr 21, 2026
One-click install
npx skills add https://github.com/shawn-sandy/agentic-acss-plugins --skill component-input
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: component-input
Source: https://github.com/shawn-sandy/agentic-acss-plugins/tree/main/plugins/acss-kit/skills/component-input
Command: npx skills add https://github.com/shawn-sandy/agentic-acss-plugins --skill component-input

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill solves the problem of creating accessible text inputs with consistent validation, error/hint wiring, and predictable controlled versus uncontrolled behavior without hand-writing repetitive aria and styling logic.

Core Features & Use Cases

  • Accessible validation & messaging: Generates an input that supports validationState (none/valid/invalid) plus errorMessage and hintText linked via aria-describedby.
  • Disabled/read-only patterns: Implements the kit-builder accessible disabled behavior (aria-disabled) and supports readOnly with the correct ARIA attributes.
  • Controlled/uncontrolled support: Works with value/defaultValue patterns while handling Enter-key behavior via onEnter.

Quick Start

Tell the AI to run the component-input skill to create an fpkit-style Input by providing the input type (e.g., email or number), the required label id, whether it should be controlled (value/onChange) or uncontrolled (defaultValue), and the validation/error state behavior you want.

Frequently Asked Questions about component-input

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

FAQPage Schema
How do I generate accessible React input components with proper ARIA validation states?

You can generate accessible React input components by running the skill with your desired input type, label id, and validation state. It produces input.tsx files with consistent aria-describedby wiring for error and hint messages.

How do I wire aria-describedby for error messages and hint text in React forms?

Wiring aria-describedby for error and hint text is handled automatically by the generated input component. You provide the errorMessage and hintText props, and the component links them via aria-describedby for screen reader accessibility.

How do I build a controlled React input that handles the Enter key?

Building a controlled React input with Enter key handling requires passing the value and onChange props during generation. The component supports an onEnter keyboard interaction to execute logic when the Enter key is pressed.

Does this input component generation support both disabled and read-only accessibility patterns?

Disabled and read-only accessibility patterns are fully supported during component generation. It implements accessible disabled behavior using aria-disabled and applies the correct ARIA attributes for readOnly states.

Can I use this to scaffold React inputs with SCSS styling modules?

You can use this skill to scaffold React inputs with SCSS styling modules. It generates both the input.tsx component logic and the accompanying input.module.scss file following fpkit/acss styling patterns.