Skip to content
cccskills
FreePublished on GitHubEnglish overview

solid-2.0

Use this primer when writing, reviewing, or migrating Solid 2.0 code. It explains core API patterns, highlights differences from Solid 1.x and React, and shows the appropriate primitives for reactive values, effects, stores, async work, and UI boundaries.

OriginalShow the original description

Solid 2.0 primer for coding agents. Use when writing, reviewing or migrating Solid 2.0 code (solid-js 2.x, @solidjs/web). The API differs from Solid 1.x and from React; read this before generating, then check unfamiliar names against node_modules/solid-js/CHEATSHEET.md.

solidjs/solid36,427 stars(GitHub 36,427 + cccskills 0)

Run score Not tested

See how to install

Good for

  • Writing a new Solid 2.0 component
  • Reviewing unfamiliar Solid 2.0 code
  • Migrating a Solid 1.x project
  • Checking the right API for async UI

Overview

What it does

This primer helps you check the core ideas and API differences when writing, reviewing, or migrating Solid 2.0 code. It covers common mistakes, such as destructuring props instead of reading them, passing accessors instead of values, mixing computation and side effects in createEffect, or updating stores outside their draft. It includes a mapping from APIs used in 1.x and guidance on when to use tools such as createSignal, createMemo, action, and <Loading>. It also covers async work, events, form input, and lists.

When it helps

Use it when learning Solid, or when generating or checking 2.0 code based on experience with React or Solid 1.x. It can help you find replacements for older APIs and choose how to display async data.

Example requests

  • “Rewrite this component using Solid 2.0 patterns.”
  • “Summarize what needs to change to migrate this Solid 1.x code to 2.0.”
  • “Choose an API for displaying async data, following this example.”

Notes

This guide covers Solid 2.0 (solid-js 2.x and @solidjs/web). It advises checking unfamiliar API names in node_modules/solid-js/CHEATSHEET.md.

This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.

Document check

AI checked the SKILL.md for operations that need care and for setup requirements. The score comes only from actually running the skill (hands-on test).

SafetyAre sending data, deleting files, and running commands disclosed?
AGoodIt guides code authoring and specifies no external sends or destructive operations.
Easy setupDoes it need few tools or API keys, and are they documented?
BPartly lackingIt assumes Solid 2.0 packages but gives no installation steps.

Not counted in the score. Rated by AI (OpenAI Codex) as of Nov 17, 2026. Treat it as a guide and read the original before installing.

Disagree? Request a re-evaluation

Tell us which point is wrong and why. No login needed. We will check it against the SKILL.md, redo the evaluation, and show the result here.

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

Files included (1)

  • SKILL.md9.4 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

agent-loops

FreeSummary

Use `@solidjs/diagnostics` to capture evidence from Solid 2.0 scenarios. Check diagnostic findings, rerun and waste budgets, the visible response to user interactions, and server-render waits and calls, then compare captures after repairs.

  • Checking generated or ported Solid code
  • Setting rerun and wasted-work limits
  • Finding why a scope reruns
solidjs/solid36.4KUpdated Nov 17, 2026

Use this guide to interpret Solid 2.0 diagnostic codes from warnings, test failures, or captured reports. It explains what each finding means and gives concrete repairs for tracking, writes, ownership, loading boundaries, and performance issues.

  • Fixing a Solid warning or test failure
  • Tracing a diagnostic code to its cause
  • Reducing unnecessary reactive work
solidjs/solid36.4KUpdated Nov 17, 2026

Use this guide to write or review Solid 2.0 server components that return templates. It explains where server markup belongs, how client components fill slots, and how to handle forms, event behavior, shared components, and compilation setup.

  • Writing a Solid server component
  • Deciding whether markup belongs on server or client
  • Passing client behavior through a slot
solidjs/solid36.4KUpdated Nov 17, 2026

See all skills by solidjs

Report a problem with this skill