Automated summary
Generates UI components, landing page sections and contact forms while enforcing a design constraint set and an accessibility checklist.
Strengths
- Runs an explicit accessibility checklist (alt text, labels, keyboard navigation, contrast) before producing markup
- Applies style constraints by default and only unlocks animations, gradients or glows when the user explicitly asks for them
- Splits its references by use case (component generation, feedback forms, front-end design) so guidance stays targeted
- Ships a plain-language version of the a11y checklist aimed at non-technical vibe coders
Limitations
- Relies on external reference files (references/*.md) that are not bundled here, so actual generation rules are not visible
- Uses ${CLAUDE_SKILL_DIR} and allowed-tools frontmatter, tying it to Claude Code
- Not user-invocable (user-invocable: false), so it must be triggered indirectly
Use it when you need to quickly produce an accessible visual section, component or form inside a front-end project.
Skip it for highly expressive brand design or heavy visual effects, which require an explicit override and fall outside its default constraints.
Security analysis
SafeThe skill only instructs reading reference files and generating UI components with accessibility checks. Although Bash is listed as an allowed tool, no commands are specified or implied in the SKILL.md content. There is no destructive, exfiltrating, or obfuscated action.
No concerns found
How this analysis is madeExamples
Crée une hero section pour une landing page de SaaS avec un titre, un sous-titre, deux boutons et une capture d'écran, en respectant l'accessibilité.Build a contact form with name, email and message fields, inline error messages and full keyboard support.Génère trois cartes de tarification responsives avec un bouton d'action par carte et des états de focus visibles.name: ui description: "Builds UI components, landing page sections, hero sections, and contact forms. Use when creating front-end visual elements." when_to_use: "UI component, hero section, landing page, contact form, front-end, visual elements, feedback form" allowed-tools: ["Read", "Write", "Edit", "Bash"] user-invocable: false
UI Skills
A group of skills responsible for generating UI components and forms.
Constraint Priority and Application Conditions
- By default, apply constraints from
${CLAUDE_SKILL_DIR}/references/ui-skills.mdwith highest priority. - Apply
${CLAUDE_SKILL_DIR}/references/frontend-design.mdonly when "edgy/unique/expressive/brand-enhancing" styles are explicitly requested. - UI Skills MUST/NEVER rules are maintained by default. However, the following exceptions are permitted only when explicitly requested by the user:
- Gradients, glows, heavy decorations
- Animations (additions/enhancements)
- Custom easing
Feature Details
| Feature | Details | |---------|---------| | Constraint set | See references/ui-skills.md / references/frontend-design.md | | Component generation | See references/component-generation.md | | Feedback forms | See references/feedback-forms.md |
Execution Steps
- Apply constraint set (following priority order)
- Quality gate (Step 0)
- Classify the user's request
- Read the appropriate reference file from "Feature Details" above
- Generate according to its content
Step 0: Quality Gate (a11y Checklist)
Ensure accessibility when generating UI components:
♿ Accessibility Checklist
Generated UI should meet the following:
### Required Items
- [ ] Set alt attributes on images
- [ ] Associate labels with form elements
- [ ] Keyboard navigable (Tab for focus movement)
- [ ] Focus state is visually distinguishable
### Recommended Items
- [ ] Do not rely on color alone for conveying information
- [ ] Contrast ratio 4.5:1 or higher (text)
- [ ] Appropriate use of aria-label / aria-describedby
- [ ] Heading structure (h1 -> h2 -> h3) is logical
### Interactive Elements
- [ ] Appropriate labels on buttons ("View product details" instead of "Details")
- [ ] Focus trap for modals/dialogs
- [ ] Error messages are read by screen readers
For VibeCoders
♿ Making Designs Accessible to Everyone
1. **Add descriptions to images**
- Instead of "product image", use "red sneakers, front view"
2. **Make clickable areas keyboard-navigable too**
- Navigate with Tab key, confirm with Enter
3. **Don't rely on color alone for judgment**
- Not just red=error, but also icon+text
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/ui-components-and-forms-builder-msh3urxs/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/ui-components-and-forms-builder-msh3urxs' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/ui-components-and-forms-builder-msh3urxs/download' --output '.skill-downloads/ui-components-and-forms-builder-msh3urxs/SKILL.md.part' && mv '.skill-downloads/ui-components-and-forms-builder-msh3urxs/SKILL.md.part' '.skill-downloads/ui-components-and-forms-builder-msh3urxs/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/ui-components-and-forms-builder-msh3urxs/SKILL.md' && test -s '.skill-downloads/ui-components-and-forms-builder-msh3urxs/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/ui' && cp -R '.skill-downloads/ui-components-and-forms-builder-msh3urxs' '.claude/skills/ui'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/ui-components-and-forms-builder-msh3urxs'openskills read 'ui-components-and-forms-builder-msh3urxs'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/ui-components-and-forms-builder-msh3urxs/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.