Install
$ agentstack add skill-lvcoi-solidjskills-solid-component-builder ✓ 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.
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-component-builder
Trigger
Use this skill for new or modified SolidJS components where component contract, reactivity, async behavior, accessibility, and SSR/hydration safety must be explicit.
Required Inputs
- Component goal and user-facing behavior.
- Prop interface and expected defaults.
- Data dependencies and async boundaries.
- Rendering context (client-only, SSR, or mixed).
- Acceptance constraints (performance, accessibility, test expectations).
Workflow
- Define component contract before implementation: props, emitted callbacks, ownership of state, and external dependencies.
- Choose primitives by rule: pure derivations use
createMemo; side effects usecreateEffect; async data usescreateResource; grouped updates usebatch. - Select control-flow primitives explicitly (`
,,/`) and document why each is used. - Declare loading, empty, error, and success rendering states when async data is present.
- Add SSR/hydration checks for browser-only behavior and deterministic initial render.
- Produce validation checklist and commands before returning final output.
Failure Modes
- Missing prop or data contracts: stop and request exact missing input keys.
- Ambiguous state ownership: default to local ownership and document escalation path.
- Missing async states: fail output and add explicit loading/error/empty branches.
- Hydration mismatch risk: require server/client render parity note before completion.
Output Contract
Return output matching ComponentBuildOutput schema at ../../skills/contracts/component-build-output.schema.json with:
summary,implementation_plan, andcomponent_contract.reactivity_decisions,acceptance_checklist, andvalidation_commands.citations: each item must includedoc_idandclaimsourced from normalized references.
Validation
node tools/scripts/validate-skills.mjs --skill solid-component-buildernode tools/scripts/validate-output-contracts.mjs
References
../../references/solidjs-normalized/manifest.jsonl../../references/solidjs-normalized/taxonomy.json../../references/solidjs/reactivity-core.md../../references/solidjs/component-patterns.md../../references/solidjs/performance-ssr.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.