react-to-solid — shadcn-ui react-to-solid, zaidan, community, shadcn-ui, ide skills, solidjs

v1.0.0

About this Skill

Perfect for Frontend Agents needing seamless React-to-SolidJS component transformations. Core transformation engine for React-to-SolidJS conversion. Contains React-to-SolidJS mapping tables, Base UI to Kobalte/Corvu mapping, and third-party dependency mapping. Provides transformation rule

# Core Topics

carere carere
[58]
[1]
Updated: 3/17/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 7/11

This page remains useful for operators, but Killer-Skills treats it as reference material instead of a primary organic landing page.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution Locale and body language aligned
Review Score
7/11
Quality Score
44
Canonical Locale
en
Detected Body Locale
en

Perfect for Frontend Agents needing seamless React-to-SolidJS component transformations. Core transformation engine for React-to-SolidJS conversion. Contains React-to-SolidJS mapping tables, Base UI to Kobalte/Corvu mapping, and third-party dependency mapping. Provides transformation rule

Core Value

Empowers agents to convert React components to SolidJS equivalents using reusable context and transformation rules, leveraging Shadcn UI and SolidJS libraries, and providing a single source of truth for all React-to-SolidJS transformations.

Ideal Agent Persona

Perfect for Frontend Agents needing seamless React-to-SolidJS component transformations.

Capabilities Granted for react-to-solid

Converting React components to SolidJS for improved performance
Generating SolidJS equivalents for existing React applications
Debugging React-to-SolidJS transformation issues using reusable context

! Prerequisites & Limits

  • Does not perform transformations itself, only provides transformation rules
  • Requires referencing agents to apply the transformation rules
  • Specific to React-to-SolidJS transformations, not applicable to other frameworks

Why this page is reference-only

  • - The underlying skill quality score is below the review floor.

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

After The Review

Decide The Next Action Before You Keep Reading Repository Material

Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.

Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is react-to-solid?

Perfect for Frontend Agents needing seamless React-to-SolidJS component transformations. Core transformation engine for React-to-SolidJS conversion. Contains React-to-SolidJS mapping tables, Base UI to Kobalte/Corvu mapping, and third-party dependency mapping. Provides transformation rule

How do I install react-to-solid?

Run the command: npx killer-skills add carere/zaidan/react-to-solid. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for react-to-solid?

Key use cases include: Converting React components to SolidJS for improved performance, Generating SolidJS equivalents for existing React applications, Debugging React-to-SolidJS transformation issues using reusable context.

Which IDEs are compatible with react-to-solid?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for react-to-solid?

Does not perform transformations itself, only provides transformation rules. Requires referencing agents to apply the transformation rules. Specific to React-to-SolidJS transformations, not applicable to other frameworks.

How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add carere/zaidan/react-to-solid. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use react-to-solid immediately in the current project.

! Reference-Only Mode

This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

react-to-solid

Install react-to-solid, an AI agent skill for AI agent workflows and automation. Review the use cases, limitations, and setup path before rollout.

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

React-to-SolidJS Transformation Rules

Single source of truth for all React-to-SolidJS transformations in the Zaidan project. This is a KNOWLEDGE skill -- it provides transformation rules as reusable context. Agents reference these tables when converting React components to SolidJS equivalents.

IMPORTANT: This skill is a knowledge resource. It does NOT perform transformations itself. Instead, it provides the necessary rules and mappings that other transformation agents will reference when executing conversions. If user call it manually, explain what this skill covers and redirect user to the agents that will use this skill, then stop.

React-to-SolidJS Transformation Rules

