framework-solidjs_skill

Overview

This skill is a SolidJS and SolidStart specialist for projects using Solid 1.8+ and modern server/client patterns. It focuses on fine-grained reactivity, direct DOM rendering, and efficient data fetching with Solid Router, Actions, and Server Functions. It also prefers practical tooling like just and bun for running and building apps.

How this skill works

The skill inspects project layout, package scripts, and configuration to detect SolidStart or a router-based setup, then recommends commands and checks. It looks for a justfile first and falls back to bun-based scripts; it runs type checks and build/dev commands using bun when possible. It validates common Solid patterns—signals, memos, effects, stores, and resources—and flags anti-patterns that break reactivity.

When to use it

• Starting or migrating an app to Solid 1.8+ or SolidStart
• Optimizing reactivity, rendering, and update performance
• Setting up or troubleshooting server-side routes, server functions, or Actions
• Creating or auditing components for correct reactivity usage
• Configuring build and run scripts to use just and bun for consistency

Best practices

• Use createSignal, createStore, createEffect, createMemo, and createResource for reactive state and derived values
• Access props via props.name or splitProps/mergeProps to preserve reactivity
• Use <For> or <Index> for lists and <Show>/<Switch> for conditional rendering to keep updates fine-grained
• Prefer just recipes (e.g., just dev, just build) and bun run for script execution to match common Solid toolchains
• Run type checks with bun run tsc --noEmit or a justfile recipe and avoid any use of any or @ts-ignore

Example use cases

• Audit a SolidStart app to ensure server functions and actions use correct data-fetching patterns
• Refactor a component that loses reactivity by replacing prop destructuring with splitProps
• Recommend a run/build workflow: prefer justfile entries, otherwise use bun run dev / bun run build
• Convert array.map JSX to <For>/<Index> for reactive lists and better update locality
• Validate type safety and run bun-based typechecks before CI builds