How do I install the Solid Reactivity Core Expert skill?

Run npx skillmds@latest add tomevault-io/solid-reactivity-core-expert in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Solid Reactivity Core Expert safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Solid Reactivity Core Expert?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Solid Reactivity Core Expert free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Solid Reactivity Core Expert?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Solid Reactivity Core Expert by tomevault-io

Name: Solid Reactivity Core Expert
Author: tomevault-io

Solid Reactivity Core Expert

Apply SolidJS fine-grained reactivity primitives with strict derivation-vs-side-effect rules. Use for signal/memo/effect/resource decisions and dependency correctness. Use when this capability is needed.

tomevault-io d502c24 2 files · 3.1 KB Updated Sep 17, 2026

File contents

solid-reactivity-core-expert

Trigger

Use for reactivity correctness decisions involving createSignal, createMemo, createEffect, createResource, batch, untrack.

Required Inputs

State ownership and mutation boundaries.
Current or planned derivations.
Side effects and async behavior.

Workflow

Classify each reactive operation as state, derivation, side effect, or async boundary.
Replace effect-driven derivations with memo/signal derivations when possible.
Confirm dependency tracking is minimal and explicit.
Provide handoff notes to macro skill for implementation/refactor/review.

Failure Modes

Unknown state ownership: require explicit owner boundary.
Effect loops detected: mark as blocking issue and propose memo-driven rewrite.
Async without loading/error semantics: add resource state matrix.

Output Contract

Return DomainGuidanceOutput with decisions, handoff steps, validation commands, and citations containing doc_id.

Validation

node tools/scripts/validate-skills.mjs --skill solid-reactivity-core-expert
node tools/scripts/validate-solid-corpus.mjs

Key Corpus References

Use these doc_id values with the read_corpus_doc MCP tool:

solid-core.reference.basic-reactivity.create-signal — signal creation and update semantics
solid-core.reference.basic-reactivity.create-memo — derivation caching rules
solid-core.reference.basic-reactivity.create-effect — side-effect tracking and cleanup
solid-core.reference.basic-reactivity.create-resource — async reactive data loading
solid-core.reference.reactive-utilities.batch — grouped signal updates

References

../../references/solidjs/reactivity-core.md
../../references/solidjs-normalized/manifest.jsonl
../../references/solidjs-normalized/docs/reference/basic-reactivity/create-signal.md
../../references/solidjs-normalized/docs/reference/basic-reactivity/create-memo.md
../../references/solidjs-normalized/docs/reference/basic-reactivity/create-effect.md

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: solid-reactivity-core-expertdescription: Apply SolidJS fine-grained reactivity primitives with strict derivation-vs-side-effect rules. Use for signal/memo/effect/resource decisions and dependency correctness. Use when this capability is needed.---# solid-reactivity-core-expert## TriggerUse for reactivity correctness decisions involving `createSignal`, `createMemo`, `createEffect`, `createResource`, `batch`, `untrack`.## Required Inputs- State ownership and mutation boundaries.- Current or planned derivations.- Side effects and async behavior.## Workflow1. Classify each reactive operation as state, derivation, side effect, or async boundary.2. Replace effect-driven derivations with memo/signal derivations when possible.3. Confirm dependency tracking is minimal and explicit.4. Provide handoff notes to macro skill for implementation/refactor/review.## Failure Modes- Unknown state ownership: require explicit owner boundary.- Effect loops detected: mark as blocking issue and propose memo-driven rewrite.- Async without loading/error semantics: add resource state matrix.## Output ContractReturn `DomainGuidanceOutput` with decisions, handoff steps, validation commands, and citations containing `doc_id`.## Validation- `node tools/scripts/validate-skills.mjs --skill solid-reactivity-core-expert`- `node tools/scripts/validate-solid-corpus.mjs`## Key Corpus ReferencesUse these `doc_id` values with the `read_corpus_doc` MCP tool:- `solid-core.reference.basic-reactivity.create-signal` — signal creation and update semantics- `solid-core.reference.basic-reactivity.create-memo` — derivation caching rules- `solid-core.reference.basic-reactivity.create-effect` — side-effect tracking and cleanup- `solid-core.reference.basic-reactivity.create-resource` — async reactive data loading- `solid-core.reference.reactive-utilities.batch` — grouped signal updates## References- `../../references/solidjs/reactivity-core.md`- `../../references/solidjs-normalized/manifest.jsonl`- `../../references/solidjs-normalized/docs/reference/basic-reactivity/create-signal.md`- `../../references/solidjs-normalized/docs/reference/basic-reactivity/create-memo.md`- `../../references/solidjs-normalized/docs/reference/basic-reactivity/create-effect.md`---> Converted and distributed by [TomeVault](https://tomevault.io/claim/lvcoi) — claim your Tome and manage your conversions.

Frequently asked questions