Build reusable, composable UI components with single responsibilities, clear prop interfaces, proper state management, and minimal coupling. Use this skill when creating or editing React components (.tsx, .jsx files), when designing component APIs with props, when implementing component composition patterns, when managing local component state, when building shadcn/ui components, when creating shared UI components in resources/js/Components/, when implementing component documentation, or when...
Scanned 2/12/2026
Install to Claude Code
npx -y skills add aiskillstore/marketplace --skill frontend-components --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Frontend Components?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/aiskillstore-frontend-components)More formats (shields.io, HTML) on the badges page.
---
name: frontend-components
description: Build reusable, composable UI components with single responsibilities, clear prop interfaces, proper state management, and minimal coupling. Use this skill when creating or editing React components (.tsx, .jsx files), when designing component APIs with props, when implementing component composition patterns, when managing local component state, when building shadcn/ui components, when creating shared UI components in resources/js/Components/, when implementing component documentation, or when refactoring large components into smaller, focused pieces.
---
# Frontend Components
This Skill provides Claude Code with specific guidance on how to adhere to coding standards as they relate to how it should handle frontend components.
## When to use this skill
- When creating new React components in `.tsx` or `.jsx` files
- When editing existing components in `resources/js/Components/` or similar directories
- When designing component prop interfaces and TypeScript types
- When implementing component composition by combining smaller components
- When managing component state (useState, useReducer, etc.)
- When building or customizing shadcn/ui components
- When creating reusable UI components (buttons, cards, modals, forms, etc.)
- When refactoring monolithic components into smaller, focused pieces
- When implementing component documentation or usage examples
- When deciding between local state and lifting state up to parent components
- When defining component naming conventions
- When encapsulating component internal logic and exposing minimal APIs
## Instructions
For details, refer to the information provided in this file:
[frontend components](../../../agent-os/standards/frontend/components.md)
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!