How do I install the Solid Design Patterns skill?

Run npx skillmds@latest add tomevault-io/solid-design-patterns 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 Design Patterns 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 Design Patterns?

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 Design Patterns free to use?

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

Who published Solid Design Patterns?

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

Solid Design Patterns by tomevault-io

Name: Solid Design Patterns
Author: tomevault-io

Solid Design Patterns

Choose SolidJS architecture patterns with explicit tradeoffs, migration paths, and deterministic recommendation rules. Use when deciding state ownership, rendering/data flow, or boundary design. Use when this capability is needed.

tomevault-io 3a8762a 2 files · 2.8 KB Updated Sep 17, 2026

File contents

solid-design-patterns

Trigger

Use this skill for architecture decisions where multiple SolidJS patterns are viable and tradeoffs must be explicit.

Required Inputs

Problem statement and constraints.
Performance and SSR/hydration expectations.
Team maintainability constraints.
Migration constraints from current architecture.

Workflow

Frame decision boundaries and non-negotiable constraints.
Compare 2-3 options with explicit fit/cost profile.
Call out anti-patterns and regression risks for each option.
Recommend one option with phased adoption path.
Include validation commands and measurable acceptance criteria.

Failure Modes

Constraint ambiguity: do not recommend until constraints are explicit.
Single-option output: invalid unless alternatives are infeasible and reason is documented.
Recommendation without migration path: add phased plan before completion.
No verification criteria: output fails validation.

Output Contract

Return output matching DesignDecisionOutput schema at ../../skills/contracts/design-decision-output.schema.json with:

decision_statement, constraints, options, recommended_option.
tradeoffs, adoption_plan, validation_commands.
citations: each architectural claim must cite normalized doc_id and rationale.

Validation

node tools/scripts/validate-skills.mjs --skill solid-design-patterns
node tools/scripts/validate-output-contracts.mjs

References

../../references/solidjs-normalized/manifest.jsonl
../../references/solidjs-normalized/taxonomy.json
../../references/solidjs/stores-context.md
../../references/solidjs/async-data.md
../../references/solidjs/performance-ssr.md

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

---name: solid-design-patternsdescription: Choose SolidJS architecture patterns with explicit tradeoffs, migration paths, and deterministic recommendation rules. Use when deciding state ownership, rendering/data flow, or boundary design. Use when this capability is needed.---# solid-design-patterns## TriggerUse this skill for architecture decisions where multiple SolidJS patterns are viable and tradeoffs must be explicit.## Required Inputs- Problem statement and constraints.- Performance and SSR/hydration expectations.- Team maintainability constraints.- Migration constraints from current architecture.## Workflow1. Frame decision boundaries and non-negotiable constraints.2. Compare 2-3 options with explicit fit/cost profile.3. Call out anti-patterns and regression risks for each option.4. Recommend one option with phased adoption path.5. Include validation commands and measurable acceptance criteria.## Failure Modes- Constraint ambiguity: do not recommend until constraints are explicit.- Single-option output: invalid unless alternatives are infeasible and reason is documented.- Recommendation without migration path: add phased plan before completion.- No verification criteria: output fails validation.## Output ContractReturn output matching `DesignDecisionOutput` schema at `../../skills/contracts/design-decision-output.schema.json` with:- `decision_statement`, `constraints`, `options`, `recommended_option`.- `tradeoffs`, `adoption_plan`, `validation_commands`.- `citations`: each architectural claim must cite normalized `doc_id` and rationale.## Validation- `node tools/scripts/validate-skills.mjs --skill solid-design-patterns`- `node tools/scripts/validate-output-contracts.mjs`## References- `../../references/solidjs-normalized/manifest.jsonl`- `../../references/solidjs-normalized/taxonomy.json`- `../../references/solidjs/stores-context.md`- `../../references/solidjs/async-data.md`- `../../references/solidjs/performance-ssr.md`---> Converted and distributed by [TomeVault](https://tomevault.io/claim/lvcoi) — claim your Tome and manage your conversions.

Frequently asked questions