菜单
Implements SolidJS reactive patterns using signals, effects, and memos. Use when writing or reviewing SolidJS components, state management, or reactive code. Covers the core mental model: components run once, signals track in reactive scopes, and props must not be destructured.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/IlyaGulya/claude-marketplace --skill solidjs-reactivity命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| name | solidjs-reactivity |
| description | Implements SolidJS reactive patterns using signals, effects, and memos. Use when writing or reviewing SolidJS components, state management, or reactive code. Covers the core mental model: components run once, signals track in reactive scopes, and props must not be destructured. |
SolidJS is NOT React. The fundamental differences:
// The component function runs ONCE. Only the {count()} expression re-evaluates.
function Counter() {
const [count, setCount] = createSignal(0);
console.log("This logs once, not on every update");
return <button onClick={() => setCount(c => c + 1)}>{count()}</button>;
}
Creates a reactive value with a getter (accessor) and setter.
{ createSignal } ;
[count, setCount] = ();
();
();
( prev + );
Options:
// Custom equality — skip update if values are "equal"
const [data, setData] = createSignal(initialData, {
equals: (prev, next) => prev.id === next.id,
});
// Always notify — useful for triggering effects on every set
const [trigger, setTrigger] = createSignal(undefined, { equals: false });
Key rule: Signal getters must be called (with ()) to read the value. count is a function, count() is the value.
Signals are only tracked when read inside a tracking scope. These are:
<div>{count()}</div>createEffect(() => console.log(count()))createMemo(() => count() * 2)Reading a signal outside these scopes does NOT create a subscription:
function MyComponent() {
const [count, setCount] = createSignal(0);
// NOT tracked — runs once during component setup
console.log(count());
// Tracked — re-runs when count changes
createEffect(() => {
console.log(count()); // tracked
});
// Tracked — JSX expressions are tracking scopes
return <div>{count()}</div>;
}
Runs side effects when dependencies change. Tracks signals automatically.
import { createSignal, createEffect, onCleanup } from "solid-js";
function Timer() {
const [count, setCount] = createSignal(0);
createEffect(() => {
const id = setInterval(() => setCount(c => c + 1), 1000);
onCleanup(() => clearInterval(id)); // cleanup on re-run or disposal
});
return <span>{count()}</span>;
}
Execution timing:
Cleanup: Use onCleanup inside an effect to clean up before re-execution or disposal.
Creates a cached derived value. Only recalculates when dependencies change.
import { createSignal, createMemo } from "solid-js";
function FilteredList() {
const [query, setQuery] = createSignal("");
const [items] = createSignal(["apple", "banana", "cherry"]);
// Recalculates only when query() or items() change
const filtered = createMemo(() =>
items().filter(item => item.includes(query()))
);
return <ul><For each={filtered()}>{item => <li>{item}</li>}</For></ul>;
}
Memo vs derived signal (plain function):
// Derived signal — recalculates every time it's read
const doubled = () => count() * 2;
// Memo — caches result, recalculates only when count changes
const doubled = createMemo(() => count() * 2);
Use createMemo when:
Use a plain derived signal when:
Groups multiple signal updates so downstream computations run once.
import { batch } from "solid-js";
batch(() => {
setFirstName("John");
setLastName("Doe");
setAge(30);
}); // Effects/memos that depend on these signals update once here
Automatic batching: Updates inside createEffect, onMount, and store setters are already batched. You rarely need explicit batch().
Important: If batch callback is async, only updates before the first await are batched.
Reads a signal without creating a tracking dependency.
import { untrack } from "solid-js";
createEffect(() => {
// count() is tracked, name() is NOT tracked
console.log(count(), untrack(() => name()));
});
Use untrack when you need a signal's current value without subscribing to changes.
The most common mistakes when writing SolidJS code are documented in detail in the PITFALLS.md companion file. The top issues:
() on signal gettersstopPropagation with delegated eventsBuild frontend interfaces with externally randomized style direction. Use when the user asks to build web components, pages, or applications with high design diversity. Produces distinctive, production-grade UI that avoids repetitive AI aesthetics.
Analyzes CLAUDE.md, AGENTS.md, and similar repository context files for effectiveness based on peer-reviewed research. Identifies instructions that hurt agent performance, redundant content, and unnecessary requirements. Use when reviewing a CLAUDE.md, auditing an AGENTS.md, optimizing context files, or when the user says "lint my CLAUDE.md", "review my AGENTS.md", "is my context file good", "optimize my context file", or "check my CLAUDE.md".
Complete reference for Claude Code skill YAML frontmatter fields, their values, and best practices. Use when writing frontmatter for SKILL.md, configuring skill invocation, setting allowed-tools, or deciding on skill metadata fields.