[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78FK4HE2AMVRRM55W2YN66C":3,"skill-same:01M78FK4HE2AMVRRM55W2YN66C":57},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M78FK4HE2AMVRRM55W2YN66C","solid-app-shell",null,"Use when making Solid app mutations optimistic, fixing stale rollbacks or lost debounced edits, integrating shared app chrome, or diagnosing theme flashes, host CSS conflicts, and cross-app Type Index categories. For the @jeswr\u002Fapp-shell component API, use the package skill.","jeswr\u002Fsolid-sdk","jeswr","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F63333554?v=4","01M78F8AE112CQ0KHFC3R0Z8SJ","Jesse Wright","01M78F8AERJX4YWDA1S4BMF74V",2,"MIT","https:\u002F\u002Fgithub.com\u002Fjeswr\u002Fsolid-sdk\u002Fblob\u002Fmain\u002Fskills\u002Fsolid-app-shell\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: solid-app-shell\ndescription: Use when making Solid app mutations optimistic, fixing stale rollbacks or lost debounced edits, integrating shared app chrome, or diagnosing theme flashes, host CSS conflicts, and cross-app Type Index categories. For the @jeswr\u002Fapp-shell component API, use the package skill.\n---\n\n## Quick reference\n\nUpdate local UI state immediately, persist asynchronously, and reconcile in the background.\nKeep a confirmed baseline and an ordered queue of field-scoped mutations; after failure, recompute the visible value from the baseline plus the remaining queue.\nFlush pending debounced writes on page teardown, respecting the keepalive body cap and retaining failed writes for retry.\nFor shared React chrome APIs, read [the package skill](..\u002F..\u002Fpackages\u002Fapp-shell\u002FSKILL.md); this skill keeps application patterns.\n\n\u003C!-- AUTHORED-BY Codex GPT-6 -->\n\n\u003C!-- AUTHORED-BY Codex GPT-6.1-Sol -->\n\n\u003C!-- AUTHORED-BY Claude Opus 4.8 -->\n\nFor the component API, [packages\u002Fapp-shell\u002FSKILL.md](..\u002F..\u002Fpackages\u002Fapp-shell\u002FSKILL.md) is authoritative.\n\n# App shell — optimistic, non-blocking pod mutations\n\nRead the companion [`AGENTS.md`](..\u002F..\u002FAGENTS.md)\nfirst; pairs with the [`solid-offline-patterns`](..\u002Fsolid-offline-patterns\u002FSKILL.md)\nskill (instant-load reads) — this one is the **write** side of the same \"the app feels instant\" goal.\n\nA pod write is a network round-trip (often a conditional PUT\u002FPATCH plus a refresh). Blocking the\ninteraction on it makes the UI feel sluggish — a dragged card hangs in mid-air until the server\nanswers. Instead, make mutations **optimistic**:\n\n1. **Update the UI immediately.** Apply the change to local state the instant the user acts — the\n   kanban card slides to its new column, the toggle flips, the title updates — before any network\n   call.\n2. **Persist asynchronously.** Fire the pod write **without blocking** the interaction, and crucially\n   **without the blocking full-refresh** that a normal mutation does (the local state is already\n   correct). Reconcile in the background on success (a live-sync\u002Frefresh will also catch any coupled\n   change the server made).\n3. **Show a small, non-intrusive save indicator** for in-flight writes: \"Saving…\" while pending, a\n   brief \"Saved\" on success that auto-clears to idle, \"Save failed\" on error. A fixed-corner pill\n   (`role=\"status\"`, `aria-live=\"polite\"`, hidden when idle) — never a modal or a blocking spinner.\n4. **On failure: show an error AND revert** the optimistic change. The revert is where the\n   correctness lives — see below.\n\n```ts\n\u002F\u002F Keep nextGeneration and this record's edit state in the store across renders.\nconst patch = moveToPatch(move); \u002F\u002F only the fields changed by this move\nif (isNoOp(visibleValue(edits), patch)) return;\nconst generation = ++nextGeneration;\nsetEdits((cur) => enqueueMutation(cur, generation, patch)); \u002F\u002F UI updates instantly\npersist((repo) => repo.applyWrite(id, move)).then(\n  () => setEdits((cur) => settleMutation(cur, generation, true)),\n  () => {\n    showSaveError();\n    setEdits((cur) => settleMutation(cur, generation, false));\n  },\n);\n```\n\n## Revert correctly — the two traps (both real review findings)\n\n### Trap 1 — reverting the WHOLE record clobbers concurrent edits to other fields\n\nWhile a failed write was in flight, the user may have edited a **different** field of the same\nitem. Keep each mutation as a field-scoped patch: a status move changes `status`\u002F`state`, a\npriority move changes `priority`. Recompute from the confirmed baseline and the remaining\npatches so unrelated edits survive.\n\n### Trap 2 — a stale failed write clobbers a NEWER mutation of the same item\n\nValue equality cannot establish ownership: with priority `0 → 1 → 2 → 1`, a late failure\nof the first write must not undo the newer successful edits. Generations identify mutations,\nbut a generation fence alone is insufficient: with `0 → 1 → 2` and **both writes failing**,\nthe second write's captured original is the unconfirmed `1`. Restoring it resurrects a failed\nedit, regardless of which failure arrives first.\n\n**Keep a confirmed baseline plus an ordered queue of mutations.** The visible record is the\nbaseline with the queue's patches applied in local intent order. On failure, remove that\nmutation and recompute; never restore its captured original. On success, mark it confirmed\nand fold only the confirmed prefix into the baseline. A successful newer mutation stays in\nthe queue while an older one is unresolved, so it remains visible without letting a late older\nsuccess overwrite it.\n\n```ts\ntype Fields = { priority: number; status: string; state: string; title: string };\ntype Item = Fields & { id: string };\ntype Mutation = { generation: number; patch: Partial\u003CFields>; confirmed: boolean };\ntype EditState = { baseline: Item; pending: Mutation[] };\n\n\u002F\u002F Store lifetime counter; never reuse a generation after deletion\u002Freplacement\u002Faccount switch.\nlet nextGeneration = 0;\n\nfunction visibleValue(state: EditState): Item {\n  return state.pending.reduce((item, mutation) => ({ ...item, ...mutation.patch }), state.baseline);\n}\n\nfunction enqueueMutation(state: EditState, generation: number, patch: Partial\u003CFields>): EditState {\n  return {\n    ...state,\n    pending: [...state.pending, { generation, patch: { ...patch }, confirmed: false }],\n  };\n}\n\nfunction settleMutation(state: EditState, generation: number, success: boolean): EditState {\n  if (!state.pending.some((mutation) => mutation.generation === generation)) return state;\n  let pending = success\n    ? state.pending.map((mutation) =>\n        mutation.generation === generation ? { ...mutation, confirmed: true } : mutation,\n      )\n    : state.pending.filter((mutation) => mutation.generation !== generation);\n  let baseline = state.baseline;\n  while (pending[0]?.confirmed) {\n    const [first, ...rest] = pending;\n    baseline = { ...baseline, ...first.patch };\n    pending = rest;\n  }\n  return { baseline, pending };\n}\n```\n\nInitialize one `EditState` per record from its confirmed server value with `pending: []`.\nAll local writers enqueue field-scoped patches. A confirmed entry waiting behind an unresolved\none remains in `pending` until it can join the baseline. These reducers are pure: React may\nreplay an updater without consuming a mutation. Drop the queue on deletion, record replacement,\nor account switch; callbacks for generations absent from the new state do nothing.\nSerialize pod writes per record or use conditional writes with conflict reconciliation to\npreserve server ordering; this queue governs local visibility. Generation-fence background\nrefreshes, and do not replace the baseline with a stale refresh while mutations remain.\n\n## Flush a debounced write on tab teardown — don't lose the last edit\n\nAn optimistic mutation that **debounces** the pod write (coalescing rapid edits into one PUT) has a\ngap the optimistic path itself doesn't cover: if the user **closes the tab, navigates away, or\nbackgrounds it** while a debounced write is still pending, the timer never fires and the **last edit\nis lost** — the UI showed \"Saving…\" (or even \"Saved\" optimistically) but nothing reached the pod. The\ndurable cache (`solid-offline`) preserves it for *that* browser, but a different device never sees it.\n\nFlush pending writes on the teardown signals — and mind the `keepalive` body cap:\n\n- **Flush on `pagehide` AND `visibilitychange` → `hidden` (and `beforeunload` as a belt-and-braces).**\n  `visibilitychange(hidden)` is the most reliable on mobile (a backgrounded tab the OS may kill never\n  fires `pagehide`\u002F`unload`); `pagehide` covers tab-close\u002Fnavigation. Treat them as the same \"the page\n  may be going away now — persist now\" trigger and de-dupe (below).\n- **Use `fetch(url, { keepalive: true })` so the request OUTLIVES the page** — a normal `fetch` is\n  cancelled when the document tears down, so the write never completes. `keepalive` lets the browser\n  finish it after the page is gone. **But `keepalive` has a hard ~64 KB cap on the encoded request\n  body** (the Fetch spec's `keepalive` inflight-body limit) — over it the `fetch` **rejects**. So:\n  encode the body first, and use `keepalive` **only when it fits**; an oversized snapshot falls back\n  to a **normal** `fetch` (best-effort — it may not finish, but it can't silently swallow the write).\n  (`navigator.sendBeacon` is the same cap and can't send the conditional `If-Match`\u002F`Content-Type`\n  headers a pod PUT needs, so prefer `keepalive` `fetch`.)\n- **Clear the pending marker only AFTER the write resolves — keep it for retry on failure.** A teardown\n  flush that optimistically marks the snapshot \"saved\" before the keepalive request resolves loses the\n  edit if that request fails; leave the durable-cache pending flag set until success so the next open\n  retries.\n- **Coalesce concurrent unload flushes of the SAME snapshot.** `pagehide` and `visibilitychange` can\n  both fire for one teardown; firing two keepalive PUTs of the same body **doubles** the bytes counted\n  against the per-page keepalive cap (and can race the conditional `If-Match`). Single-flight the flush\n  on the snapshot's identity\u002Fversion so one teardown sends **one** request. **But never coalesce a\n  keepalive flush onto a non-keepalive in-flight save** — a normal debounced save already in flight is\n  cancelled by the teardown, so the keepalive flush must still run; only coalesce keepalive-with-keepalive.\n\nThis is the teardown corner of the optimistic-mutation \u002F `solid-offline` invariant: optimistic +\ndurable-cache makes the edit *survive locally*; the keepalive flush is what makes it *reach the pod*\nwhen the tab dies mid-debounce. (Cited: the five jeswr OSS Solid forks — Linkding, Elk, Excalidraw,\nMiniflux, Actual — 2026-06; Excalidraw's debounced scene-persist needed the `pagehide` keepalive\nflush + the 64 KB cap fallback, hardened over roborev's fetch\u002Funload rounds.)\n\n## Indicator, no-ops, and reconciliation\n\n- **A move that doesn't change anything is a no-op** — a drop onto the card's *current* column must\n  not fire a write or show \"Saving…\". Compare the patch with `visibleValue(edits)` and bail.\n- **Keep the optimistic state in the durable cache too** (see `solid-offline`), so a reopen\n  mid-write paints the optimistic state rather than the pre-write one.\n- **Reconcile in the background after a successful persist** (a non-blocking refresh), so a change\n  the server coupled to your write — e.g. a workflow status that also flips an open\u002Fclosed flag —\n  lands without the user waiting on it.\n\n## Reading a pod container into a view (the read side)\n\nBuilding a list\u002Fbrowser view over a pod container surfaced three patterns worth applying every time (each a roborev finding while building 8 sibling Solid apps):\n\n- **Inject the authenticated `fetch` as a seam, don't hard-wire login.** The view\u002Fhook\u002Fdata-layer take an injectable `fetch` (fall back to the ambient global a reactive-auth shell patches). This builds + unit-tests *now* (stub the fetch) while the real login wires in later — the view is never coupled to the auth flow.\n- **Validate `ldp:contains` child IRIs before you fetch them.** A view that reads each child of a listed container must NOT blindly fetch every IRI the container advertises — a malicious\u002Fmalformed container can list arbitrary URLs\u002Fschemes (an SSRF vector, and it runs before any href-display gate). Require each child to be: an `http(s):` IRI, **same-origin** with the container (compare parsed `URL.origin`, not a raw string prefix — defeats `https:\u002F\u002Fyou@evil\u002F…` userinfo + look-alike-prefix tricks), and a **real descendant path** (compare `URL.pathname` under the container's slash-terminated path with a non-empty remainder — so the container itself, even with `?query`\u002F`#fragment`, is rejected). Drop anything else (don't fetch, don't fail the listing).\n- **A data-layer `list()` that swallows 401\u002F403 → `[]` is right for the store but WRONG for a screen.** It makes \"you don't have permission\" indistinguishable from \"empty\", so a forbidden container renders \"Nothing here\" instead of an access-denied state. Wrap it in a thin **UI read facade** that surfaces a typed `AccessDeniedError` (401\u002F403), maps **404 → empty**, **2xx-empty → empty**, else re-throws — without changing the shared store contract other callers depend on. And on an access error during a *reload*, **clear the previously-loaded list + selection** so stale data doesn't linger under the access-denied state.\n\n\n\n\u003C!-- AUTHORED-BY Claude Opus 5.5 -->\n\n## Offline conventions in the Solid Suite shell (`apps\u002Fsuite`)\n\n- **`requiresOnline`.** Writes work offline everywhere (they queue in the outbox) except controls\n  that need a connection: share changes, registration, connector sign-in, purging the trash.\n  Wrap each in `\u003CRequiresOnline>` (`src\u002Fshell\u002Fsync\u002Frequires-online.tsx`); it renders suite-ui's\n  `OnlineGate`, which disables the control while the shell is offline or reconnecting and\n  explains \"You're offline. This needs a connection.\" in a keyboard- and pointer-reachable\n  tooltip. Use `useNeedsConnection()` when only the flag is needed (a whole fieldset). The\n  control must forward `disabled`\u002F`aria-disabled`. First use: the share dialog's Add button.\n- **Connection state** comes from `useConnectionState()` (\"online\" | \"offline\" |\n  \"reconnecting\"): `navigator.onLine` plus, while offline, an unauthenticated opaque HEAD to the\n  active storage root every 30 s; \"Reconnecting…\" shows for at least 1.5 s. Outside the shell it\n  falls back to `navigator.onLine`. Never switch on `navigator.onLine` directly in a shell control.\n- **Outbox.** `useOutbox()` (`src\u002Fshell\u002Fsync\u002Foffline-provider.tsx`) is the seam the SyncSheet\n  reads until the SDK outbox lands: `enqueue({ label, where })` records a change *description*\n  (never contents); a reconnect sends pending items; failed items wait for Retry.\n- **Recent items** (behind `\u002Foffline`) record the shell's `pageTitle` and pathname only, per\n  account; no queries, fragments or document contents.\n- **Service worker** (`\u002Fservice-worker`, production only): precaches shell routes and `\u002F_next\u002Fstatic`\n  assets and answers offline navigations, falling back to `\u002Foffline`. It never caches storage\n  responses, requests with `Authorization`\u002F`DPoP`, or cross-origin responses.\n\n## Detailed integration patterns\n\n- Read for cross-app class mapping, prebuild environment precedence, and controlled forms. [references\u002Finterop-and-forms.md](references\u002Finterop-and-forms.md).\n- Read when integrating shared chrome, Tailwind tokens, theming, or Lit\u002FReact controls. [references\u002Fchrome-integration.md](references\u002Fchrome-integration.md).\n\n## Pitfalls\n\n### Paginated sources and snapshot overwrites\n\nWhen syncing a local API into a pod by replacing a whole RDF document, a fresh dataset plus\nconditional PUT overwrites everything, even if the source API silently capped the first page.\nAn oversized `limit` is not proof of completeness. Follow every page\u002Fcursor until the API's\ncompletion condition (for example, `offset >= total`), assemble the complete snapshot, then\nserialize through the suite RDF writer and perform the conditional write. If a page fails or\npagination stops making progress, fail the sync without writing a partial replacement.\nAn ETag prevents conflicting writes; it cannot detect a truncated source snapshot.\n\n## Gotchas\n\n| Gotcha | Detail |\n|---|---|\n| Interaction hangs until the pod answers | The write is blocking — update local state first, persist async, never `await` before the UI updates |\n| Editor breaks on the empty string mid-edit | A controlled input wired straight to a throwing typed setter (`@solid\u002Fobject` `…As`) throws on every transiently-invalid keystroke — store the **raw** string in local state, never throw in `onChange`, validate the assembled draft separately, call the setter only at save with a valid value |\n| Host app's `button {}` repaints your shell's controls | Tailwind v4: an **unlayered** author rule beats EVERY `@layer`'d utility — `@layer`\u002Fspecificity bumps don't fix it. Ship an unlayered attribute-scoped reset (`[data-app-shell-control]{…}`, 0,1,0 > a bare element's 0,0,1 when both unlayered) + a **private literal** token mirror (`--as-accent`, not `var(--accent)` indirection) declared on a `:root`\u002Fshared ancestor so portaled menus\u002Fdialogs inherit it |\n| Dark-OS user sees a one-frame light flash | A `ThemeProvider` resolving\u002Fapplying the theme in a passive `useEffect` runs after paint, so `resolvedTheme` starts `light`. Apply in an **isomorphic layout effect** (`useLayoutEffect` in-browser, `useEffect` off-browser via a `typeof window` guard) — correct on the first painted frame, SSR-safe; a pre-hydration class-toggling `\u003Cscript>` doesn't fix React state |\n| Web-Component prop dropped via the React wrapper | `@lit\u002Freact` `createComponent` classifies props before the Lit class finalizes, so a non-reflected reactive **property** is silently dropped under React 19 — the element renders its fallback (e.g. `Loading` shows generic \"Loading\"). Make the prop `reflect: true`, or consume the raw element with a DOM **attribute** (`\u003Cjeswr-loading label=\"…\">`) |\n| `@lit\u002Freact` prop won't render in a vitest test | `@lit\u002Freact` resolves its **`node`** export condition under vitest\u002Fjsdom, whose build SKIPS the `useLayoutEffect` that forwards props — so a React-wrapper assertion (`render(\u003CLoading label\u002F>)` then check the label) **can't pass even with `reflect: true`**; it's an env artifact, not a bug. Test the **raw element**: set the property directly, then assert the reflected attribute + the rendered `::part`, not the wrapper |\n| Host `button {}` distorts the shared controls' SIZE | A chrome library's reset isolates **color\u002Fborder\u002Ffill** but leaves the **box model** to its own layered classes — so a consumer's bare unlayered global `button {}` still out-ranks that layered sizing and squashes the shared controls. Scope host element rules (`.login-form button`), or exclude the controls with `button:where(:not([data-app-shell-control]))`; only globally relax what the reset covers, never the box model |\n| Bare `:not([attr])` exclusion repaints your OWN buttons | The exclusion-selector trap: `button:not([data-app-shell-control])` **leaks the attribute's specificity through `:not()`** → `(0,1,1)`, out-ranking your class-only host overrides (`.foo-link`\u002F`.foo-cancel` at `(0,1,0)`) and repainting them with the base look. Wrap it: `button:where(:not([…]))` carries **zero** specificity → stays `(0,0,1)`. Guard with a test rejecting BOTH the unscoped and the bare-`:not()` form |\n| App shows the SUITE palette instead of its own | To consume `@jeswr\u002Fapp-shell` on a Tailwind-v4 app while keeping your own colours: **alias** the shell-private `--as-*` tokens onto your palette on **both `:root` and `.dark`**, register the `as-*` keys in `@theme` + set `darkMode: 'class'`, and import **only the shell's reset** — NOT its suite theme-token sheet (which re-declares `--as-*` with the suite colours and overrides your aliases). Re-point the token seam; don't fork the shell |\n| `npm run build` bakes a localhost client-id | A prebuild config script doesn't get the bundler's `.env` loading — load `.env`\u002F`.env.local` yourself via `node:util` `parseEnv`; a wrong client-id origin = broken login at the deployed subdomain |\n| `.env.local` fails to fully override `.env` | Resolve the origin **per-layer** (`shell → .env.local → .env → default`, first layer that yields one wins), never merge into one dict + pick per-variable — that lets `.env` beat `.env.local` cross-variable |\n| Forbidden container shows \"empty\" | A store `list()` swallowing 401\u002F403→`[]` hides access-denied — wrap in a UI facade that surfaces a typed AccessDenied; clear stale list on a reload that 403s |\n| View fetches an attacker's URL | Don't fetch every `ldp:contains` IRI — require http(s) + same-origin (parsed `origin`) + a real descendant `pathname` before fetching a child |\n| A producer app's data shows under \"Other\" | A consumer must map EVERY producer's Type-Index `solid:forClass` IRI into its own category\u002Fview map (both `https`\u002F`http` schema.org forms) — an unmapped class is still discovered but mis-bucketed into the fallback (cited: pod-docs' `pd:Document`); add the mapping + a regression test when you add a producer app |\n| Concurrent edits lost on revert | Trap 1 — enqueue field-scoped patches and recompute from the confirmed baseline plus remaining mutations |\n| Newer move undone by an older failure | Trap 2 — remove only the failed generation from the queue; retain newer edits and never restore an unconfirmed original |\n| Spurious \"Saving…\" on a no-op drop | Compare the patch with the visible value and skip the write when nothing changes |\n| Indicator clutters the UI | Hide when idle; auto-clear \"Saved\" back to idle after ~1.5 s; fixed-corner pill, `aria-live=\"polite\"`, not a modal |\n| Coupled server change missing after persist | Background-reconcile on success — the server may have changed a field your write didn't set |\n| Last edit lost when the tab is closed mid-debounce | A debounced pod write whose timer hasn't fired is lost on tab-close\u002Fnavigate\u002Fbackground. Flush on `pagehide` **and** `visibilitychange→hidden` (mobile-reliable) with `fetch(url,{keepalive:true})` so the request outlives the page; clear the pending marker only AFTER it resolves (keep it for retry) |\n| `keepalive` flush rejects on a big body | `keepalive` has a hard ~64 KB encoded-body cap — over it the `fetch` rejects and the write silently never sends. Encode first, use `keepalive` only when it fits; an oversized snapshot falls back to a **normal** `fetch` (best-effort). `sendBeacon` has the same cap and can't carry the `If-Match`\u002F`Content-Type` a pod PUT needs |\n| Two keepalive PUTs of one snapshot blow the cap | `pagehide` + `visibilitychange` both fire for one teardown — single-flight the flush on the snapshot's version so one teardown = one request. But never coalesce a keepalive flush onto a non-keepalive in-flight save (the normal save is cancelled by the teardown; the keepalive flush must still run) |\n\n---\n\n*Learned building [`jeswr\u002Fsolid-issues`](..\u002F..\u002Fapps\u002Fissues\u002FREADME.md): the optimistic\nboard logic in [`src\u002Flib\u002Fboard.ts`](..\u002F..\u002Fapps\u002Fissues\u002Fsrc\u002Flib\u002Fboard.ts)\n(`optimisticMove`, `revertMoveIfCurrent` — both revert traps), the non-blocking `persist` in\n[`src\u002Flib\u002Fuse-issues.ts`](..\u002F..\u002Fapps\u002Fissues\u002Fsrc\u002Flib\u002Fuse-issues.ts),\nand the [`src\u002Fcomponents\u002Fsave-indicator.tsx`](..\u002F..\u002Fapps\u002Fissues\u002Fsrc\u002Fcomponents\u002Fsave-indicator.tsx)\npill, commit `ca0c687`. Both revert traps were roborev findings fixed in that change.*\n","## Quick reference\n\nUpdate local UI state immediately, persist asynchronously, and reconcile in the background.\nKeep a confirmed baseline and an ordered queue of field-scoped mutations; after failure, recompute the visible value from the baseline plus the remaining queue.\nFlush pending debounced writes on page teardown, respecting the keepalive body cap and retaining failed writes for retry.\nFor shared React chrome APIs, read [the package skill](..\u002F..\u002Fpackages\u002Fapp-shell\u002FSKILL.md); this skill keeps application patterns.\n\n\u003C!-- AUTHORED-BY Codex GPT-6 -->\n\n\u003C!-- AUTHORED-BY Codex GPT-6.1-Sol -->\n\n\u003C!-- AUTHORED-BY Claude Opus 4.8 -->\n\nFor the component API, [packages\u002Fapp-shell\u002FSKILL.md](..\u002F..\u002Fpackages\u002Fapp-shell\u002FSKILL.md) is authoritative.\n\n# App shell — optimistic, non-blocking pod mutations\n\nRead the companion [`AGENTS.md`](..\u002F..\u002FAGENTS.md)\nfirst; pairs with the [`solid-offline-patterns`](..\u002Fsolid-offline-patterns\u002FSKILL.md)\nskill (instant-load reads) — this one is the **write** side of the same \"the app feels instant\" goal.\n\nA pod write is a network round-trip (often a conditional PUT\u002FPATCH plus a refresh). Blocking the\ninteraction on it makes the UI feel sluggish — a dragged card hangs in mid-air until the server\nanswers. Instead, make mutations **optimistic**:\n\n1. **Update the UI immediately.** Apply the change to local state the instant the user acts — the\n   kanban card slides to its new column, the toggle flips, the title updates — before any network\n   call.\n2. **Persist asynchronously.** Fire the pod write **without blocking** the interaction, and crucially\n   **without the blocking full-refresh** that a normal mutation does (the local state is already\n   correct). Reconcile in the background on success (a live-sync\u002Frefresh will also catch any coupled\n   change the server made).\n3. **Show a small, non-intrusive save indicator** for in-flight writes: \"Saving…\" while pending, a\n   brief \"Saved\" on success that auto-clears to idle, \"Save failed\" on error. A fixed-corner pill\n   (`role=\"status\"`, `aria-live=\"polite\"`, hidden when idle) — never a modal or a blocking spinner.\n4. **On failure: show an error AND revert** the optimistic change. The revert is where the\n   correctness lives — see below.\n\n```ts\n\u002F\u002F Keep nextGeneration and this record's edit state in the store across renders.\nconst patch = moveToPatch(move); \u002F\u002F only the fields changed by this move\nif (isNoOp(visibleValue(edits), patch)) return;\nconst generation = ++nextGeneration;\nsetEdits((cur) => enqueueMutation(cur, generation, patch)); \u002F\u002F UI updates instantly\npersist((repo) => repo.applyWrite(id, move)).then(\n  () => setEdits((cur) => settleMutation(cur, generation, true)),\n  () => {\n    showSaveError();\n    setEdits((cur) => settleMutation(cur, generation, false));\n  },\n);\n```\n\n## Revert correctly — the two traps (both real review findings)\n\n### Trap 1 — reverting the WHOLE record clobbers concurrent edits to other fields\n\nWhile a failed write was in flight, the user may have edited a **different** field of the same\nitem. Keep each mutation as a field-scoped patch: a status move changes `status`\u002F`state`, a\npriority move changes `priority`. Recompute from the confirmed baseline and the remaining\npatches so unrelated edits survive.\n\n### Trap 2 — a stale failed write clobbers a NEWER mutation of the same item\n\nValue equality cannot establish ownership: with priority `0 → 1 → 2 → 1`, a late failure\nof the first write must not undo the newer successful edits. Generations identify mutations,\nbut a generation fence alone is insufficient: with `0 → 1 → 2` and **both writes failing**,\nthe second write's captured original is the unconfirmed `1`. Restoring it resurrects a failed\nedit, regardless of which failure arrives first.\n\n**Keep a confirmed baseline plus an ordered queue of mutations.** The visible record is the\nbaseline with the queue's patches applied in local intent order. On failure, remove that\nmutation and recompute; never restore its captured original. On success, mark it confirmed\nand fold only the confirmed prefix into the baseline. A successful newer mutation stays in\nthe queue while an older one is unresolved, so it remains visible without letting a late older\nsuccess overwrite it.\n\n```ts\ntype Fields = { priority: number; status: string; state: string; title: string };\ntype Item = Fields & { id: string };\ntype Mutation = { generation: number; patch: Partial\u003CFields>; confirmed: boolean };\ntype EditState = { baseline: Item; pending: Mutation[] };\n\n\u002F\u002F Store lifetime counter; never reuse a generation after deletion\u002Freplacement\u002Faccount switch.\nlet nextGeneration = 0;\n\nfunction visibleValue(state: EditState): Item {\n  return state.pending.reduce((item, mutation) => ({ ...item, ...mutation.patch }), state.baseline);\n}\n\nfunction enqueueMutation(state: EditState, generation: number, patch: Partial\u003CFields>): EditState {\n  return {\n    ...state,\n    pending: [...state.pending, { generation, patch: { ...patch }, confirmed: false }],\n  };\n}\n\nfunction settleMutation(state: EditState, generation: number, success: boolean): EditState {\n  if (!state.pending.some((mutation) => mutation.generation === generation)) return state;\n  let pending = success\n    ? state.pending.map((mutation) =>\n        mutation.generation === generation ? { ...mutation, confirmed: true } : mutation,\n      )\n    : state.pending.filter((mutation) => mutation.generation !== generation);\n  let baseline = state.baseline;\n  while (pending[0]?.confirmed) {\n    const [first, ...rest] = pending;\n    baseline = { ...baseline, ...first.patch };\n    pending = rest;\n  }\n  return { baseline, pending };\n}\n```\n\nInitialize one `EditState` per record from its confirmed server value with `pending: []`.\nAll local writers enqueue field-scoped patches. A confirmed entry waiting behind an unresolved\none remains in `pending` until it can join the baseline. These reducers are pure: React may\nreplay an updater without consuming a mutation. Drop the queue on deletion, record replacement,\nor account switch; callbacks for generations absent from the new state do nothing.\nSerialize pod writes per record or use conditional writes with conflict reconciliation to\npreserve server ordering; this queue governs local visibility. Generation-fence background\nrefreshes, and do not replace the baseline with a stale refresh while mutations remain.\n\n## Flush a debounced write on tab teardown — don't lose the last edit\n\nAn optimistic mutation that **debounces** the pod write (coalescing rapid edits into one PUT) has a\ngap the optimistic path itself doesn't cover: if the user **closes the tab, navigates away, or\nbackgrounds it** while a debounced write is still pending, the timer never fires and the **last edit\nis lost** — the UI showed \"Saving…\" (or even \"Saved\" optimistically) but nothing reached the pod. The\ndurable cache (`solid-offline`) preserves it for *that* browser, but a different device never sees it.\n\nFlush pending writes on the teardown signals — and mind the `keepalive` body cap:\n\n- **Flush on `pagehide` AND `visibilitychange` → `hidden` (and `beforeunload` as a belt-and-braces).**\n  `visibilitychange(hidden)` is the most reliable on mobile (a backgrounded tab the OS may kill never\n  fires `pagehide`\u002F`unload`); `pagehide` covers tab-close\u002Fnavigation. Treat them as the same \"the page\n  may be going away now — persist now\" trigger and de-dupe (below).\n- **Use `fetch(url, { keepalive: true })` so the request OUTLIVES the page** — a normal `fetch` is\n  cancelled when the document tears down, so the write never completes. `keepalive` lets the browser\n  finish it after the page is gone. **But `keepalive` has a hard ~64 KB cap on the encoded request\n  body** (the Fetch spec's `keepalive` inflight-body limit) — over it the `fetch` **rejects**. So:\n  encode the body first, and use `keepalive` **only when it fits**; an oversized snapshot falls back\n  to a **normal** `fetch` (best-effort — it may not finish, but it can't silently swallow the write).\n  (`navigator.sendBeacon` is the same cap and can't send the conditional `If-Match`\u002F`Content-Type`\n  headers a pod PUT needs, so prefer `keepalive` `fetch`.)\n- **Clear the pending marker only AFTER the write resolves — keep it for retry on failure.** A teardown\n  flush that optimistically marks the snapshot \"saved\" before the keepalive request resolves loses the\n  edit if that request fails; leave the durable-cache pending flag set until success so the next open\n  retries.\n- **Coalesce concurrent unload flushes of the SAME snapshot.** `pagehide` and `visibilitychange` can\n  both fire for one teardown; firing two keepalive PUTs of the same body **doubles** the bytes counted\n  against the per-page keepalive cap (and can race the conditional `If-Match`). Single-flight the flush\n  on the snapshot's identity\u002Fversion so one teardown sends **one** request. **But never coalesce a\n  keepalive flush onto a non-keepalive in-flight save** — a normal debounced save already in flight is\n  cancelled by the teardown, so the keepalive flush must still run; only coalesce keepalive-with-keepalive.\n\nThis is the teardown corner of the optimistic-mutation \u002F `solid-offline` invariant: optimistic +\ndurable-cache makes the edit *survive locally*; the keepalive flush is what makes it *reach the pod*\nwhen the tab dies mid-debounce. (Cited: the five jeswr OSS Solid forks — Linkding, Elk, Excalidraw,\nMiniflux, Actual — 2026-06; Excalidraw's debounced scene-persist needed the `pagehide` keepalive\nflush + the 64 KB cap fallback, hardened over roborev's fetch\u002Funload rounds.)\n\n## Indicator, no-ops, and reconciliation\n\n- **A move that doesn't change anything is a no-op** — a drop onto the card's *current* column must\n  not fire a write or show \"Saving…\". Compare the patch with `visibleValue(edits)` and bail.\n- **Keep the optimistic state in the durable cache too** (see `solid-offline`), so a reopen\n  mid-write paints the optimistic state rather than the pre-write one.\n- **Reconcile in the background after a successful persist** (a non-blocking refresh), so a change\n  the server coupled to your write — e.g. a workflow status that also flips an open\u002Fclosed flag —\n  lands without the user waiting on it.\n\n## Reading a pod container into a view (the read side)\n\nBuilding a list\u002Fbrowser view over a pod container surfaced three patterns worth applying every time (each a roborev finding while building 8 sibling Solid apps):\n\n- **Inject the authenticated `fetch` as a seam, don't hard-wire login.** The view\u002Fhook\u002Fdata-layer take an injectable `fetch` (fall back to the ambient global a reactive-auth shell patches). This builds + unit-tests *now* (stub the fetch) while the real login wires in later — the view is never coupled to the auth flow.\n- **Validate `ldp:contains` child IRIs before you fetch them.** A view that reads each child of a listed container must NOT blindly fetch every IRI the container advertises — a malicious\u002Fmalformed container can list arbitrary URLs\u002Fschemes (an SSRF vector, and it runs before any href-display gate). Require each child to be: an `http(s):` IRI, **same-origin** with the container (compare parsed `URL.origin`, not a raw string prefix — defeats `https:\u002F\u002Fyou@evil\u002F…` userinfo + look-alike-prefix tricks), and a **real descendant path** (compare `URL.pathname` under the container's slash-terminated path with a non-empty remainder — so the container itself, even with `?query`\u002F`#fragment`, is rejected). Drop anything else (don't fetch, don't fail the listing).\n- **A data-layer `list()` that swallows 401\u002F403 → `[]` is right for the store but WRONG for a screen.** It makes \"you don't have permission\" indistinguishable from \"empty\", so a forbidden container renders \"Nothing here\" instead of an access-denied state. Wrap it in a thin **UI read facade** that surfaces a typed `AccessDeniedError` (401\u002F403), maps **404 → empty**, **2xx-empty → empty**, else re-throws — without changing the shared store contract other callers depend on. And on an access error during a *reload*, **clear the previously-loaded list + selection** so stale data doesn't linger under the access-denied state.\n\n\n\n\u003C!-- AUTHORED-BY Claude Opus 5.5 -->\n\n## Offline conventions in the Solid Suite shell (`apps\u002Fsuite`)\n\n- **`requiresOnline`.** Writes work offline everywhere (they queue in the outbox) except controls\n  that need a connection: share changes, registration, connector sign-in, purging the trash.\n  Wrap each in `\u003CRequiresOnline>` (`src\u002Fshell\u002Fsync\u002Frequires-online.tsx`); it renders suite-ui's\n  `OnlineGate`, which disables the control while the shell is offline or reconnecting and\n  explains \"You're offline. This needs a connection.\" in a keyboard- and pointer-reachable\n  tooltip. Use `useNeedsConnection()` when only the flag is needed (a whole fieldset). The\n  control must forward `disabled`\u002F`aria-disabled`. First use: the share dialog's Add button.\n- **Connection state** comes from `useConnectionState()` (\"online\" | \"offline\" |\n  \"reconnecting\"): `navigator.onLine` plus, while offline, an unauthenticated opaque HEAD to the\n  active storage root every 30 s; \"Reconnecting…\" shows for at least 1.5 s. Outside the shell it\n  falls back to `navigator.onLine`. Never switch on `navigator.onLine` directly in a shell control.\n- **Outbox.** `useOutbox()` (`src\u002Fshell\u002Fsync\u002Foffline-provider.tsx`) is the seam the SyncSheet\n  reads until the SDK outbox lands: `enqueue({ label, where })` records a change *description*\n  (never contents); a reconnect sends pending items; failed items wait for Retry.\n- **Recent items** (behind `\u002Foffline`) record the shell's `pageTitle` and pathname only, per\n  account; no queries, fragments or document contents.\n- **Service worker** (`\u002Fservice-worker`, production only): precaches shell routes and `\u002F_next\u002Fstatic`\n  assets and answers offline navigations, falling back to `\u002Foffline`. It never caches storage\n  responses, requests with `Authorization`\u002F`DPoP`, or cross-origin responses.\n\n## Detailed integration patterns\n\n- Read for cross-app class mapping, prebuild environment precedence, and controlled forms. [references\u002Finterop-and-forms.md](references\u002Finterop-and-forms.md).\n- Read when integrating shared chrome, Tailwind tokens, theming, or Lit\u002FReact controls. [references\u002Fchrome-integration.md](references\u002Fchrome-integration.md).\n\n## Pitfalls\n\n### Paginated sources and snapshot overwrites\n\nWhen syncing a local API into a pod by replacing a whole RDF document, a fresh dataset plus\nconditional PUT overwrites everything, even if the source API silently capped the first page.\nAn oversized `limit` is not proof of completeness. Follow every page\u002Fcursor until the API's\ncompletion condition (for example, `offset >= total`), assemble the complete snapshot, then\nserialize through the suite RDF writer and perform the conditional write. If a page fails or\npagination stops making progress, fail the sync without writing a partial replacement.\nAn ETag prevents conflicting writes; it cannot detect a truncated source snapshot.\n\n## Gotchas\n\n| Gotcha | Detail |\n|---|---|\n| Interaction hangs until the pod answers | The write is blocking — update local state first, persist async, never `await` before the UI updates |\n| Editor breaks on the empty string mid-edit | A controlled input wired straight to a throwing typed setter (`@solid\u002Fobject` `…As`) throws on every transiently-invalid keystroke — store the **raw** string in local state, never throw in `onChange`, validate the assembled draft separately, call the setter only at save with a valid value |\n| Host app's `button {}` repaints your shell's controls | Tailwind v4: an **unlayered** author rule beats EVERY `@layer`'d utility — `@layer`\u002Fspecificity bumps don't fix it. Ship an unlayered attribute-scoped reset (`[data-app-shell-control]{…}`, 0,1,0 > a bare element's 0,0,1 when both unlayered) + a **private literal** token mirror (`--as-accent`, not `var(--accent)` indirection) declared on a `:root`\u002Fshared ancestor so portaled menus\u002Fdialogs inherit it |\n| Dark-OS user sees a one-frame light flash | A `ThemeProvider` resolving\u002Fapplying the theme in a passive `useEffect` runs after paint, so `resolvedTheme` starts `light`. Apply in an **isomorphic layout effect** (`useLayoutEffect` in-browser, `useEffect` off-browser via a `typeof window` guard) — correct on the first painted frame, SSR-safe; a pre-hydration class-toggling `\u003Cscript>` doesn't fix React state |\n| Web-Component prop dropped via the React wrapper | `@lit\u002Freact` `createComponent` classifies props before the Lit class finalizes, so a non-reflected reactive **property** is silently dropped under React 19 — the element renders its fallback (e.g. `Loading` shows generic \"Loading\"). Make the prop `reflect: true`, or consume the raw element with a DOM **attribute** (`\u003Cjeswr-loading label=\"…\">`) |\n| `@lit\u002Freact` prop won't render in a vitest test | `@lit\u002Freact` resolves its **`node`** export condition under vitest\u002Fjsdom, whose build SKIPS the `useLayoutEffect` that forwards props — so a React-wrapper assertion (`render(\u003CLoading label\u002F>)` then check the label) **can't pass even with `reflect: true`**; it's an env artifact, not a bug. Test the **raw element**: set the property directly, then assert the reflected attribute + the rendered `::part`, not the wrapper |\n| Host `button {}` distorts the shared controls' SIZE | A chrome library's reset isolates **color\u002Fborder\u002Ffill** but leaves the **box model** to its own layered classes — so a consumer's bare unlayered global `button {}` still out-ranks that layered sizing and squashes the shared controls. Scope host element rules (`.login-form button`), or exclude the controls with `button:where(:not([data-app-shell-control]))`; only globally relax what the reset covers, never the box model |\n| Bare `:not([attr])` exclusion repaints your OWN buttons | The exclusion-selector trap: `button:not([data-app-shell-control])` **leaks the attribute's specificity through `:not()`** → `(0,1,1)`, out-ranking your class-only host overrides (`.foo-link`\u002F`.foo-cancel` at `(0,1,0)`) and repainting them with the base look. Wrap it: `button:where(:not([…]))` carries **zero** specificity → stays `(0,0,1)`. Guard with a test rejecting BOTH the unscoped and the bare-`:not()` form |\n| App shows the SUITE palette instead of its own | To consume `@jeswr\u002Fapp-shell` on a Tailwind-v4 app while keeping your own colours: **alias** the shell-private `--as-*` tokens onto your palette on **both `:root` and `.dark`**, register the `as-*` keys in `@theme` + set `darkMode: 'class'`, and import **only the shell's reset** — NOT its suite theme-token sheet (which re-declares `--as-*` with the suite colours and overrides your aliases). Re-point the token seam; don't fork the shell |\n| `npm run build` bakes a localhost client-id | A prebuild config script doesn't get the bundler's `.env` loading — load `.env`\u002F`.env.local` yourself via `node:util` `parseEnv`; a wrong client-id origin = broken login at the deployed subdomain |\n| `.env.local` fails to fully override `.env` | Resolve the origin **per-layer** (`shell → .env.local → .env → default`, first layer that yields one wins), never merge into one dict + pick per-variable — that lets `.env` beat `.env.local` cross-variable |\n| Forbidden container shows \"empty\" | A store `list()` swallowing 401\u002F403→`[]` hides access-denied — wrap in a UI facade that surfaces a typed AccessDenied; clear stale list on a reload that 403s |\n| View fetches an attacker's URL | Don't fetch every `ldp:contains` IRI — require http(s) + same-origin (parsed `origin`) + a real descendant `pathname` before fetching a child |\n| A producer app's data shows under \"Other\" | A consumer must map EVERY producer's Type-Index `solid:forClass` IRI into its own category\u002Fview map (both `https`\u002F`http` schema.org forms) — an unmapped class is still discovered but mis-bucketed into the fallback (cited: pod-docs' `pd:Document`); add the mapping + a regression test when you add a producer app |\n| Concurrent edits lost on revert | Trap 1 — enqueue field-scoped patches and recompute from the confirmed baseline plus remaining mutations |\n| Newer move undone by an older failure | Trap 2 — remove only the failed generation from the queue; retain newer edits and never restore an unconfirmed original |\n| Spurious \"Saving…\" on a no-op drop | Compare the patch with the visible value and skip the write when nothing changes |\n| Indicator clutters the UI | Hide when idle; auto-clear \"Saved\" back to idle after ~1.5 s; fixed-corner pill, `aria-live=\"polite\"`, not a modal |\n| Coupled server change missing after persist | Background-reconcile on success — the server may have changed a field your write didn't set |\n| Last edit lost when the tab is closed mid-debounce | A debounced pod write whose timer hasn't fired is lost on tab-close\u002Fnavigate\u002Fbackground. Flush on `pagehide` **and** `visibilitychange→hidden` (mobile-reliable) with `fetch(url,{keepalive:true})` so the request outlives the page; clear the pending marker only AFTER it resolves (keep it for retry) |\n| `keepalive` flush rejects on a big body | `keepalive` has a hard ~64 KB encoded-body cap — over it the `fetch` rejects and the write silently never sends. Encode first, use `keepalive` only when it fits; an oversized snapshot falls back to a **normal** `fetch` (best-effort). `sendBeacon` has the same cap and can't carry the `If-Match`\u002F`Content-Type` a pod PUT needs |\n| Two keepalive PUTs of one snapshot blow the cap | `pagehide` + `visibilitychange` both fire for one teardown — single-flight the flush on the snapshot's version so one teardown = one request. But never coalesce a keepalive flush onto a non-keepalive in-flight save (the normal save is cancelled by the teardown; the keepalive flush must still run) |\n\n---\n\n*Learned building [`jeswr\u002Fsolid-issues`](..\u002F..\u002Fapps\u002Fissues\u002FREADME.md): the optimistic\nboard logic in [`src\u002Flib\u002Fboard.ts`](..\u002F..\u002Fapps\u002Fissues\u002Fsrc\u002Flib\u002Fboard.ts)\n(`optimisticMove`, `revertMoveIfCurrent` — both revert traps), the non-blocking `persist` in\n[`src\u002Flib\u002Fuse-issues.ts`](..\u002F..\u002Fapps\u002Fissues\u002Fsrc\u002Flib\u002Fuse-issues.ts),\nand the [`src\u002Fcomponents\u002Fsave-indicator.tsx`](..\u002F..\u002Fapps\u002Fissues\u002Fsrc\u002Fcomponents\u002Fsave-indicator.tsx)\npill, commit `ca0c687`. Both revert traps were roborev findings fixed in that change.*\n",{"name":5,"description":7},"main","5482abfe2666cc12f835fe360e8fad1f1e1dea8c","skills\u002Fsolid-app-shell",0,"https:\u002F\u002Fgithub.com\u002Fjeswr\u002Fsolid-sdk","https:\u002F\u002Fgithub.com\u002Fjeswr","jeswr.org\u002F#me","@solid Lead @theodi | PhD Candidate @OxfordHCC\r\n\r\n","2026-11-15 05:20:24",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add jeswr\u002Fsolid-sdk --skill solid-app-shell",{"tool":39,"command":40},"bunx","bunx skills add jeswr\u002Fsolid-sdk --skill solid-app-shell",{"tool":42,"command":43},"pnpm","pnpm dlx skills add jeswr\u002Fsolid-sdk --skill solid-app-shell","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjeswr\u002Fsolid-sdk\u002Fblob\u002Fmain\u002Fskills\u002Fsolid-app-shell\u002FSKILL.md",true,[47,53],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"references\u002Fchrome-integration.md","REFERENCE","参考文档",16380,"https:\u002F\u002Fgithub.com\u002Fjeswr\u002Fsolid-sdk\u002Fblob\u002Fmain\u002Fskills\u002Fsolid-app-shell\u002Freferences\u002Fchrome-integration.md",{"path":54,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":55,"sourceHtmlUrl":56},"references\u002Finterop-and-forms.md",7269,"https:\u002F\u002Fgithub.com\u002Fjeswr\u002Fsolid-sdk\u002Fblob\u002Fmain\u002Fskills\u002Fsolid-app-shell\u002Freferences\u002Finterop-and-forms.md",[58,65,72,79,86,93],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M78FNRF6EV6SKPEYRZ6JTTQ3","storage-conformance","Work on @jeswr\u002Fstorage-conformance, the shared storage conformance suite package in the Solid SDK workspace.","https:\u002F\u002Fgithub.com\u002Fjeswr\u002Fsolid-sdk\u002Fblob\u002Fmain\u002Ftools\u002Fstorage-conformance\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M78FNMS7HQGD9EE43WAFEW6A","fetch-rdf-engine-tests","Maintain fetch-rdf's real Node WASM parser integration tests without introducing a reverse engine dependency in fetch-rdf.","https:\u002F\u002Fgithub.com\u002Fjeswr\u002Fsolid-sdk\u002Fblob\u002Fmain\u002Ftools\u002Ffetch-rdf-engine-tests\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M78FNK5M6ASAR3909JT6BZV1","alpha","Use when checking fixtures, including folded YAML descriptions.","https:\u002F\u002Fgithub.com\u002Fjeswr\u002Fsolid-sdk\u002Fblob\u002Fmain\u002Ftest\u002Ffixtures\u002Fcheck-skills\u002Fvalid\u002Fskills\u002Falpha\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M78FNGATR8F4N09HWSFVWBAF","widget","Use when testing package skills: YAML quoting works.","https:\u002F\u002Fgithub.com\u002Fjeswr\u002Fsolid-sdk\u002Fblob\u002Fmain\u002Ftest\u002Ffixtures\u002Fcheck-skills\u002Fvalid\u002Fpackages\u002Fwidget\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M78FN9M05GCHYTK848SSMN9R","web-seo","Use when improving technical and entity SEO for a modern personal, portfolio, documentation, or marketing site, including crawlable HTML, canonical metadata, sitemap and robots, Person\u002FProfilePage JSON-LD, Core Web Vitals, and honest ranking expectations.","https:\u002F\u002Fgithub.com\u002Fjeswr\u002Fsolid-sdk\u002Fblob\u002Fmain\u002Fskills\u002Fweb-seo\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M78FN5ANETMSPMEFACSJ7JMC","solid-wac","Use when implementing or auditing Solid server WAC authorization, ACL creation and inheritance, auxiliary-resource escalation, method-to-mode mapping, 401 versus 403 challenges, WAC-Allow, or defensive typed ACL parsing with @solid\u002Fobject and @rdfjs\u002Fwrapper.","https:\u002F\u002Fgithub.com\u002Fjeswr\u002Fsolid-sdk\u002Fblob\u002Fmain\u002Fskills\u002Fsolid-wac\u002FSKILL.md",[],[]]