- Home
- Skills
- Shotaiuchi
- Dotclaude
- Feature Ui
feature-ui_skill
- Shell
0
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill shotaiuchi/dotclaude --skill feature-ui- SKILL.md1.7 KB
Overview
This skill implements UI components, layouts, interactions, animations, responsive behavior, and accessibility for new features. It provides a practical checklist and verification approach to ensure components are reusable, performant, and accessible. Use it to produce consistent, production-ready UI pieces that match design intent and development standards.
How this skill works
I inspect component structure, props, state, and separation of concerns to confirm single responsibility and reusability. I validate layouts across breakpoints, spacing, typography, and overflow behavior against design specs. I test interactions, loading states, transitions, and gesture handling for performance and feedback. I run accessibility checks for semantics, ARIA, keyboard navigation, contrast, and screen reader compatibility.
When to use it
- Building new UI components for features or pages
- Converting designs from designers into code
- Auditing existing components for accessibility or responsiveness
- Adding interactions, animations, or loading states
- Preparing components for reuse in a shared library
Best practices
- Define clear component hierarchy and composition patterns before coding
- Type and document all props/inputs and separate container vs presentational logic
- Keep components single-responsibility and manage state locally or via explicit stores
- Follow design tokens for consistent typography, spacing, and colors
- Test responsivity across breakpoints and validate overflow/scroll scenarios
- Include keyboard, focus, ARIA attributes, and screen reader announcements early
Example use cases
- Implementing a new modal/dialog with focus management, animations, and ARIA roles
- Building a responsive card grid with consistent spacing and skeleton loading states
- Creating an interactive form component that validates, announces errors, and manages focus
- Converting a prototype interaction (drag/swipe) into a performant, touch-friendly component
- Refactoring a component for reuse and adding docs and typed props for a component library
FAQ
Use Complete, Partial, Blocked, or Skipped to reflect implementation progress and blockers.
How do I verify accessibility quickly?
Start with semantic HTML, keyboard navigation, focus order, color contrast checks, and a screen reader pass; automate where possible with linters and axe.