Skip to content
cccskills
FreePublished on GitHubEnglish overview

server-components

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.

OriginalShow the original description

Rules for writing Solid 2.0 server components ("use server" functions that return a template) and their slots with @solidjs/web. Use when writing or reviewing a server component, deciding what lives on the server versus the client, or wiring a slot.

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

Run score Not tested

See how to install

Good for

  • Writing a Solid server component
  • Deciding whether markup belongs on server or client
  • Passing client behavior through a slot
  • Reviewing a server-rendered form or control

Overview

What it does

This guide covers implementation rules for Solid 2.0 server components: "use server" functions that return templates. It explains how to place data-driven elements in server markup and leave parts that need event handling or client state to client components supplied through slots. It describes slot types and placement, when $key helps preserve state, and how to pass async values. For server-rendered elements that need interaction, it covers using a form action or placing a client-owned element inside a slot.

When it helps

Use it when deciding which elements or behavior belong on the server and which belong on the client. It can also help when combining a server-rendered list with editing UI, or when placing interactive elements through slots.

Example requests

  • “Turn this list into a server component and pass the editing UI through a slot.”
  • “Should this button’s behavior live on the server or the client?”
  • “Check the props for this slot and how to use $key.”

Notes

The compilation example uses @solidjs/vite-plugin with ssr: true and serverFunctions: { components: true }.

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 describes server functions and forms, without directing unconfirmed external sends.
Easy setupDoes it need few tools or API keys, and are they documented?
BPartly lackingIt specifies `@solidjs/vite-plugin` and SSR options, with limited setup detail.

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.md4.7 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

solid-2.0

FreeSummary

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.

  • Writing a new Solid 2.0 component
  • Reviewing unfamiliar Solid 2.0 code
  • Migrating a Solid 1.x project
solidjs/solid36.4KUpdated Nov 17, 2026

See all skills by solidjs

Report a problem with this skill