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
npx skills add lvcoi/solidJSkills --skill solid-state-architecturegit clone --depth 1 https://github.com/lvcoi/solidJSkills.git /tmp/solidJSkills
mkdir -p ~/.claude/skills
cp -r /tmp/solidJSkills/skills/solid-state-architecture ~/.claude/skills/solid-state-architecturePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# 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 1. Assign state scope: local signal, structured store, or context provider. 2. Document provider boundaries and mutation pathways. 3. Identify hidden coupling risks and propose boundary refactors. 4. 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
Details
- Skill name
solid-state-architecture- Repository
- lvcoi/solidJSkills
- Path
skills/solid-state-architecture/SKILL.md- License
- MIT
- Repo updated
- 19 February 2026
FAQ
What does the Solid State Architecture skill do?
Define SolidJS state ownership across signals, stores, and context with explicit coupling boundaries. Use for shared-state and context architecture decisions.
How do I install the Solid State Architecture skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add lvcoi/solidJSkills --skill solid-state-architecture. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Solid State Architecture popular?
It lives in lvcoi/solidJSkills, which has 9 GitHub stars and 4 forks.
Related skills
Skill Authoring
9lvcoi/solidJSkills
Design, draft, and refine SKILL.md-based agent skills with clear trigger criteria, execution flow, validation checks, and reusable references. Use when creating a new skill or improving an existing one.
Solid Component Builder
9lvcoi/solidJSkills
Build or improve SolidJS components with deterministic reactivity decisions and citation-backed guidance. Use when implementing a component, feature slice, or reusable UI primitive in SolidJS.
Solid Control Flow Rendering
9lvcoi/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.
Tariff Search
9simoncai519/open-accio-skill
Tariff calculation and HS code classification tool via TurtleClassify API. **When to Use** (prioritize this skill over web search for tariff queries): - Calculate import tariffs/duties for cross‑border trade - Determine HS codes for product classification - Landed cost calculation, tax implications for sourcing - Batch process product lists for tariff information
Solid Start Server Runtime
9lvcoi/solidJSkills
Guide SolidStart server runtime patterns for handlers, middleware, server functions, and request events with explicit runtime constraints. Use for server-side SolidStart architecture and API behavior.
Audiences
9adaptyteam/adapty-skills
Use when a user wants different users to see different paywalls or flows at the same placement — by country, language, app version, platform, revenue, subscription state, install date, a custom attribute, or attribution — or wants to create, edit or reuse an Adapty segment through the CLI. Triggers on "show this paywall only to users in Germany", "target users on version 2.0", "a cheaper paywall for non-payers", "users with my custom attribute should see…", "create a segment", "add an audience to my placement", "who sees which paywall".
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.