[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6KKHH2VSS4JDCSVZ0KPFHKQ":3,"skill-same:01M6KKHH2VSS4JDCSVZ0KPFHKQ":70},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":43,"commitSha":44,"skillDirectory":45,"forksCount":13,"repositoryHtmlUrl":46,"repositoryHomepageUrl":6,"ownerHtmlUrl":47,"ownerBlogUrl":6,"ownerDescription":48,"updatedAt":49,"install":50,"resources":63},"01M6KKHH2VSS4JDCSVZ0KPFHKQ","push-based-widget-module-pattern",null,"How to implement sidebar\u002Fwidget UI components that receive pushed data updates from a caller, using a singleton module pattern with exported factory and update functions plus module-level DOM refs for efficient partial re-renders.","AG064\u002FOpenSpace","AG064","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F184930299?v=4","01M6KHVFG7TB73NHX3RDYSTMH2","01M6KHVFMM7XA2PZA9Z83PHS3V",0,"MIT","https:\u002F\u002Fgithub.com\u002FAG064\u002FOpenSpace\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fpush-based-widget-module-pattern\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"push based widget module pattern","push","pattern","widget","module","singleton","implement","for","updates","dom","re","with","ui components","how to","functions","factory","how","data","update","components","2026-11-10 10:12:30",false,"---\nname: push-based-widget-module-pattern\ndescription: How to implement sidebar\u002Fwidget UI components that receive pushed data updates from a caller, using a singleton module pattern with exported factory and update functions plus module-level DOM refs for efficient partial re-renders.\n---\n\n# Push-Based Widget Module Pattern\n\nUse this pattern when a UI sidebar or widget component needs to be updated by its **caller** (push-based) rather than fetching data itself. Instead of a class or framework component, implement the widget as a plain module with singleton state, a factory function to create the DOM, and an update function to efficiently patch it.\n\n---\n\n## When to Use\n\n- A sidebar, panel, or widget is rendered once but updated frequently with new data.\n- The data source lives outside the component (e.g., a parent controller, event bus, or store).\n- You want lightweight partial re-renders without rebuilding the entire DOM tree.\n- You prefer a simple module interface over a class-based or framework-based component.\n\n---\n\n## Core Structure\n\n```\nwidgets\u002F\n  MyWidget.ts          # The module (singleton state + exports)\n  MyWidget.types.ts    # (Optional) Exported data interface\n```\n\n---\n\n## Step-by-Step Instructions\n\n### 1. Define the Data Interface\n\nExport a typed interface so callers know exactly what data to push.\n\n```typescript\n\u002F\u002F MyWidget.types.ts  (or inline at top of MyWidget.ts)\nexport interface MyWidgetData {\n  title: string;\n  items: string[];\n  status: \"idle\" | \"active\" | \"error\";\n  \u002F\u002F ... all fields the widget needs to render\n}\n```\n\n### 2. Declare Module-Level Singleton Refs\n\nAt module scope, keep references to the **container** and any **frequently updated child nodes**. This avoids querying the DOM on every update.\n\n```typescript\n\u002F\u002F MyWidget.ts\nimport type { MyWidgetData } from \".\u002FMyWidget.types\";\n\n\u002F\u002F Singleton DOM refs\nlet containerEl: HTMLElement | null = null;\nlet titleEl: HTMLElement | null = null;\nlet itemListEl: HTMLElement | null = null;\nlet statusEl: HTMLElement | null = null;\n\n\u002F\u002F Current state snapshot (optional — useful for diffing)\nlet currentData: MyWidgetData | null = null;\n```\n\n### 3. Export a Factory Function (`createMyWidget`)\n\nThe factory builds the full DOM tree **once**, stores refs to mutable nodes, and returns the root element to be mounted by the caller.\n\n```typescript\nexport function createMyWidget(): HTMLElement {\n  \u002F\u002F Build the container\n  containerEl = document.createElement(\"aside\");\n  containerEl.className = \"my-widget\";\n\n  \u002F\u002F Build static structure; keep refs to dynamic parts\n  titleEl = document.createElement(\"h2\");\n  titleEl.className = \"my-widget__title\";\n\n  itemListEl = document.createElement(\"ul\");\n  itemListEl.className = \"my-widget__list\";\n\n  statusEl = document.createElement(\"span\");\n  statusEl.className = \"my-widget__status\";\n\n  \u002F\u002F Compose the tree\n  const header = document.createElement(\"header\");\n  header.appendChild(titleEl);\n  header.appendChild(statusEl);\n\n  containerEl.appendChild(header);\n  containerEl.appendChild(itemListEl);\n\n  return containerEl;\n}\n```\n\n> **Rule:** `createMyWidget` should be callable only once per page. If called again, consider returning the existing `containerEl` (idempotent factory).\n\n### 4. Export an Update Function (`updateMyWidget`)\n\nThe update function receives the new data object and performs **surgical DOM mutations** on the stored refs. It does NOT rebuild the whole tree.\n\n```typescript\nexport function updateMyWidget(data: MyWidgetData): void {\n  if (!containerEl) {\n    console.warn(\"updateMyWidget called before createMyWidget\");\n    return;\n  }\n\n  currentData = data;\n\n  \u002F\u002F Update only what changed\n  if (titleEl) titleEl.textContent = data.title;\n  if (statusEl) {\n    statusEl.textContent = data.status;\n    statusEl.dataset.status = data.status; \u002F\u002F for CSS hooks\n  }\n\n  \u002F\u002F Rebuild only dynamic list items\n  if (itemListEl) {\n    itemListEl.innerHTML = \"\"; \u002F\u002F clear previous items\n    data.items.forEach((item) => {\n      const li = document.createElement(\"li\");\n      li.textContent = item;\n      itemListEl!.appendChild(li);\n    });\n  }\n}\n```\n\n> **Optimization tip:** For large lists, compare `currentData` to `data` before clearing and rebuilding, or use a keyed reconciliation approach.\n\n### 5. Caller Usage Pattern\n\nThe caller mounts the widget once and pushes updates whenever its data changes.\n\n```typescript\nimport { createMyWidget, updateMyWidget } from \".\u002Fwidgets\u002FMyWidget\";\nimport type { MyWidgetData } from \".\u002Fwidgets\u002FMyWidget.types\";\n\n\u002F\u002F Mount once\nconst sidebar = document.getElementById(\"sidebar\")!;\nsidebar.appendChild(createMyWidget());\n\n\u002F\u002F Push updates (e.g., from a store subscription, WebSocket, timer)\nfunction onDataChange(newData: MyWidgetData) {\n  updateMyWidget(newData);\n}\n\n\u002F\u002F Example: push an initial state immediately\nonDataChange({\n  title: \"Today's Focus\",\n  items: [\"Task A\", \"Task B\"],\n  status: \"active\",\n});\n```\n\n---\n\n## Full Module Template\n\n```typescript\n\u002F\u002F widgets\u002FMyWidget.ts\n\nexport interface MyWidgetData {\n  \u002F\u002F Define all fields here\n}\n\n\u002F\u002F --- Singleton state ---\nlet containerEl: HTMLElement | null = null;\n\u002F\u002F Add more refs as needed per section of the widget\n\n\u002F\u002F --- Factory ---\nexport function createMyWidget(): HTMLElement {\n  if (containerEl) return containerEl; \u002F\u002F idempotent\n\n  containerEl = document.createElement(\"aside\");\n  \u002F\u002F ... build DOM, store refs ...\n  return containerEl;\n}\n\n\u002F\u002F --- Update ---\nexport function updateMyWidget(data: MyWidgetData): void {\n  if (!containerEl) return;\n  \u002F\u002F ... patch DOM refs with new data ...\n}\n```\n\n---\n\n## Guidelines & Best Practices\n\n| Concern | Recommendation |\n|---|---|\n| **Idempotent factory** | Return existing `containerEl` if called twice to avoid duplicate mounts. |\n| **Null guards** | Always check refs before mutating — the update fn may be called before mount in some flows. |\n| **Granular refs** | Store refs for every section that updates independently. Avoid `querySelector` in the update path. |\n| **Interface exports** | Always export the data interface so callers can type their push calls. |\n| **No internal fetching** | The module must never fetch or subscribe to external data — that is the caller's responsibility. |\n| **CSS hooks** | Use `data-*` attributes or CSS classes on refs to let stylesheets react to state changes. |\n| **Cleanup** | Optionally export a `destroyMyWidget()` that nulls all refs for SPA teardown scenarios. |\n\n---\n\n## Anti-Patterns to Avoid\n\n- ❌ **Class with constructor** — adds instantiation overhead and prevents the clean factory\u002Fupdate split.\n- ❌ **Querying the DOM in the update function** (`document.querySelector(...)`) — slow and fragile.\n- ❌ **Rebuilding the entire tree on every update** — defeats the purpose of the module-level refs.\n- ❌ **Mixing data-fetching into the widget module** — breaks the push-based contract.","# Push-Based Widget Module Pattern\n\nUse this pattern when a UI sidebar or widget component needs to be updated by its **caller** (push-based) rather than fetching data itself. Instead of a class or framework component, implement the widget as a plain module with singleton state, a factory function to create the DOM, and an update function to efficiently patch it.\n\n---\n\n## When to Use\n\n- A sidebar, panel, or widget is rendered once but updated frequently with new data.\n- The data source lives outside the component (e.g., a parent controller, event bus, or store).\n- You want lightweight partial re-renders without rebuilding the entire DOM tree.\n- You prefer a simple module interface over a class-based or framework-based component.\n\n---\n\n## Core Structure\n\n```\nwidgets\u002F\n  MyWidget.ts          # The module (singleton state + exports)\n  MyWidget.types.ts    # (Optional) Exported data interface\n```\n\n---\n\n## Step-by-Step Instructions\n\n### 1. Define the Data Interface\n\nExport a typed interface so callers know exactly what data to push.\n\n```typescript\n\u002F\u002F MyWidget.types.ts  (or inline at top of MyWidget.ts)\nexport interface MyWidgetData {\n  title: string;\n  items: string[];\n  status: \"idle\" | \"active\" | \"error\";\n  \u002F\u002F ... all fields the widget needs to render\n}\n```\n\n### 2. Declare Module-Level Singleton Refs\n\nAt module scope, keep references to the **container** and any **frequently updated child nodes**. This avoids querying the DOM on every update.\n\n```typescript\n\u002F\u002F MyWidget.ts\nimport type { MyWidgetData } from \".\u002FMyWidget.types\";\n\n\u002F\u002F Singleton DOM refs\nlet containerEl: HTMLElement | null = null;\nlet titleEl: HTMLElement | null = null;\nlet itemListEl: HTMLElement | null = null;\nlet statusEl: HTMLElement | null = null;\n\n\u002F\u002F Current state snapshot (optional — useful for diffing)\nlet currentData: MyWidgetData | null = null;\n```\n\n### 3. Export a Factory Function (`createMyWidget`)\n\nThe factory builds the full DOM tree **once**, stores refs to mutable nodes, and returns the root element to be mounted by the caller.\n\n```typescript\nexport function createMyWidget(): HTMLElement {\n  \u002F\u002F Build the container\n  containerEl = document.createElement(\"aside\");\n  containerEl.className = \"my-widget\";\n\n  \u002F\u002F Build static structure; keep refs to dynamic parts\n  titleEl = document.createElement(\"h2\");\n  titleEl.className = \"my-widget__title\";\n\n  itemListEl = document.createElement(\"ul\");\n  itemListEl.className = \"my-widget__list\";\n\n  statusEl = document.createElement(\"span\");\n  statusEl.className = \"my-widget__status\";\n\n  \u002F\u002F Compose the tree\n  const header = document.createElement(\"header\");\n  header.appendChild(titleEl);\n  header.appendChild(statusEl);\n\n  containerEl.appendChild(header);\n  containerEl.appendChild(itemListEl);\n\n  return containerEl;\n}\n```\n\n> **Rule:** `createMyWidget` should be callable only once per page. If called again, consider returning the existing `containerEl` (idempotent factory).\n\n### 4. Export an Update Function (`updateMyWidget`)\n\nThe update function receives the new data object and performs **surgical DOM mutations** on the stored refs. It does NOT rebuild the whole tree.\n\n```typescript\nexport function updateMyWidget(data: MyWidgetData): void {\n  if (!containerEl) {\n    console.warn(\"updateMyWidget called before createMyWidget\");\n    return;\n  }\n\n  currentData = data;\n\n  \u002F\u002F Update only what changed\n  if (titleEl) titleEl.textContent = data.title;\n  if (statusEl) {\n    statusEl.textContent = data.status;\n    statusEl.dataset.status = data.status; \u002F\u002F for CSS hooks\n  }\n\n  \u002F\u002F Rebuild only dynamic list items\n  if (itemListEl) {\n    itemListEl.innerHTML = \"\"; \u002F\u002F clear previous items\n    data.items.forEach((item) => {\n      const li = document.createElement(\"li\");\n      li.textContent = item;\n      itemListEl!.appendChild(li);\n    });\n  }\n}\n```\n\n> **Optimization tip:** For large lists, compare `currentData` to `data` before clearing and rebuilding, or use a keyed reconciliation approach.\n\n### 5. Caller Usage Pattern\n\nThe caller mounts the widget once and pushes updates whenever its data changes.\n\n```typescript\nimport { createMyWidget, updateMyWidget } from \".\u002Fwidgets\u002FMyWidget\";\nimport type { MyWidgetData } from \".\u002Fwidgets\u002FMyWidget.types\";\n\n\u002F\u002F Mount once\nconst sidebar = document.getElementById(\"sidebar\")!;\nsidebar.appendChild(createMyWidget());\n\n\u002F\u002F Push updates (e.g., from a store subscription, WebSocket, timer)\nfunction onDataChange(newData: MyWidgetData) {\n  updateMyWidget(newData);\n}\n\n\u002F\u002F Example: push an initial state immediately\nonDataChange({\n  title: \"Today's Focus\",\n  items: [\"Task A\", \"Task B\"],\n  status: \"active\",\n});\n```\n\n---\n\n## Full Module Template\n\n```typescript\n\u002F\u002F widgets\u002FMyWidget.ts\n\nexport interface MyWidgetData {\n  \u002F\u002F Define all fields here\n}\n\n\u002F\u002F --- Singleton state ---\nlet containerEl: HTMLElement | null = null;\n\u002F\u002F Add more refs as needed per section of the widget\n\n\u002F\u002F --- Factory ---\nexport function createMyWidget(): HTMLElement {\n  if (containerEl) return containerEl; \u002F\u002F idempotent\n\n  containerEl = document.createElement(\"aside\");\n  \u002F\u002F ... build DOM, store refs ...\n  return containerEl;\n}\n\n\u002F\u002F --- Update ---\nexport function updateMyWidget(data: MyWidgetData): void {\n  if (!containerEl) return;\n  \u002F\u002F ... patch DOM refs with new data ...\n}\n```\n\n---\n\n## Guidelines & Best Practices\n\n| Concern | Recommendation |\n|---|---|\n| **Idempotent factory** | Return existing `containerEl` if called twice to avoid duplicate mounts. |\n| **Null guards** | Always check refs before mutating — the update fn may be called before mount in some flows. |\n| **Granular refs** | Store refs for every section that updates independently. Avoid `querySelector` in the update path. |\n| **Interface exports** | Always export the data interface so callers can type their push calls. |\n| **No internal fetching** | The module must never fetch or subscribe to external data — that is the caller's responsibility. |\n| **CSS hooks** | Use `data-*` attributes or CSS classes on refs to let stylesheets react to state changes. |\n| **Cleanup** | Optionally export a `destroyMyWidget()` that nulls all refs for SPA teardown scenarios. |\n\n---\n\n## Anti-Patterns to Avoid\n\n- ❌ **Class with constructor** — adds instantiation overhead and prevents the clean factory\u002Fupdate split.\n- ❌ **Querying the DOM in the update function** (`document.querySelector(...)`) — slow and fragile.\n- ❌ **Rebuilding the entire tree on every update** — defeats the purpose of the module-level refs.\n- ❌ **Mixing data-fetching into the widget module** — breaks the push-based contract.",{"name":5,"description":7},"main","ff671ef61ed6587c49bd54c81cdc751c0b99e363","showcase\u002Fskills\u002Fpush-based-widget-module-pattern","https:\u002F\u002Fgithub.com\u002FAG064\u002FOpenSpace","https:\u002F\u002Fgithub.com\u002FAG064","AG064, E.Mi.\r\n\r\nA person who thinks all the time, yet all they have to think about is nothing. I want to improve the world and work on open source projects","2026-10-08 06:53:48",{"source":8,"skillName":5,"commands":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add AG064\u002FOpenSpace --skill push-based-widget-module-pattern",{"tool":56,"command":57},"bunx","bunx skills add AG064\u002FOpenSpace --skill push-based-widget-module-pattern",{"tool":59,"command":60},"pnpm","pnpm dlx skills add AG064\u002FOpenSpace --skill push-based-widget-module-pattern","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FAG064\u002FOpenSpace\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fpush-based-widget-module-pattern\u002FSKILL.md",true,[64],{"path":65,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":68,"sourceHtmlUrl":69},".skill_id","OTHER","其他",46,"https:\u002F\u002Fgithub.com\u002FAG064\u002FOpenSpace\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fpush-based-widget-module-pattern\u002F.skill_id",[71,94,110,119,148,162],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":38},"01M6KKMPWA0B5SCCH766F8M5EA","write-special-chars-ts-check","Workaround for write_file failures caused by special characters (apostrophes, backticks, template literals) using a Python heredoc script, plus a reliable TypeScript type-checking step that filters output to only the newly-written files to avoid being misled by pre-existing errors.","https:\u002F\u002Fgithub.com\u002FAG064\u002FOpenSpace\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fwrite-special-chars-ts-check\u002FSKILL.md",[],[78,79,80,81,82,83,25,84,85,86,87,88,89,90,91,92,93],"write special chars ts check","check","write","filters","Existing","type-checking","errors","script","output","type","files","only","template","file","python","typescript",{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":38},"01M6KKMJXVBNVEY3TRK055F4A7","write-special-chars-readback","Workaround for write_file failures caused by special characters (apostrophes, backticks, template literals) using a Python heredoc script, with mandatory post-write verification via read_file and cleanup of \u002Ftmp helper scripts.","https:\u002F\u002Fgithub.com\u002FAG064\u002FOpenSpace\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fwrite-special-chars-readback\u002FSKILL.md",[],[101,102,80,90,103,104,91,92,105,106,107,108,109,25,85,29],"readback","write special chars readback","cleanup","read","scripts","verification","via","post","helper",{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":38},"01M6KKMEGX9M9NC105J0W3Q5B9","write-special-chars-heredoc","Workaround for write_file failures caused by special characters (apostrophes, backticks, template literals) by using a Python heredoc script executed via shell.","https:\u002F\u002Fgithub.com\u002FAG064\u002FOpenSpace\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fwrite-special-chars-heredoc\u002FSKILL.md",[],[80,117,92,25,107,90,118,91,85],"write special chars heredoc","shell",{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":130,"publishedAt":38},"01M6KKM8EJ2AATVHZBNB916WT0","worldmonitor-reference","Curated architecture index of the WorldMonitor open-source dashboard. Reference for extracting patterns — vanilla TypeScript, Panel class hierarchy, service layer, CSS grid, API edge functions, refresh scheduler, and 60+ data source integrations.","https:\u002F\u002Fgithub.com\u002FAG064\u002FOpenSpace\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fworldmonitor-reference\u002FSKILL.md",[125],{"categoryNo":126,"categoryName":127,"taxonomyType":128,"taxonomyTypeDesc":129},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[131,132,133,134,93,135,136,137,138,139,25,140,141,142,143,144,145,146,35,147],"reference","worldmonitor","worldmonitor reference","dashboard","css","architecture","extracting","hierarchy","source","layer","panel","patterns","edge functions","integrations","open","api","scheduler",{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":152,"categories":153,"keywords":154,"publishedAt":38},"01M6KKM39PHYK627F19GE2B9XN","virtual-list","Implement efficient virtual scrolling for rendering large lists with DOM recycling, chunk-based rendering, and performance optimizations","https:\u002F\u002Fgithub.com\u002FAG064\u002FOpenSpace\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fvirtual-list\u002FSKILL.md",[],[155,156,157,158,25,27,29,159,160,24,161],"virtual list","list","virtual","chunk","rendering","recycling","performance",{"skillNo":163,"name":164,"nameZh":6,"description":165,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":166,"categories":167,"keywords":168,"publishedAt":38},"01M6KKKY7T2P61Y0JH54CDEJKQ","verify-directory-structure","Diagnose and resolve file access issues by first verifying the directory structure.","https:\u002F\u002Fgithub.com\u002FAG064\u002FOpenSpace\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fverify-directory-structure\u002FSKILL.md",[],[169,170,171,172,173,174,91,175,176,177],"directory","verify","structure","verify directory structure","access","first","issues","diagnose","file access"]