SkillHub ClubShip Full StackFull StackFrontend

frontend-components

Imported from https://github.com/DevanB/lucidlog.

Packaged view

This page reorganizes the original catalog entry around fit, installability, and workflow context first. The original raw source lives below.

Stars

Hot score

Updated

March 20, 2026

Overall rating

C2.0

Composite score

2.0

Best-practice grade

C61.2

Install command

npx @skill-hub/cli install devanb-lucidlog-frontend-components

Repository

DevanB/lucidlog

Skill path: .claude/skills/frontend-components

Imported from https://github.com/DevanB/lucidlog.

Open repository

Best for

Primary workflow: Ship Full Stack.

Technical facets: Full Stack, Frontend.

Target audience: everyone.

License: Unknown.

Original source

Catalog source: SkillHub Club.

Repository owner: DevanB.

This is still a mirrored public skill entry. Review the repository before installing into production workflows.

What it helps with

Install frontend-components into Claude Code, Codex CLI, Gemini CLI, or OpenCode workflows
Review https://github.com/DevanB/lucidlog before adding frontend-components to shared team environments
Use frontend-components for development workflows

Works across

Claude CodeCodex CLIGemini CLIOpenCode

Favorites: 0.

Sub-skills: 0.

Aggregator: No.

Original source / Raw SKILL.md

---
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)