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.
Install
$ agentstack add skill-lvcoi-solidjskills-solid-start-server-runtime ✓ 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-start-server-runtime) 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-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-runtimenode 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 declarationssolid-start.solid-start.reference.server.create-middleware— middleware compositionsolid-start.solid-start.reference.server.create-handler— custom server handlerssolid-start.solid-start.advanced.request-events— request event lifecyclesolid-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
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.