Skip to content

ericrisco/rsc-harness / skills/solid-js

solid-js

Verified

Use when building, reviewing or debugging a SolidJS app — signals, stores, effects, memos and resources, and JSX that compiles to real DOM with no virtual DOM. Covers the classic traps: a signal that does not update the UI, For versus Index, effect loops, components that run once, and props losing reactivity when destructured. NOT React's re-render model (that is `react`).

FileKindSize
SKILL.mdskill md12.3 KB
evals/README.mdmarkdown77 B
evals/cases.yamlconfig1.9 KB
references/reactivity-deep-dive.mdmarkdown3.3 KB
references/router-and-start.mdmarkdown3.1 KB
scripts/verify.shexecutablescript4.7 KB

evals/cases.yaml

View on GitHub
skill: solid-js

should_trigger:
  - prompt: "My SolidJS signal is not updating the UI."
    why: "Signal reads/writes and UI tracking are core SolidJS."
  - prompt: "Should I use <For> or <Index> for this Solid list?"
    why: "Solid list control flow choice belongs here."
  - prompt: "createEffect is looping forever in my Solid component."
    why: "Solid effects and dependency tracking are specific to this skill."
  - prompt: "Why does my Solid component body only run once?"
    why: "Solid's run-once component model is the central mental model."
  - prompt: "Mi prop no se actualiza al desestructurar en Solid."
    why: "Spanish props destructuring/reactivity trap triggers SolidJS."

should_not_trigger:
  - prompt: "Fix this React hook dependency array."
    route_to: "react"
    why: "React hook/re-render model is not Solid."
  - prompt: "Implement a Next.js server action."
    route_to: "nextjs"
    why: "Next.js App Router/RSC belongs to nextjs."
  - prompt: "Migrate this Svelte 4 component to Svelte 5 runes."
    route_to: "svelte"
    why: "Svelte runes are a different compiler/reactivity model."
  - prompt: "Deploy this frontend to Vercel."
    route_to: "vercel"
    why: "Deployment target specifics belong to Vercel/deployment."

capability:
  - scenario: "A SolidJS component destructures props, uses count instead of count(), and has a createEffect that derives state."
    must_include:
      - "Explains that Solid component functions run once and tracked getter reads drive updates."
      - "Reads signals with count() and writes with the setter/updater form."
      - "Avoids destructuring reactive props in a way that freezes values."
      - "Uses plain derived functions or createMemo for derived values instead of effect-set-state."
      - "Chooses <For> vs <Index> based on item identity/stability."
      - "Keeps React mental-model advice out of Solid code."
      - "Flags Solid 2.0 beta vs stable 1.9 API differences when relevant."
brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).Stars: 322kUpdated Claude CodeCodexVerifiedInstall
brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.Stars: 197kUpdated Claude CodeCodexVerifiedInstall
frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.Stars: 197kUpdated Claude CodeCodexVerifiedInstall
mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).Stars: 197kUpdated Claude CodeCodexVerifiedInstall