ui

Generates accessible UI components and web forms with configurable design constraints.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/lane2077/claude-code-harness-zh --skill ui-lane2077
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ui
Source: https://github.com/lane2077/claude-code-harness-zh/tree/main/codex/.codex/skills/ui
Command: npx skills add https://github.com/lane2077/claude-code-harness-zh --skill ui-lane2077

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Generates reusable UI components and feedback forms while enforcing accessibility, design consistency, and rapid delivery for frontend projects.

Core Features & Use Cases

  • UI component generation (hero, pricing, features, header) with responsive behavior.
  • Accessible feedback forms and user input interfaces ready for integration.
  • Enforcement of design constraints from reference documents to maintain branding.

Quick Start

Describe your UI needs and I will generate components and forms following the project accessibility and design constraints.

Frequently Asked Questions about ui

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

FAQPage Schema
How do I generate accessible UI components with Tailwind?

Generate accessible UI components with Tailwind by applying design constraints from reference documents to produce modular, responsive primitives with keyboard accessibility for web apps.

Can I generate feedback forms that are ready for frontend integration?

Yes, you can generate accessible feedback forms ready for frontend integration that enforce design consistency and responsive behavior across different application contexts.

What is the best way to build responsive hero sections and pricing components?

The best way to build responsive hero sections and pricing components is to generate them using Tailwind-compatible primitives that enforce project accessibility and design constraints.

Does this approach support keyboard accessibility for user input interfaces?

Yes, this approach supports keyboard accessibility for user input interfaces by enforcing accessibility constraints during the generation of forms and general UI components.

How do I maintain branding consistency when creating web app components?

Maintain branding consistency when creating web app components by enforcing design constraints from reference documents during the generation of UI elements and feedback forms.

What are the limitations of generating UI components from design constraints?

Generating UI components from design constraints is limited to Tailwind-compatible primitives and general web app contexts, ensuring responsive behavior and keyboard accessibility across supported modular components.