ui-components

Manage solid-ui component library initialization, theming, and modifications via CLI workflows.

Updated Sep 21, 2025
One-click install
npx skills add https://github.com/hmjn023/solid-imager --skill ui-components-hmjn023
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ui-components
Source: https://github.com/hmjn023/solid-imager/tree/main/.opencode/skills/ui-components
Command: npx skills add https://github.com/hmjn023/solid-imager --skill ui-components-hmjn023

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams manage a centralized Solid UI component library used across the project, enabling consistent initialization, component creation, and theming within the server workspace.

Core Features & Use Cases

  • Initialize the solid-ui setup from the server context.
  • Add new UI components or modify existing ones under apps/server/src/components/ui/.
  • Apply coherent theming and styling across the component library to ensure visual consistency.

Quick Start

Initialize the solid-ui workflow from the server workspace and use the CLI to add or adjust components as needed.

Frequently Asked Questions about ui-components

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

FAQPage Schema
How do I initialize a solid-ui component library within a server workspace?

To initialize the solid-ui component library, trigger the CLI-driven workflow from the server context to set up the directory structure under apps/server/src/components/ui/ for centralized management.

What is the best way to add new UI components to a SolidJS project?

The best way to add new UI components is using the CLI-driven workflow, which performs directory structure checks and places new components directly under apps/server/src/components/ui/.

Can I apply consistent theming across my SolidJS component library?

Yes, you can apply coherent theming and styling across the solid-ui component library to ensure visual consistency across all components located within the server workspace directory structure.

Does this UI component workflow require any specific dependencies to run?

No specific external dependencies are required to run this workflow, as it relies on deterministic CLI-driven processes and directory structure checks within the server workspace itself.

Why should I use a CLI-driven workflow for front-end component maintenance?

A CLI-driven workflow for front-end component maintenance provides deterministic processes for initialization, addition, and modification, reducing manual errors when extending the UI library.

What are the limitations of modifying existing solid-ui components in the server workspace?

Modifications are constrained to the apps/server/src/components/ui/ directory path, meaning this workflow applies deterministic checks only within the server workspace and does not manage components outside this structure.