AspectReact (shadcn)SolidJS (Zaidan)
Class attributeclassNameclass
Class prop typeclassName?: stringclass?: string
Props destructuring{ className, ...props }splitProps(props, ["class"])
Spread props{...props}{...others} after splitProps
Default propsDestructure defaults { x = 5 }mergeProps({ x: 5 }, props)
Conditional rendering{condition && <El />}<Show when={condition}><El /></Show>
List rendering{items.map(x => ...)}<For each={items}>{x => ...}</For>
Primitive library@base-ui/react-*@kobalte/core/*
PolymorphicasChild propas prop with PolymorphicProps
RefsforwardRef wrapperRemove (not needed in SolidJS)
Children typeReact.ReactNodeJSX.Element
Component typeReact.ComponentProps<"div">ComponentProps<"div">
Event targete.target.valuee.currentTarget.value
Utils import@/registry/bases/base/lib/utils@/lib/utils

Import Transformations

tsx
1// REMOVE (React): 2import * as React from "react" 3import { Slot } from "base-ui" 4import * as DialogPrimitive from "@base-ui/react/dialog" 5import { cn } from "@/registry/bases/base/lib/utils" 6 7// ADD (SolidJS): 8import type { ComponentProps, JSX, ValidComponent } from "solid-js" 9import { splitProps, mergeProps, Show, For } from "solid-js" 10import * as DialogPrimitive from "@kobalte/core/dialog" 11import type { PolymorphicProps } from "@kobalte/core/polymorphic" 12import { cn } from "@/lib/utils"

Advanced Transformation Patterns

Component Part Patterns WITHOUT Kobalte/Corvu Primitive

When a component part does NOT use a Kobalte or Corvu primitive, use this pattern:

tsx
1type ComponentPartProps = ComponentProps<"<html_element>"> 2 3const ComponentPart = (props: ComponentPartProps) => { 4 const mergedProps = mergeProps({ aProp: "default" } as ComponentPartProps, props); 5 const [local, others] = splitProps(mergedProps, ["aProp"]); 6 return <html_element aProp={local.aProp} {...others} />; 7}

Component Part Patterns WITH Kobalte/Corvu Primitive

When a component part uses a Kobalte or Corvu primitive, use polymorphic typing:

tsx
1import * as Primitive from "@kobalte/core/primitive"; 2 3type ComponentPartProps<T extends ValidComponent = "<html_element>"> = 4 PolymorphicProps<T, Primitive.PrimitivePartProps<T>> & 5 Pick<ComponentProps<"<html_element>">, "aProp">; 6 7const ComponentPart = <T extends ValidComponent = "<html_element>">( 8 props: ComponentPartProps<T> 9) => { 10 const mergedProps = mergeProps( 11 { aProp: "default" } as ComponentPartProps<T>, 12 props as ComponentPartProps<T> 13 ); 14 const [local, others] = splitProps(mergedProps, ["aProp"]); 15 return <Primitive.Root aProp={local.aProp} {...others} />; 16}

Reading Kobalte Documentation

When consulting Kobalte docs at https://kobalte.dev/docs/core/components/<component-name>:

  • Anatomy Section: Lists all ComponentPart elements and how to combine them
  • Rendered Elements Section: Check the "Default rendered element" column:
    • If starts with a capital letter -> no primitive used (e.g., a Kobalte sub-component)
    • If none -> no primitive used (wrapper/context provider)
    • Otherwise -> native HTML element (e.g., div, button, h3)
  • API Reference: Props, data attributes, CSS variables for each part
  • CSS Variables: Kobalte prefixes with --kb- (e.g., --kb-accordion-content-height)

Reading Corvu Documentation

When consulting Corvu docs at https://corvu.dev/docs/primitives/<component-name>:

  • Anatomy Section: Lists all ComponentPart elements with combination patterns
  • API Reference Section: Rendered elements are specified in the Props table, under the as row
  • DynamicProps: Corvu uses DynamicProps instead of Kobalte's PolymorphicProps
  • CSS Variables: Corvu prefixes with --corvu- (e.g., --corvu-disclosure-content-height)
  • Data Attributes: Corvu prefixes with data-corvu- (e.g., data-corvu-accordion-trigger)
  • Context Hooks: useContext() and useItemContext() for accessing component state

Documentation Resources

Kobalte Core Components

  • URL Pattern: https://kobalte.dev/docs/core/components/<component-name>
  • Content: Anatomy, Rendered elements, API Reference, Props, Data Attributes, CSS Variables
  • For detailed patterns, see docs/kobalte-patterns.md

Corvu Primitives

  • URL Pattern: https://corvu.dev/docs/primitives/<component-name>
  • Content: Anatomy, API Reference with rendered elements in Props table
  • For detailed patterns, see docs/corvu-patterns.md

Shadcn Registry

  • Components: https://raw.githubusercontent.com/shadcn-ui/ui/refs/heads/main/apps/v4/registry/bases/base/ui/<component-name>.tsx
  • Examples: https://raw.githubusercontent.com/shadcn-ui/ui/refs/heads/main/apps/v4/registry/bases/base/examples/<component-name>-example.tsx
  • Docs: https://raw.githubusercontent.com/shadcn-ui/ui/refs/heads/main/apps/v4/content/docs/components/<component-name>.mdx
  • Schema: https://ui.shadcn.com/schema/registry.json

Supporting Documentation

Related Skills

Looking for an alternative to react-to-solid or another community skill for your workflow? Explore these related open-source skills.

View All

openclaw-release-maintainer

Logo of openclaw
openclaw

Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞

333.8k
0
AI

widget-generator

Logo of f
f

Generate customizable widget plugins for the prompts.chat feed system

149.6k
0
AI

flags

Logo of vercel
vercel

The React Framework

138.4k
0
Browser

pr-review

Logo of pytorch
pytorch

Tensors and Dynamic neural networks in Python with strong GPU acceleration

98.6k
0
Developer