solid-state-architecture

solid-state-architecture is a skill for Claude Code, Codex from lvcoi/solidJSkills. It costs 31 tokens per session (502 once invoked), scanned A, original, MIT.

A guide for deciding where SolidJS application state should live: in local signals, shared stores, or context providers. It maps who owns each piece of state and how updates reach other components.

In plain words
What is it for?
Use it when designing state ownership, context boundaries, store shapes, and data flows across a SolidJS component tree.
Why use it?
It helps avoid unnecessary shared state, unclear update paths, and hidden dependencies between components. A component is a reusable part of a user interface.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/lvcoi/solidjskills/solid-state-architecture
Any agent
npx skills add lvcoi/solidJSkills --skill solid-state-architecture
Clone the repo
git clone --depth 1 https://github.com/lvcoi/solidJSkills

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for solid-state-architecture

README.md
[![agentmods](https://agentmods.dev/badge/skills/lvcoi/solidjskills/solid-state-architecture.svg)](https://agentmods.dev/skills/lvcoi/solidjskills/solid-state-architecture)
Your own site
<a href="https://agentmods.dev/skills/lvcoi/solidjskills/solid-state-architecture"><img src="https://agentmods.dev/badge/skills/lvcoi/solidjskills/solid-state-architecture.svg" alt="Measured on agentmods" height="20"></a>
Per session 31 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 502 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00031 $0.00502
Opus 5 $0.00015 $0.00251
Sonnet 5 $0.00006 $0.00100
Haiku 4.5 $0.00003 $0.00050

Measured 5d ago against content hash eb7b7554724f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

solid-state-architecture scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 5d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/solid-state-architecture/SKILL.md · 65 lines

What it actually says

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

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
Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 5d ago First seen · 65 lines · 31 tokens per session scan A eb7b7554724f

Subscribe to this mod's changes

solid-state-architecture is a skill published in the GitHub repository lvcoi/solidJSkills (10 stars, last pushed 6mo ago), licensed MIT. It adds 31 tokens to every session and 502 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens