docs: add skills - #3362
Conversation
Three skills under `.claude/skills/`, each a self-contained SKILL.md that an agent picks up on this checkout and that can be copied into another project. They cover usage patterns for people writing Solid apps, not workflows for working on this repository. - `solid-reactivity`: the primitive signatures that changed from Solid 1.x. `createEffect` takes a compute and an effect, a function argument to `createSignal` or `createStore` makes it derived, async is a computation that throws while pending, and the 1.x names that are gone map to their replacements. - `solid-control-flow`: Show, For, Repeat, Switch, Match, Loading, Errored, Dynamic, Portal, and Reveal, with the callback-child and keyed semantics that decide what remounts. - `solid-server-functions`: the closure rule the compiler enforces, why the boundary is not authentication, what declaring GET gives up, error sanitization, and the deployment secret the no-JS form path needs. Every claim is taken from the source in this repository rather than from Solid 1.x, including the removed-API map in `packages/solid/src/index.ts`. Co-Authored-By: Claude Opus 5 <[email protected]>
|
Merging this PR will degrade performance by 54.69%
|
| Benchmark | BASE |
HEAD |
Efficiency | |
|---|---|---|---|---|
| ❌ | projection derive: write one NESTED field (reference) |
262.3 µs | 579 µs | -54.69% |
Tip
Investigate this regression by commenting @codspeedbot fix this regression on this PR, or directly use the CodSpeed MCP with your agent.
Comparing lxsmnsyc:solid-usage-skills (4a24b42) with next (27aee36)
|
Coming from the PR discussion #3343 - I think this hits the same issue, just with higher stakes.
And it won't stop at one. Cursor has its own rules format, Copilot has If the underlying knowledge (signatures, control-flow semantics, server-function rules) is accurate, it belongs in the project's actual docs - vendor-neutral, human-readable, maintained by people who know the internals. Turning that into a |
|
Speaking of my understanding of the field - I use Claude Code, too. |
|
@nickshiro no worries, this is still a draft and isn't final yet. I'm still exploring the recipes before moving this to plugin form. Take note that the skills were meant to be plugins to be used by users, not a guide for the repo structure. |
Three skills under
.claude/skills/, each a self-contained SKILL.md that an agent picks up on this checkout and that can be copied into another project. They cover usage patterns for people writing Solid apps, not workflows for working on this repository.solid-reactivity: the primitive signatures that changed from Solid 1.x.createEffecttakes a compute and an effect, a function argument tocreateSignalorcreateStoremakes it derived, async is a computation that throws while pending, and the 1.x names that are gone map to their replacements.solid-control-flow: Show, For, Repeat, Switch, Match, Loading, Errored, Dynamic, Portal, and Reveal, with the callback-child and keyed semantics that decide what remounts.solid-server-functions: the closure rule the compiler enforces, why the boundary is not authentication, what declaring GET gives up, error sanitization, and the deployment secret the no-JS form path needs.Every claim is taken from the source in this repository rather than from Solid 1.x, including the removed-API map in
packages/solid/src/index.ts.