How do I install the Solid Start Server Runtime skill?

Run npx skillmds@latest add tomevault-io/solid-start-server-runtime 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 Start Server Runtime 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 Start Server Runtime?

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 Start Server Runtime free to use?

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

Who published Solid Start Server Runtime?

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

Solid Start Server Runtime by tomevault-io

Name: Solid Start Server Runtime
Author: tomevault-io

Solid Start Server Runtime

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. Use when this capability is needed.

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

File contents

solid-start-server-runtime

Trigger

Use for SolidStart server runtime concerns: handlers, middleware, server functions, request event usage, and response behavior.

Required Inputs

Server runtime target and deployment constraints.
Route/API behavior and auth/session requirements.
Error/status/header handling expectations.

Workflow

Map endpoint responsibilities to SolidStart server primitives.
Select middleware boundaries and request event usage.
Define response/status/header semantics and failure handling.
Produce handoff notes for implementation and security checks.

Failure Modes

Runtime/deployment target unspecified: request target before decisions.
Mixed client/server concerns without boundaries: enforce boundary split.
Missing auth/session model for protected endpoints: block completion.

Output Contract

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

Validation

node tools/scripts/validate-skills.mjs --skill solid-start-server-runtime
node tools/scripts/validate-solid-corpus.mjs

Key Corpus References

Use these doc_id values with the read_corpus_doc MCP tool:

solid-start.solid-start.reference.server.use-server — server function declarations
solid-start.solid-start.reference.server.create-middleware — middleware composition
solid-start.solid-start.reference.server.create-handler — custom server handlers
solid-start.solid-start.advanced.request-events — request event lifecycle
solid-start.solid-start.advanced.middleware — middleware patterns and ordering

References

../../references/solidjs-normalized/docs/solid-start/reference/server/create-handler.md
../../references/solidjs-normalized/docs/solid-start/reference/server/create-middleware.md
../../references/solidjs-normalized/docs/solid-start/reference/server/use-server.md
../../references/solidjs-normalized/docs/solid-start/advanced/request-events.md
../../references/solidjs-normalized/manifest.jsonl

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

---name: solid-start-server-runtimedescription: 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. Use when this capability is needed.---# solid-start-server-runtime## TriggerUse for SolidStart server runtime concerns: handlers, middleware, server functions, request event usage, and response behavior.## Required Inputs- Server runtime target and deployment constraints.- Route/API behavior and auth/session requirements.- Error/status/header handling expectations.## Workflow1. Map endpoint responsibilities to SolidStart server primitives.2. Select middleware boundaries and request event usage.3. Define response/status/header semantics and failure handling.4. Produce handoff notes for implementation and security checks.## Failure Modes- Runtime/deployment target unspecified: request target before decisions.- Mixed client/server concerns without boundaries: enforce boundary split.- Missing auth/session model for protected endpoints: block completion.## Output ContractReturn `DomainGuidanceOutput` with runtime decisions, handoff steps, validation commands, and citations including `doc_id`.## Validation- `node tools/scripts/validate-skills.mjs --skill solid-start-server-runtime`- `node tools/scripts/validate-solid-corpus.mjs`## Key Corpus ReferencesUse these `doc_id` values with the `read_corpus_doc` MCP tool:- `solid-start.solid-start.reference.server.use-server` — server function declarations- `solid-start.solid-start.reference.server.create-middleware` — middleware composition- `solid-start.solid-start.reference.server.create-handler` — custom server handlers- `solid-start.solid-start.advanced.request-events` — request event lifecycle- `solid-start.solid-start.advanced.middleware` — middleware patterns and ordering## References- `../../references/solidjs-normalized/docs/solid-start/reference/server/create-handler.md`- `../../references/solidjs-normalized/docs/solid-start/reference/server/create-middleware.md`- `../../references/solidjs-normalized/docs/solid-start/reference/server/use-server.md`- `../../references/solidjs-normalized/docs/solid-start/advanced/request-events.md`- `../../references/solidjs-normalized/manifest.jsonl`---> Converted and distributed by [TomeVault](https://tomevault.io/claim/lvcoi) — claim your Tome and manage your conversions.

Frequently asked questions