一键在 Manus 中运行任何 Skill

solid-state-architecture

星标6

分支4

更新时间2026年2月16日 17:49

Define SolidJS state ownership across signals, stores, and context with explicit coupling boundaries. Use for shared-state and context architecture decisions.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

lvcoi

lvcoi/solidJSkills

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

solid-state-architecture

Trigger

Use when deciding local vs shared state, context boundaries, store shape, and update pathways.

Required Inputs

Domain entities and update paths.
Component tree boundaries.
Cross-tree dependency requirements.

Workflow

Assign state scope: local signal, structured store, or context provider.
Document provider boundaries and mutation pathways.
Identify hidden coupling risks and propose boundary refactors.
Hand off explicit ownership map to macro skill.

Failure Modes

Context used as default for local state: mark anti-pattern and propose local alternative.
Store updates without explicit mutation path: fail until path is listed.
Shared state without consumer boundaries: require boundary map.

Output Contract

Return DomainGuidanceOutput with scope decisions, handoff actions, and citations with doc_id.

Validation

node tools/scripts/validate-skills.mjs --skill solid-state-architecture
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.store-utilities.create-store — nested reactive state
solid-core.reference.store-utilities.produce — immer-style store mutation
solid-core.reference.store-utilities.reconcile — diffed store replacement
solid-core.reference.component-apis.create-context — context creation
solid-core.concepts.stores — store concepts and patterns

References

../../references/solidjs/stores-context.md
../../references/solidjs-normalized/docs/concepts/stores.md
../../references/solidjs-normalized/docs/reference/store-utilities/create-store.md
../../references/solidjs-normalized/docs/reference/component-apis/create-context.md

同仓库更多 Skills

同仓库

solid-control-flow-rendering

lvcoi/solidJSkills

Select and enforce SolidJS control-flow and rendering primitives with explicit branch semantics. Use for conditional/list rendering, suspense boundaries, and dynamic rendering choices.

2026-02-166

solid-intent-router

lvcoi/solidJSkills

Route SolidJS user intent to the correct macro and domain subskill with deterministic keyword precedence and fallback rules. Use when selecting which Solid skill should execute first.

2026-02-166

solid-meta-head-management

lvcoi/solidJSkills

Apply solid-meta head and metadata primitives with deterministic SSR-safe behavior. Use for title/meta/link/style/base management across route and layout boundaries.

2026-02-166

solid-reactivity-core-expert

lvcoi/solidJSkills

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

2026-02-166

solid-router-data-navigation

lvcoi/solidJSkills

Apply Solid Router routing, navigation, and data APIs with deterministic loading/error and revalidation behavior. Use for route layout, params, query/action, and navigation flows.

2026-02-166

solid-ssr-hydration-debugger

lvcoi/solidJSkills

Diagnose and prevent SolidJS SSR/hydration mismatches with deterministic reproduction and remediation steps. Use for server-client render inconsistencies, hydration errors, and browser-only boundary issues.

2026-02-166

name	solid-state-architecture
description	Define SolidJS state ownership across signals, stores, and context with explicit coupling boundaries. Use for shared-state and context architecture decisions.
outputs	{"schema":"../../skills/contracts/domain-guidance-output.schema.json","format":"state-architecture-guidance"}
requires_references	["../../references/solidjs-normalized/manifest.jsonl","../../references/solidjs/stores-context.md"]
validation_commands	["node tools/scripts/validate-skills.mjs --skill solid-state-architecture","node tools/scripts/validate-solid-corpus.mjs"]

solid-state-architecture

Trigger

Use when deciding local vs shared state, context boundaries, store shape, and update pathways.

Required Inputs

Domain entities and update paths.
Component tree boundaries.
Cross-tree dependency requirements.

Workflow

Assign state scope: local signal, structured store, or context provider.
Document provider boundaries and mutation pathways.
Identify hidden coupling risks and propose boundary refactors.
Hand off explicit ownership map to macro skill.

Failure Modes

Context used as default for local state: mark anti-pattern and propose local alternative.
Store updates without explicit mutation path: fail until path is listed.
Shared state without consumer boundaries: require boundary map.

Output Contract

Return DomainGuidanceOutput with scope decisions, handoff actions, and citations with doc_id.

Validation

node tools/scripts/validate-skills.mjs --skill solid-state-architecture
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.store-utilities.create-store — nested reactive state
solid-core.reference.store-utilities.produce — immer-style store mutation
solid-core.reference.store-utilities.reconcile — diffed store replacement
solid-core.reference.component-apis.create-context — context creation
solid-core.concepts.stores — store concepts and patterns

References

../../references/solidjs/stores-context.md
../../references/solidjs-normalized/docs/concepts/stores.md
../../references/solidjs-normalized/docs/reference/store-utilities/create-store.md
../../references/solidjs-normalized/docs/reference/component-apis/create-context.md