Solid State Architecture
Define SolidJS state ownership across signals, stores, and context with explicit coupling boundaries. Use for shared-state and context architecture decisions.
Install
$ agentstack add skill-lvcoi-solidjskills-solid-state-architecture ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-lvcoi-solidjskills-solid-state-architecture) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
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-architecturenode 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 statesolid-core.reference.store-utilities.produce— immer-style store mutationsolid-core.reference.store-utilities.reconcile— diffed store replacementsolid-core.reference.component-apis.create-context— context creationsolid-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
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: lvcoi
- Source: lvcoi/solidJSkills
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.