solid-syntax-components

Define SolidJS components with safe prop access and child handling.

4|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/OpenAEC-Foundation/SolidJS-Claude-Skill-Package --skill solid-syntax-components
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: solid-syntax-components
Source: https://github.com/OpenAEC-Foundation/SolidJS-Claude-Skill-Package/tree/main/skills/source/solid-syntax/solid-syntax-components
Command: npx skills add https://github.com/OpenAEC-Foundation/SolidJS-Claude-Skill-Package --skill solid-syntax-components

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

SolidJS components can fall into React-inspired patterns like prop destructuring or repeated access to props, which can break reactivity. This Skill guides you to write components that preserve SolidJS reactivity by enforcing proper prop access, proper handling of children, and correct component typing patterns.

Core Features & Use Cases

  • Covers Component, ParentComponent, VoidComponent, and FlowComponent types and their recommended usage.
  • Demonstrates reactive props handling with splitProps and mergeProps, plus safe refs and event delegation.
  • Provides guidance on children resolution via the children() helper and iteration with For, plus use: directives.

Quick Start

Create a SolidJS component that reads props reactively and resolves children safely using the correct component type.

Frequently Asked Questions about solid-syntax-components

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

FAQPage Schema
Why does destructuring props break reactivity in SolidJS components?

Destructuring props breaks SolidJS reactivity by detaching property access from the reactive proxy. To preserve reactivity, access props directly or use splitProps and mergeProps to manage prop subsets safely without losing reactive tracking.

How do I properly handle children in SolidJS to maintain reactivity?

To maintain reactivity when handling children in SolidJS, use the children() helper to resolve child components safely. This ensures proper reactive tracking and avoids common pitfalls when passing nested content through ParentComponent types.

When should I use splitProps versus mergeProps in SolidJS?

Use splitProps in SolidJS to separate props into distinct reactive groups for targeted component access, and use mergeProps to combine multiple prop sources while preserving reactivity. Both prevent the reactivity loss caused by manual object spreading.

What is the difference between Component, ParentComponent, and FlowComponent types in SolidJS?

SolidJS Component types define standard components, ParentComponent types handle nested children safely, and FlowComponent types manage control flow structures like Show or Switch. Each enforces specific prop access and child handling patterns to preserve reactivity.

Do I need TypeScript to use SolidJS component patterns effectively?

TypeScript is required to effectively use these SolidJS component patterns, as the Skill relies on SolidJS 1.x/2.x with TypeScript to enforce proper typing for Component, ParentComponent, VoidComponent, and FlowComponent definitions.

How do I use directives and refs safely in SolidJS components?

To use directives and refs safely in SolidJS components, apply the use: directive syntax for DOM element behavior and ensure refs are accessed safely without breaking the reactive boundary. This Skill provides patterns for correct event delegation and ref handling.