solid
Skill395k starsChanged todayMITView on GitHub
Write, refactor, review, or test Solid 2 UI in OpenClaw (Control UI, plugin views, Canvas hosts), including state ownership, native custom elements, overlays, testing, performance, and lessons learned.
16 other projects use a version of this.
Trending
Quiet since March.about the whole repository
Most recently taken up by
- vladcheck/agentictheir own version, first seen Nov 8, 2026
- vladcheck/skillstheir own version, first seen Nov 1, 2026
- openclaw/openclawword for word, first seen Nov 1, 2026
- vercel-labs/json-rendertheir own version, first seen Oct 29, 2026
- bighamx/openclaw-android-node-apkword for word, first seen Oct 17, 2026
- steipete/warelayword for word, first seen Oct 17, 2026
Who's talking about molt-bot/clawdbot
- deepwiki.com“Bootstrap Files | molt-bot/clawdbot | DeepWiki”the web · Mar 7, 2026
- medium.com“My First Three Days with Clawdbot (now Moltbot)”the web · Feb 20, 2026
- linkedin.com“Clawdbot Review: Powerful but Security Concerns”the web · Feb 20, 2026
- sidsaladi.substack.com“OpenClaw/Moltbot/ClawdBot 101: The Complete Guide”the web · Feb 11, 2026
- resecurity.com“Clawdbot / Moltbot: The Autonomous AI Butler That Could ...”the web · Feb 6, 2026
The biggest 5 of 18 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 18
Talked about on the web (18 times).
On the web · 18
- Mar 7, 2026Bootstrap Files | molt-bot/clawdbot | DeepWiki — deepwiki.com
- Feb 20, 2026My First Three Days with Clawdbot (now Moltbot) — medium.com
- Feb 20, 2026Clawdbot Review: Powerful but Security Concerns — linkedin.com
- Feb 11, 2026OpenClaw/Moltbot/ClawdBot 101: The Complete Guide — sidsaladi.substack.com
- Feb 6, 2026Clawdbot / Moltbot: The Autonomous AI Butler That Could ... — resecurity.com
13 more on the web
- Feb 5, 2026Is OpenClaw Worth the Hype? I Spent 10 Days Finding Out — aimaker.substack.com
- Feb 4, 2026Can someone explain OpenClaw AI (formerly Clawdbot ... — beginrescueend.com
- Feb 2, 2026Full Setup Guide Clawdbot Moltbot OpenClaw — dev.to
- Feb 1, 2026Tales from the jar side: Clawdbot née Moltbot née OpenClaw, Moltbook and emergent behavior, The Boss still rules, and the usual Social Media silliness — kenkousen.substack.com
- Feb 1, 2026One Week Later with OpenClaw (prev. ClawdBot, prev. MoltBot): A Product Designer's Honest Take — nervegna.substack.com
- Jan 31, 2026In-Depth Moltbot Analysis for AI Developers — blog.promptlayer.com
- Jan 31, 2026I Used Clawdbot (OpenClaw) for 6 Hours so You Don't Have to Buy a Mac Mini - #108 — theagilevc.substack.com
- Jan 29, 2026Moltbot Hands-On Review: A Magical AI Assistant with Serious Red Flags | by Erik.C — medium.com
- Jan 29, 2026Moltbot (formerly Clawdbot): I Put an AI Agent on My Linux Server and Gave It My WhatsApp. Here's What Happened — mvidmar.substack.com
- Jan 29, 2026Falling in and out of love with Moltbot — platformer.news
- Jan 27, 2026Build Your Own AI Assistant with Molt Bot (Clawdbot) and ... — builder.aws.com
- Jan 27, 2026I Tried OpenClaw (Moltbot/ClawdBot) for Data Engineering and Here’s the Honest Truth | by Reliable Data Engineering — medium.com
- Jan 26, 2026MoltBot (ClawdBot) Review & Setup Guide — uxwritinghub.com
Other versions16 projects use a version of this.
Word for word · 7
- steipete/warelay★ 395k100% same
- moltbot/clawdbot★ 395k100% same
- openclaw/openclaw★ 395k100% same
- steipete/clawdis★ 394k100% same
- moltbot/moltbot★ 394k100% same
- clawdbot/clawdbot★ 394k100% same
- bighamx/openclaw-android-node-apk★ 57100% same
Edited · 0
None found.
Wrote their own version · 9
- vercel-labs/json-render★ 20ksame name
- ramziddin/solid-skills★ 591same name
- nank1ro/solid★ 165same name
- DGouron/review-flow★ 44same name
- JordanCoin/codingskills★ 10same name
- Gusen1453/creed★ 3same name
- vladcheck/agentic★ 1same name
- vladcheck/skills★ 1same name
- ramybarsoum/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository113 other files it gives its agents.
- AGENTS.mdAGENTS.md
- docs/AGENTS.mdAGENTS.md
- extensions/AGENTS.mdAGENTS.md
- scripts/AGENTS.mdAGENTS.md
- test/AGENTS.mdAGENTS.md
- ui/AGENTS.mdAGENTS.md
- agent-transcriptSkill
- auto-qaSkill
- autoreviewSkill
- channel-message-flowsSkill
- clawdtributorSkill
- claw-scoreSkill
- clawsweeperSkill
- control-ui-e2eSkill
- crabboxSkill
- discord-clawdSkill
- discord-e2eSkill
- discord-user-postSkill
- discrawlSkill
- gitcrawlSkill
- graincrawlSkill
- ios-e2eSkill
- labs-graduationSkill
- notcrawlSkill
- openclaw-changelog-updateSkill
- openclaw-ci-limitsSkill
- openclaw-debuggingSkill
- openclaw-docker-e2e-authoringSkill
- openclaw-ghsa-maintainerSkill
- openclaw-live-updaterSkill
- openclaw-parallels-smokeSkill
- openclaw-performanceSkill
- openclaw-pr-maintainerSkill
- openclaw-qa-testingSkill
- openclaw-refactor-docsSkill
- openclaw-release-validationSkill
- openclaw-repair-sweepSkill
- openclaw-secret-scanning-maintainerSkill
- openclaw-test-heap-leaksSkill
- openclaw-testingSkill
- openclaw-test-performanceSkill
- openclaw-updateSkill
- parallels-discord-roundtripSkill
- plugin-sdk-impactSkill
- proof-videoSkill
- prototype-openclaw-tuiSkill
- pr-simplifySkill
- release-openclaw-announcementSkill
- release-openclaw-ciSkill
- release-openclaw-macSkill
- release-openclaw-maintainerSkill
- release-openclaw-plugin-testingSkill
- security-triageSkill
- slack-e2eSkill
- slacrawlSkill
- tag-duplicate-prs-issuesSkill
- technical-documentationSkill
- telegram-e2e-userbotSkill
- test-auditSkill
- update-team-serverSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 53
Use jsxImportSource: "@solidjs/web" and its JSX types, not Solid 1's solid-js/web.
“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Solid 2 in OpenClaw
The Control UI and plugin views (extensions/x, extensions/workboard) render with Solid 2 (solid-js, @solidjs/web, @solidjs/signals, compiled by @solidjs/vite-plugin/@solidjs/compiler). Lit and Web Awesome are removed from these surfaces; new code is Solid only. The Canvas hosts also use Solid.
Read ui/AGENTS.md first; its state-ownership rules apply to Solid unchanged. Use the exact installed Solid pins from the owning package.json: the runtime and compiler are 2.0.0-rc.18, and @solidjs/vite-plugin is 3.0.0-next.51. @solidjs/testing-library remains 1.0.0-beta.3. solid-js and @solidjs/* are exempt from the repository's seven-day release-age gate (Peter, 2026-10-11). Peter also approved exact-version exceptions for seroval@1.7.0 and seroval-plugins@1.7.0 on 2026-10-24: rc.18 requires them for SSR/hydration serialization. Other third-party Solid ecosystem packages remain subject to the gate.
Rules that keep the UI correct
Before your first edit, read the installed ui/node_modules/solid-js/CHEATSHEET.md, especially its "What changed from 1.x" list. It is the rc.18 API contract, written as a guard against React and Solid 1 priors, the two dominant bug sources. For new code or a Solid audit, then read idioms and lessons; to refactor or review existing code, also use the refactor checklist. Check solid-js/types/client/flow.d.ts and the installed @solidjs/signals / @solidjs/web types when choosing an API. rc.18 has no createAsync: asynchronous values are ordinary computations returning promises or async iterables. createDeferred explicitly permits stale answers during refetch; use it only when that lag is the intended presentation contract.
For async reads, mutations, keyed projections, lazy components, or coordinated loading, read the async and action recipes. Cron is the worked reference: plain owners admit requests and writes; Solid presents their readiness and optimistic transitions.
For lists, derivations, copies, or anything on a hot path, read performance.
- Domain owners stay plain TypeScript. The Gateway store, capabilities,
lib/sessions/*, caches, persistence, and mutation authority keep synchronous mutate-then-read semantics. Solid 2 writes become visible only after a microtask flush, so authoritative state never lives in a signal. → state and ownership - Components consume projections from
ui/src/lib/reactive/(one per owner and scope, never a second store) anduseApplication()for the application context. Add a thin adapter only with its first production caller; subscribe to ordered events directly. - Host tags and classes survive. A component renders its existing
openclaw-*tag as a plain host element in light DOM; CSS and E2E select it. Never rename a tag or a class. → components - One implementation per registered tag. Solid-rendered native hosts share their renderer through
defineSolidBridgeinui/src/lib/solid-bridge.ts; use its returned component in JSX. Specialized native hosts such as Tooltip keep their existing wrapper and lifecycle owner. → components - One renderer per DOM region, and one lifecycle owner per overlay surface. → overlays
- Derive, don't synchronize.
createMemobeforecreateSignal; no copies of owner state; no defensive guards for states the owner already excludes. Prefer smaller code with fewer owners. - Keep rendering controller lifecycles out. Production Control UI rendering controllers and host-update contracts have been removed and are guarded. The controller-to-Solid recipe explains the boundary for new integrations: plain domain owners retain authority; Solid owns presentation and lifecycle.
Component skeleton
An illustrative component (the tag is an example): it renders its host tag, reads an owner through a projection, and derives instead of copying state.
import { createMemo, Show } from "solid-js";
import { useApplication } from "../lib/reactive/context.ts";
import { projectAgents } from "../lib/reactive/domain-capabilities.ts";
export function AgentCount(props: { compact?: boolean }) {
const app = useApplication();
// Reads through to the synchronous owner; disposed with this component's owner.
const agents = projectAgents(app.agents);
// Never destructure props: reads must stay reactive.
const count = createMemo(() => agents.read().agentsList?.agents.length ?? 0);
return (
<openclaw-agent-count class={["agent-count", { "agent-count--compact": props.compact }]}>
<Show when={count() > 0} fallback={<span class="muted">—</span>}>
<span>{count()}</span>
</Show>
</openclaw-agent-count>
);
}Use jsxImportSource: "@solidjs/web" and its JSX types, not Solid 1's solid-js/web.
Traps that compile but break
on:x,oncapture:,attr:x,bool:x,classList, anduse:are compile errors on native elements in rc.18. Spreads can still hide them from the compiler; keep the lint guard.prop:and XML namespaces remain supported.- Events are camelCase (
onClick). Dashed custom events need the exact dash, such asonSession-change, or alisten(...)ref factory. - Native event bindings bind once: dispatch through a stable callback that reads the current handler prop. Runtime spreads, including dynamic elements, can update handlers.
- A read right after a write sees the old value until
flush(). Don't write-then-read in handlers; derive. - Reactive reads after the first
awaitin an async memo are untracked, and async memos get noAbortSignal. - Ref callbacks run unowned:
onCleanupinside them does nothing. - ARIA enumerations are typed strings:
aria-pressed={pressed() ? "true" : "false"}, never a boolean. - Solid 1 APIs (
createResource,onMount,mergeProps,Context.Provider) don't carry over: use async computations,onSettled,merge, and the context component itself. - Writing a signal or store from a memo, an effect compute phase, or a component body throws in dev.
untrackdoesn't exempt it (the guard checks the owner); derive instead, or write from a handler,onSettled, or effect apply. - Class strings built with template literals or
.filter(Boolean).join(" ")lose composable reactivity: useclass={["base", { active: active() }]}. createRenderEffectis for render-phase runtime bindings, andflush()in production code usually hides a write-then-read: feature code usescreateEffectand derivations.
Enforced wave-zero guard
pnpm check:control-ui-controllers runs in lint and the changed-file checks.
For production ui/src and the bundled Workboard, Memory Core, Nostr, WhatsApp,
ClawRouter, and X view directories, it rejects createRenderEffect outside lib/reactive/,
all direct addEventListener calls in TSX, DOM queries outside the explicit
foreign-DOM owner list, and option-free memos whose callback only returns a
literal. Property/equality, async, and option-bearing memos retain their contracts.
Tests and test helpers are excluded. The native AST scan counts generic and
optional calls; flush, getOwner, and runWithOwner resolve actual Solid imports,
including aliases and namespaces, without counting owner methods or shadowed locals.
createEffect, untrack, addEventListener, querySelector(All), flush,
getOwner, and runWithOwner also have
per-file shrink-only baselines in config/control-ui-*-baseline.txt and
config/plugin-ui-*-baseline.txt. New calls cannot borrow another file's
allowance, including allowances in another plugin or the host. Deleting
calls requires pnpm check:control-ui-controllers --prune; moving an allowance
requires a verified Git rename. Never raise a baseline to admit new debt. See
the refactor checklist for replacements and
the permitted survivors.
The guard also bans JSX classList and hand-written createComponent outside
the explicit context-adapter allowlist. Component/view onCleanup and manual
stored/chained import loaders have shrink-only baselines; computation cleanup
and reactive primitives remain allowed. Saving flags require recipe review:
trace the co-written createOptimistic(false) rather than infer busy state
from isPending or a nearby optimistic declaration.
More, each with its root cause: lessons learned.
Testing
mountSolid, waitForSolid/flush, renderSolidRef, and the Solid application-context provider live in ui/src/test-helpers/. .test.tsx files are discovered. Keep assertions when you replace a harness. Visual changes need inspected, sanitized before/after screenshots. Follow the assigned campaign's compute budget. → testing
References
| Topic | Read when |
| idioms | choosing a primitive, derivations, props, lifecycle, stores, keys, async, context, diagnostics |
| async and actions | Gateway-owned reads, optimistic mutations, keyed projections, lazy code, sibling loading |
| refactor checklist | refactoring or reviewing existing Solid: measurable smells, replacements, before/after |
| components | writing components, native custom-element hosts, JSX bindings, events, refs, styles |
| state and ownership | touching owners, projections, async reads, lifetimes, parking, chat render lifecycle |
| overlays | menus, popovers, tooltips, dialogs, focus, positioning, the platform floor |
| testing | unit, browser, E2E, WebKit, parity, retention suites |
| performance | startup bundle, lazy loading, render budgets |
| plugins | building a plugin's Control UI view in Solid |
| lessons learned | before a new kind of change; most entries cost a failed CI run to learn |
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

