[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7828DS45Z5G8DSMA8FR7DBK":3,"skill-same:01M7828DS45Z5G8DSMA8FR7DBK":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},"01M7828DS45Z5G8DSMA8FR7DBK","improve-codebase-architecture",null,"Architectural exploration — seam decisions, entry-module isolation, zero-dep core gate. Plan under docs\u002Fplans\u002F. Use when improving architecture, consolidating modules, or enforcing import boundaries.","stainless-code\u002Fpersist","stainless-code","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F188862219?v=4","01M7826VYMCF2NTQWQZRWQ454T","STAINLESS CODE","01M7826VZKNC149Y9ZNK0F93N7",5,"MIT","https:\u002F\u002Fgithub.com\u002Fstainless-code\u002Fpersist\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fimprove-codebase-architecture\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: improve-codebase-architecture\ndescription: Architectural exploration — seam decisions, entry-module isolation, zero-dep core gate. Plan under docs\u002Fplans\u002F. Use when improving architecture, consolidating modules, or enforcing import boundaries.\n---\n\n# Improve Codebase Architecture\n\n**This repo** uses plan files under `docs\u002Fplans\u002F` instead of temp reports; vocabulary in [LANGUAGE.md](.\u002FLANGUAGE.md) is the architecture nouns. Domain terms: [`docs\u002Fglossary.md`](..\u002F..\u002F..\u002Fdocs\u002Fglossary.md) (persistence language: backend, codec, source, envelope, hydration signal).\n\nExplore a slice of the codebase (a seam, an entry point, a module cluster) like an AI would, surface architectural friction, discover opportunities for improving testability and module boundaries, and propose deepening \u002F boundary-enforcement refactors as **plan files** under `docs\u002Fplans\u002F` (see Step 7).\n\nA **deep module** (John Ousterhout, \"A Philosophy of Software Design\") has a small interface hiding a large implementation. Deep modules are more testable, more AI-navigable, and let you test at the seam instead of inside.\n\n## Architecture vocabulary — read first\n\nUse the terms in [LANGUAGE.md](.\u002FLANGUAGE.md) **exactly** in every suggestion this skill produces — module, interface, implementation, depth, seam, adapter, leverage, locality, deletion test. Consistent vocabulary is what stops a deepening conversation from drifting into \"component \u002F service \u002F boundary\" mush. Pass the vocabulary to every sub-agent spawned in Step 5 alongside the technical brief so designs come back named consistently.\n\nThe vocabulary is **separate from domain glossaries** — `LANGUAGE.md` covers architecture nouns (`module`, `seam`); [`docs\u002Fglossary.md`](..\u002F..\u002F..\u002Fdocs\u002Fglossary.md) holds canonical persistence nouns (`backend`, `codec`, `source`, `envelope`, `hydration signal`). All belong in the same conversation.\n\n## Process\n\n### 1. Explore the slice\n\nUse a **read-only explore subagent** to navigate the slice naturally. Don't follow rigid heuristics — explore organically and note where you experience friction:\n\n- Where does understanding one concept require bouncing between many small files?\n- Where are modules so shallow that the interface is nearly as complex as the implementation?\n- Where have pure functions been extracted just for testability, but the real bugs hide in how they're called?\n- Where do tightly-coupled modules create integration risk in the seams between them?\n- Which parts are untested, or hard to test (DOM-coupled when they could be `bun:test`-fast)?\n- Where does a subpath entry leak its optional peer into the zero-dep core, or reach across to another entry's internals?\n- Where does `src\u002F` lack a public-surface convention — internal helpers exported from `index.ts` alongside the public API?\n- Where is the **zero-dep core gate** at risk — a new import in `persist-core` \u002F `hydration` pulling a peer dep value?\n\nThe friction you encounter IS the signal.\n\n**Done when:** ≥3 candidates listed with cluster + dependency category.\n\n### 2. Present candidates\n\nPresent a numbered list of opportunities. For each candidate, show:\n\n- **Cluster**: which modules \u002F entry points \u002F seams are involved.\n- **Why they're coupled**: shared types, call patterns, co-ownership of a concept, seam-crossing imports.\n- **Dependency category**: see [REFERENCE.md](.\u002FREFERENCE.md) (\"Dependency Categories\"). Common cases in this repo: category 1 (in-process pure functions — most of `persist-core`, codec `encode`\u002F`decode`); category 2 (local-substitutable — in-memory `StateStorage` test doubles, `HydrationSignal` observed without a real store).\n- **Test impact**: what existing `bun:test` \u002F `tests-dom` coverage would be replaced by boundary tests; whether a new architectural regression test (in the spirit of the zero-dep core gate test) should land alongside.\n- **Boundary enforcement option**: when relevant, the oxlint rule that would codify it — see [REFERENCE.md § Boundary enforcement](.\u002FREFERENCE.md#boundary-enforcement-oxlint) (this repo uses oxlint only; do not propose `eslint-plugin-boundaries`).\n\nDon't propose interfaces yet. Ask the user: \"Which of these would you like to explore?\"\n\n### 3. User picks a candidate\n\n### 4. Frame the problem space\n\nBefore spawning sub-agents, write a user-facing explanation of the problem space for the chosen candidate:\n\n- The constraints any new interface \u002F boundary rule would need to satisfy (existing import sites, the test surface, the published `.d.mts` public API, `docs\u002Farchitecture.md` seam model).\n- The dependencies it would need to rely on (`StateStorage\u003CTRaw>`, `StorageCodec\u003CS, TRaw>`, `PersistableSource\u003CTState>`, the `HydrationSignal` observation contract, the [`docs\u002Fglossary.md`](..\u002F..\u002F..\u002Fdocs\u002Fglossary.md) ubiquitous language).\n- A rough illustrative code sketch to make the constraints concrete — this is **not** a proposal, just a way to ground the constraints.\n\nShow this to the user, then immediately proceed to Step 5. The user reads and thinks about the problem while the sub-agents work in parallel.\n\n### 5. Design multiple interfaces (or boundary structures)\n\nSpawn 3+ subagents in parallel (`generalPurpose` is usually right; `explore` if read-only). Each must produce a **radically different** design.\n\nPrompt each sub-agent with a separate technical brief (file paths, coupling details, dependency category, what's being hidden \u002F enforced). This brief is independent of the user-facing explanation in Step 4. Give each agent a different design constraint:\n\n- Agent 1: \"Minimize the interface — aim for 1–3 entry points max.\"\n- Agent 2: \"Maximize flexibility — support many use cases and extension (new codecs, new backends, new framework adapters).\"\n- Agent 3: \"Optimize for the most common caller — make the default case trivial (one-line `persistSource` composition).\"\n- Agent 4 (when applicable): \"Design around the ports & adapters pattern for a cross-boundary dependency (a new backend that owns its transport — IndexedDB, a future remote storage).\"\n- Agent 4 alternate (boundary-enforcement candidate): design an oxlint `overrides[]` block and post-refactor `src\u002F` shape per [REFERENCE.md § Boundary enforcement](.\u002FREFERENCE.md#boundary-enforcement-oxlint).\n\nEach sub-agent outputs:\n\n1. Interface signature (types, methods, params) — or, for boundary candidates, the lint config + the post-refactor folder shape.\n2. Usage example showing how callers use it.\n3. What complexity it hides internally — or, for boundary candidates, which classes of import become impossible.\n4. Dependency strategy (how deps are handled — see [REFERENCE.md](.\u002FREFERENCE.md)).\n5. Trade-offs.\n\nPresent designs sequentially, then compare them in prose (need ≥3 sub-agent outputs before comparing).\n\nAfter comparing, give your own recommendation: which design you think is strongest and why. If elements from different designs would combine well, propose a hybrid. Be opinionated — the user wants a strong read, not just a menu.\n\n### 6. User picks an interface (or accepts recommendation)\n\nIf the choice between candidates is non-obvious — multiple designs survive the comparison, the user keeps asking \"but what about X?\", or the dependency graph between decisions isn't clear — drop into [`grill-with-docs`](..\u002Fgrill-with-docs\u002FSKILL.md) before writing the plan. The grilling loop walks the decision tree branch-by-branch, surfaces hidden constraints, and writes resolved terminology back into [`docs\u002Fglossary.md`](..\u002F..\u002F..\u002Fdocs\u002Fglossary.md) inline. The plan file in Step 7 then captures decisions instead of options.\n\nThe deletion test (per [LANGUAGE.md § Principles](.\u002FLANGUAGE.md#principles)) is also worth re-running here: for each candidate, ask \"if we deleted the new module 18 months from now, would the complexity it hides reappear across N callers, or just move?\" If \"just move\", the deepening is a wash and you should pick a different candidate.\n\n### 7. Create a plan file\n\nThe output of this skill is a **plan file** under `docs\u002Fplans\u002F`. Pick the path based on what the refactor touches:\n\n- **Cross-cutting \u002F any refactor** (this repo is one surface): `docs\u002Fplans\u002F\u003Cshort-kebab-name>.md` using the template in [REFERENCE.md](.\u002FREFERENCE.md).\n- **Roadmap entry**: one line under the appropriate section in [`docs\u002Froadmap.md`](..\u002F..\u002F..\u002Fdocs\u002Froadmap.md).\n\nWrite the plan, then share the file path(s) and any roadmap-link paths so the user can open them. Don't ask for review before writing.\n\n**Done when:** plan file at path; roadmap link.\n\nIf the user explicitly asks for a GitHub issue, draft the issue body but do **not** create it directly — the user files it themselves.\n\n**Plan-file conventions:** [REFERENCE.md § Project-specific conventions](.\u002FREFERENCE.md#project-specific-conventions).\n","# Improve Codebase Architecture\n\n**This repo** uses plan files under `docs\u002Fplans\u002F` instead of temp reports; vocabulary in [LANGUAGE.md](.\u002FLANGUAGE.md) is the architecture nouns. Domain terms: [`docs\u002Fglossary.md`](..\u002F..\u002F..\u002Fdocs\u002Fglossary.md) (persistence language: backend, codec, source, envelope, hydration signal).\n\nExplore a slice of the codebase (a seam, an entry point, a module cluster) like an AI would, surface architectural friction, discover opportunities for improving testability and module boundaries, and propose deepening \u002F boundary-enforcement refactors as **plan files** under `docs\u002Fplans\u002F` (see Step 7).\n\nA **deep module** (John Ousterhout, \"A Philosophy of Software Design\") has a small interface hiding a large implementation. Deep modules are more testable, more AI-navigable, and let you test at the seam instead of inside.\n\n## Architecture vocabulary — read first\n\nUse the terms in [LANGUAGE.md](.\u002FLANGUAGE.md) **exactly** in every suggestion this skill produces — module, interface, implementation, depth, seam, adapter, leverage, locality, deletion test. Consistent vocabulary is what stops a deepening conversation from drifting into \"component \u002F service \u002F boundary\" mush. Pass the vocabulary to every sub-agent spawned in Step 5 alongside the technical brief so designs come back named consistently.\n\nThe vocabulary is **separate from domain glossaries** — `LANGUAGE.md` covers architecture nouns (`module`, `seam`); [`docs\u002Fglossary.md`](..\u002F..\u002F..\u002Fdocs\u002Fglossary.md) holds canonical persistence nouns (`backend`, `codec`, `source`, `envelope`, `hydration signal`). All belong in the same conversation.\n\n## Process\n\n### 1. Explore the slice\n\nUse a **read-only explore subagent** to navigate the slice naturally. Don't follow rigid heuristics — explore organically and note where you experience friction:\n\n- Where does understanding one concept require bouncing between many small files?\n- Where are modules so shallow that the interface is nearly as complex as the implementation?\n- Where have pure functions been extracted just for testability, but the real bugs hide in how they're called?\n- Where do tightly-coupled modules create integration risk in the seams between them?\n- Which parts are untested, or hard to test (DOM-coupled when they could be `bun:test`-fast)?\n- Where does a subpath entry leak its optional peer into the zero-dep core, or reach across to another entry's internals?\n- Where does `src\u002F` lack a public-surface convention — internal helpers exported from `index.ts` alongside the public API?\n- Where is the **zero-dep core gate** at risk — a new import in `persist-core` \u002F `hydration` pulling a peer dep value?\n\nThe friction you encounter IS the signal.\n\n**Done when:** ≥3 candidates listed with cluster + dependency category.\n\n### 2. Present candidates\n\nPresent a numbered list of opportunities. For each candidate, show:\n\n- **Cluster**: which modules \u002F entry points \u002F seams are involved.\n- **Why they're coupled**: shared types, call patterns, co-ownership of a concept, seam-crossing imports.\n- **Dependency category**: see [REFERENCE.md](.\u002FREFERENCE.md) (\"Dependency Categories\"). Common cases in this repo: category 1 (in-process pure functions — most of `persist-core`, codec `encode`\u002F`decode`); category 2 (local-substitutable — in-memory `StateStorage` test doubles, `HydrationSignal` observed without a real store).\n- **Test impact**: what existing `bun:test` \u002F `tests-dom` coverage would be replaced by boundary tests; whether a new architectural regression test (in the spirit of the zero-dep core gate test) should land alongside.\n- **Boundary enforcement option**: when relevant, the oxlint rule that would codify it — see [REFERENCE.md § Boundary enforcement](.\u002FREFERENCE.md#boundary-enforcement-oxlint) (this repo uses oxlint only; do not propose `eslint-plugin-boundaries`).\n\nDon't propose interfaces yet. Ask the user: \"Which of these would you like to explore?\"\n\n### 3. User picks a candidate\n\n### 4. Frame the problem space\n\nBefore spawning sub-agents, write a user-facing explanation of the problem space for the chosen candidate:\n\n- The constraints any new interface \u002F boundary rule would need to satisfy (existing import sites, the test surface, the published `.d.mts` public API, `docs\u002Farchitecture.md` seam model).\n- The dependencies it would need to rely on (`StateStorage\u003CTRaw>`, `StorageCodec\u003CS, TRaw>`, `PersistableSource\u003CTState>`, the `HydrationSignal` observation contract, the [`docs\u002Fglossary.md`](..\u002F..\u002F..\u002Fdocs\u002Fglossary.md) ubiquitous language).\n- A rough illustrative code sketch to make the constraints concrete — this is **not** a proposal, just a way to ground the constraints.\n\nShow this to the user, then immediately proceed to Step 5. The user reads and thinks about the problem while the sub-agents work in parallel.\n\n### 5. Design multiple interfaces (or boundary structures)\n\nSpawn 3+ subagents in parallel (`generalPurpose` is usually right; `explore` if read-only). Each must produce a **radically different** design.\n\nPrompt each sub-agent with a separate technical brief (file paths, coupling details, dependency category, what's being hidden \u002F enforced). This brief is independent of the user-facing explanation in Step 4. Give each agent a different design constraint:\n\n- Agent 1: \"Minimize the interface — aim for 1–3 entry points max.\"\n- Agent 2: \"Maximize flexibility — support many use cases and extension (new codecs, new backends, new framework adapters).\"\n- Agent 3: \"Optimize for the most common caller — make the default case trivial (one-line `persistSource` composition).\"\n- Agent 4 (when applicable): \"Design around the ports & adapters pattern for a cross-boundary dependency (a new backend that owns its transport — IndexedDB, a future remote storage).\"\n- Agent 4 alternate (boundary-enforcement candidate): design an oxlint `overrides[]` block and post-refactor `src\u002F` shape per [REFERENCE.md § Boundary enforcement](.\u002FREFERENCE.md#boundary-enforcement-oxlint).\n\nEach sub-agent outputs:\n\n1. Interface signature (types, methods, params) — or, for boundary candidates, the lint config + the post-refactor folder shape.\n2. Usage example showing how callers use it.\n3. What complexity it hides internally — or, for boundary candidates, which classes of import become impossible.\n4. Dependency strategy (how deps are handled — see [REFERENCE.md](.\u002FREFERENCE.md)).\n5. Trade-offs.\n\nPresent designs sequentially, then compare them in prose (need ≥3 sub-agent outputs before comparing).\n\nAfter comparing, give your own recommendation: which design you think is strongest and why. If elements from different designs would combine well, propose a hybrid. Be opinionated — the user wants a strong read, not just a menu.\n\n### 6. User picks an interface (or accepts recommendation)\n\nIf the choice between candidates is non-obvious — multiple designs survive the comparison, the user keeps asking \"but what about X?\", or the dependency graph between decisions isn't clear — drop into [`grill-with-docs`](..\u002Fgrill-with-docs\u002FSKILL.md) before writing the plan. The grilling loop walks the decision tree branch-by-branch, surfaces hidden constraints, and writes resolved terminology back into [`docs\u002Fglossary.md`](..\u002F..\u002F..\u002Fdocs\u002Fglossary.md) inline. The plan file in Step 7 then captures decisions instead of options.\n\nThe deletion test (per [LANGUAGE.md § Principles](.\u002FLANGUAGE.md#principles)) is also worth re-running here: for each candidate, ask \"if we deleted the new module 18 months from now, would the complexity it hides reappear across N callers, or just move?\" If \"just move\", the deepening is a wash and you should pick a different candidate.\n\n### 7. Create a plan file\n\nThe output of this skill is a **plan file** under `docs\u002Fplans\u002F`. Pick the path based on what the refactor touches:\n\n- **Cross-cutting \u002F any refactor** (this repo is one surface): `docs\u002Fplans\u002F\u003Cshort-kebab-name>.md` using the template in [REFERENCE.md](.\u002FREFERENCE.md).\n- **Roadmap entry**: one line under the appropriate section in [`docs\u002Froadmap.md`](..\u002F..\u002F..\u002Fdocs\u002Froadmap.md).\n\nWrite the plan, then share the file path(s) and any roadmap-link paths so the user can open them. Don't ask for review before writing.\n\n**Done when:** plan file at path; roadmap link.\n\nIf the user explicitly asks for a GitHub issue, draft the issue body but do **not** create it directly — the user files it themselves.\n\n**Plan-file conventions:** [REFERENCE.md § Project-specific conventions](.\u002FREFERENCE.md#project-specific-conventions).\n",{"name":5,"description":7},"main","29ca2183c92cd13e04ce6c14fb431fd6993862cd",".agents\u002Fskills\u002Fimprove-codebase-architecture",0,"https:\u002F\u002Fgithub.com\u002Fstainless-code\u002Fpersist","https:\u002F\u002Fgithub.com\u002Fstainless-code","https:\u002F\u002Fstainless-code.com\u002F","Open-source tooling for JS\u002FTS and AI agents.","2026-11-01 20:56:20",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add stainless-code\u002Fpersist --skill improve-codebase-architecture",{"tool":39,"command":40},"bunx","bunx skills add stainless-code\u002Fpersist --skill improve-codebase-architecture",{"tool":42,"command":43},"pnpm","pnpm dlx skills add stainless-code\u002Fpersist --skill improve-codebase-architecture","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fstainless-code\u002Fpersist\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fimprove-codebase-architecture\u002FSKILL.md",true,[47,53],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"LANGUAGE.md","REFERENCE","参考文档",8982,"https:\u002F\u002Fgithub.com\u002Fstainless-code\u002Fpersist\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fimprove-codebase-architecture\u002FLANGUAGE.md",{"path":54,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":55,"sourceHtmlUrl":56},"REFERENCE.md",12540,"https:\u002F\u002Fgithub.com\u002Fstainless-code\u002Fpersist\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fimprove-codebase-architecture\u002FREFERENCE.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},"01M782D4ZQGJPNT470FSKDB6A8","vue-persist","Gate Vue 3 UI on Persist hydration with useHydrated (shallowRef). Use in setup\u002FeffectScope when avoiding flash of default state on async backends.","https:\u002F\u002Fgithub.com\u002Fstainless-code\u002Fpersist\u002Fblob\u002Fmain\u002Fskills\u002Fvue-persist\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},"01M782D1GJRWNQ3458F3H1FK2F","svelte-store-persist","Gate Svelte store-based UI on Persist hydration with hydratedStore (Readable). Use for Svelte 3–4 or Svelte 5 apps that still use stores; runes UI → svelte-persist.","https:\u002F\u002Fgithub.com\u002Fstainless-code\u002Fpersist\u002Fblob\u002Fmain\u002Fskills\u002Fsvelte-store-persist\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},"01M782CWBTRWAQ52TBNQ8665CC","svelte-persist","Gate Svelte 5 runes UI on Persist hydration with hydratedRune (.current). Use for Svelte 5; for stores \u002F Svelte 3–4 use svelte-store-persist.","https:\u002F\u002Fgithub.com\u002Fstainless-code\u002Fpersist\u002Fblob\u002Fmain\u002Fskills\u002Fsvelte-persist\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},"01M782CR8Z2V3SJW661RTMWY2F","solid-persist","Gate Solid UI on Persist hydration with useHydrated (Accessor). Use when avoiding flash of default state on async backends; read hydrated() in reactive scopes.","https:\u002F\u002Fgithub.com\u002Fstainless-code\u002Fpersist\u002Fblob\u002Fmain\u002Fskills\u002Fsolid-persist\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},"01M782CJQGP7739WA9BS801HZP","react-persist","Gate React UI on Persist hydration with useHydrated + toHydrationSignal. Use when avoiding flash of default state on async backends (IndexedDB), SSR snapshot true, or wiring HydrationSignal into React 18\u002F19.","https:\u002F\u002Fgithub.com\u002Fstainless-code\u002Fpersist\u002Fblob\u002Fmain\u002Fskills\u002Freact-persist\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},"01M782CF96RMXCDETM5TF2JDRV","preact-persist","Gate Preact UI on Persist hydration with useHydrated (preact\u002Fcompat useSyncExternalStore). Use when avoiding flash of default state on async backends or wiring HydrationSignal into Preact.","https:\u002F\u002Fgithub.com\u002Fstainless-code\u002Fpersist\u002Fblob\u002Fmain\u002Fskills\u002Fpreact-persist\u002FSKILL.md",[],[]]