[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79SW2N6QETQBRSSBS88KXEF":3,"skill-same:01M79SW2N6QETQBRSSBS88KXEF":53},{"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":32,"commitSha":33,"skillDirectory":34,"forksCount":14,"repositoryHtmlUrl":35,"repositoryHomepageUrl":6,"ownerHtmlUrl":36,"ownerBlogUrl":6,"ownerDescription":37,"updatedAt":38,"install":39,"resources":52},"01M79SW2N6QETQBRSSBS88KXEF","desktop-offline-storage-architect",null,"Architect-level local data design for desktop apps — embedded database choice, file layout and app-data conventions, backup and corruption recovery, large local datasets, sync with a server when one exists, and the long-session durability a desktop app is expected to provide. Use when the app owns data on the user's machine.","SriAkhilSJ\u002FPulseAIRepo","SriAkhilSJ","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F206201543?v=4","01M79RWFD1Q09B89SXTTKKJY6Z","Sri Akhil SJ","01M79RWFE26NPG0BZ1FRNX376H",0,"MIT","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fdesktop-architect\u002Fdata-architect\u002Fdesktop-offline-storage-architect\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: desktop-offline-storage-architect\ndescription: Architect-level local data design for desktop apps — embedded database choice, file layout and app-data conventions, backup and corruption recovery, large local datasets, sync with a server when one exists, and the long-session durability a desktop app is expected to provide. Use when the app owns data on the user's machine.\nlicense: MIT\ncompatibility: SQLite, DuckDB, LevelDB, IndexedDB, LMDB, filesystem\nmetadata:\n  crusor-domain: desktop-architect\n  crusor-path: desktop-architect\u002Fdata-architect\u002Fdesktop-offline-storage-architect\n  crusor-origin: original\n  crusor-sources: \"sqlite.org\u002Fwal.html; sqlite.org\u002Flang_vacuum.html; developer.apple.com\u002Fdocumentation\u002Ffoundation\u002Ffile_system; learn.microsoft.com\u002Fwindows\u002Fapps\u002Fdesign\u002Fapp-settings\"\n  crusor-triggers: \"local database, sqlite, app data, local storage, offline data, file corruption, backup, data directory, embedded database, local cache, loses data, data loss, crash recovery\"\n  crusor-verified-on: \"2026-10-30\"\n---\n\n# Desktop Offline Storage Architect\n\nA desktop app owns **durable user data**. The bar is not \"it saves\" — it is \"it\nsurvives a power cut, a full disk, and a corrupted file\".\n\n## When to use\n\n- The app stores user documents, history, or state locally.\n- Choosing between SQLite, a document store, and plain files.\n- Data grows to GBs, or users report lost\u002Fcorrupt data.\n\n## When NOT to use\n\n- Server-authoritative data with only a small preference cache.\n- The issue is the remote schema → `website-architect\u002Fdatabase-*`.\n\n## Decision 1 — Store choice\n\n| Store | Use for |\n|---|---|\n| SQLite (WAL) | relational, queries, transactions, most apps |\n| DuckDB | analytical, columnar, local reporting |\n| key-value (LevelDB\u002FLMDB) | huge KV sets, caches |\n| JSON\u002FJSONL files | settings, small portable configs |\n| files on disk | documents, media, exports |\n\n- SQLite is the default answer; it is a bounded, transactional, well-understood\n  engine.\n- Do not store a database in a network\u002Fsynced folder (Dropbox\u002FOneDrive) — file\n  locking is unreliable there. Sync via the app instead.\n\n## Decision 2 — Layout and conventions\n\n```\napp data dir\u002F            (OS-correct per platform)\n  db\u002Fapp.db              transactional state\n  files\u002F                 user documents (content-addressed or uuid)\n  cache\u002F                 disposable, deletable\n  logs\u002F                  rotating, bounded\n  backups\u002F               last N snapshots\n```\n\n- Cache is always safe to delete; never store anything irreplaceable there.\n- Per-user vs per-machine scope is a decision; roaming profiles change the answer.\n- Paths derived from the OS API, never hardcoded.\n- File names sanitised; user input never becomes a path component.\n\n## Decision 3 — Durability\n\n- WAL mode with a sensible checkpoint interval; `synchronous=NORMAL` is usually\n  the right trade, `FULL` for critical writes.\n- Transactions wrap multi-step writes; a crash mid-sequence leaves no partial\n  state.\n- Write-then-rename for atomic file replacement.\n- Handle a full disk explicitly: detect, surface, and do not corrupt existing data.\n- Flush before reporting success to the UI.\n\n## Decision 4 — Corruption and backup\n\n- Assume the file can be corrupt: run `PRAGMA integrity_check` on startup after an\n  unclean shutdown.\n- Keep rotating snapshots (on version change, daily, before migrations).\n- Recovery path: attempt open → integrity check → restore from latest good backup\n  → move the corrupt file aside for support (never delete it).\n- Export\u002Fimport a portable format so users are never trapped.\n- Log the recovery event and tell the user what happened.\n\n## Decision 5 — Scale\n\n- Index for the queries the UI actually runs; a full scan on 2 GB is a bug.\n- Paginate reads; never load a whole table into memory for a list view.\n- Vacuum\u002Fcompact on a schedule or after large deletes; disk grows otherwise.\n- Blobs: filesystem with references in the DB, unless you need transactional\n  blobs and the size is small.\n- Measure: open time and query time on a production-size dataset.\n\n## Decision 6 — Sync with a server\n\n- The local DB is authoritative for the session; the server is authoritative for\n  shared state — decide per entity.\n- Sync via the app's API with ids and versions; never by syncing the database file.\n- Conflicts resolved per field; deletions as tombstones.\n- Offline queue survives restarts and is idempotent on replay.\n\n## Failure modes at scale\n\n- Database inside a Dropbox folder; two machines, one corrupted file.\n- No backup before migration; a failed upgrade destroys history.\n- Cache directory used for user documents, purged by a cleaner.\n- Full disk during save; the app truncates the file and reports success.\n- Startup integrity check absent; every user sees a crash loop after a power cut.\n\n## Verification receipts\n\n1. Store choice and layout documented with the OS-correct paths.\n2. Crash test: kill mid-write, data intact, WAL recovers.\n3. Corruption drill: truncate the DB file, recovery path restores from backup.\n4. Full-disk test: write fails cleanly, existing data untouched.\n5. Open and query timings on a production-size dataset.\n","# Desktop Offline Storage Architect\n\nA desktop app owns **durable user data**. The bar is not \"it saves\" — it is \"it\nsurvives a power cut, a full disk, and a corrupted file\".\n\n## When to use\n\n- The app stores user documents, history, or state locally.\n- Choosing between SQLite, a document store, and plain files.\n- Data grows to GBs, or users report lost\u002Fcorrupt data.\n\n## When NOT to use\n\n- Server-authoritative data with only a small preference cache.\n- The issue is the remote schema → `website-architect\u002Fdatabase-*`.\n\n## Decision 1 — Store choice\n\n| Store | Use for |\n|---|---|\n| SQLite (WAL) | relational, queries, transactions, most apps |\n| DuckDB | analytical, columnar, local reporting |\n| key-value (LevelDB\u002FLMDB) | huge KV sets, caches |\n| JSON\u002FJSONL files | settings, small portable configs |\n| files on disk | documents, media, exports |\n\n- SQLite is the default answer; it is a bounded, transactional, well-understood\n  engine.\n- Do not store a database in a network\u002Fsynced folder (Dropbox\u002FOneDrive) — file\n  locking is unreliable there. Sync via the app instead.\n\n## Decision 2 — Layout and conventions\n\n```\napp data dir\u002F            (OS-correct per platform)\n  db\u002Fapp.db              transactional state\n  files\u002F                 user documents (content-addressed or uuid)\n  cache\u002F                 disposable, deletable\n  logs\u002F                  rotating, bounded\n  backups\u002F               last N snapshots\n```\n\n- Cache is always safe to delete; never store anything irreplaceable there.\n- Per-user vs per-machine scope is a decision; roaming profiles change the answer.\n- Paths derived from the OS API, never hardcoded.\n- File names sanitised; user input never becomes a path component.\n\n## Decision 3 — Durability\n\n- WAL mode with a sensible checkpoint interval; `synchronous=NORMAL` is usually\n  the right trade, `FULL` for critical writes.\n- Transactions wrap multi-step writes; a crash mid-sequence leaves no partial\n  state.\n- Write-then-rename for atomic file replacement.\n- Handle a full disk explicitly: detect, surface, and do not corrupt existing data.\n- Flush before reporting success to the UI.\n\n## Decision 4 — Corruption and backup\n\n- Assume the file can be corrupt: run `PRAGMA integrity_check` on startup after an\n  unclean shutdown.\n- Keep rotating snapshots (on version change, daily, before migrations).\n- Recovery path: attempt open → integrity check → restore from latest good backup\n  → move the corrupt file aside for support (never delete it).\n- Export\u002Fimport a portable format so users are never trapped.\n- Log the recovery event and tell the user what happened.\n\n## Decision 5 — Scale\n\n- Index for the queries the UI actually runs; a full scan on 2 GB is a bug.\n- Paginate reads; never load a whole table into memory for a list view.\n- Vacuum\u002Fcompact on a schedule or after large deletes; disk grows otherwise.\n- Blobs: filesystem with references in the DB, unless you need transactional\n  blobs and the size is small.\n- Measure: open time and query time on a production-size dataset.\n\n## Decision 6 — Sync with a server\n\n- The local DB is authoritative for the session; the server is authoritative for\n  shared state — decide per entity.\n- Sync via the app's API with ids and versions; never by syncing the database file.\n- Conflicts resolved per field; deletions as tombstones.\n- Offline queue survives restarts and is idempotent on replay.\n\n## Failure modes at scale\n\n- Database inside a Dropbox folder; two machines, one corrupted file.\n- No backup before migration; a failed upgrade destroys history.\n- Cache directory used for user documents, purged by a cleaner.\n- Full disk during save; the app truncates the file and reports success.\n- Startup integrity check absent; every user sees a crash loop after a power cut.\n\n## Verification receipts\n\n1. Store choice and layout documented with the OS-correct paths.\n2. Crash test: kill mid-write, data intact, WAL recovers.\n3. Corruption drill: truncate the DB file, recovery path restores from backup.\n4. Full-disk test: write fails cleanly, existing data untouched.\n5. Open and query timings on a production-size dataset.\n",{"name":5,"license":15,"metadata":24,"description":7,"compatibility":31},{"crusor-path":25,"crusor-domain":26,"crusor-origin":27,"crusor-sources":28,"crusor-triggers":29,"crusor-verified-on":30},"desktop-architect\u002Fdata-architect\u002Fdesktop-offline-storage-architect","desktop-architect","original","sqlite.org\u002Fwal.html; sqlite.org\u002Flang_vacuum.html; developer.apple.com\u002Fdocumentation\u002Ffoundation\u002Ffile_system; learn.microsoft.com\u002Fwindows\u002Fapps\u002Fdesign\u002Fapp-settings","local database, sqlite, app data, local storage, offline data, file corruption, backup, data directory, embedded database, local cache, loses data, data loss, crash recovery","2026-10-30","SQLite, DuckDB, LevelDB, IndexedDB, LMDB, filesystem","main","8fa4e240be65b98472c9b2d3a505ade2aea1a5c6","skills\u002Fdesktop-architect\u002Fdata-architect\u002Fdesktop-offline-storage-architect","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ","Studying in CMR institute of Technology\r\n2024 - 2028","2026-11-13 21:02:23",{"source":8,"skillName":5,"commands":40,"prompt":50,"zipAvailable":51},[41,44,47],{"tool":42,"command":43},"npx","npx skills add SriAkhilSJ\u002FPulseAIRepo --skill desktop-offline-storage-architect",{"tool":45,"command":46},"bunx","bunx skills add SriAkhilSJ\u002FPulseAIRepo --skill desktop-offline-storage-architect",{"tool":48,"command":49},"pnpm","pnpm dlx skills add SriAkhilSJ\u002FPulseAIRepo --skill desktop-offline-storage-architect","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fdesktop-architect\u002Fdata-architect\u002Fdesktop-offline-storage-architect\u002FSKILL.md",true,[],[54,61,68,75,82,89],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M79TTAJNACCNXCEN3649CMMD","interaction-patterns-architect","Architect-level interaction design in code — choosing established patterns over invented ones, feedback and latency behaviour, destructive-action safeguards, navigation and overlay conventions, and the state model behind every interactive surface. Use when a screen has to behave, not just look.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002Finteraction-patterns-architect\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M79TT2ESKB1TKZBYY9KYJHV9","design-system-ops-architect","Architect-level operation of a design system in code — token pipelines and versioning, component API and variant policy, the catalogue as the contract, adoption metrics, and the governance that stops a system from forking into three. Use when a component library must survive several teams.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002Fdesign-system-ops-architect\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M79TSV0PWGNK3PRX9P4JDR9N","design-handoff-architect","Architect-level design handoff — what must be specified before implementation starts, tokens over raw values, responsive and content-limit contracts, state matrices, and the review loop that catches drift between design and code. Use when a design is about to become code.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002Fdesign-handoff-architect\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M79TSJS9BFXNP696FMJ9GKDA","content-microcopy-architect","Architect-level UI content — where strings live, voice and terminology consistency, error and empty-state copy as part of the interface, translation-ready authoring, and the content model a product needs before it multiplies screens. Use when the words in the interface matter as much as the pixels.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002Fcontent-microcopy-architect\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M79TSCNBST3N1M68V1KPH9HQ","ui-ux-implementation-architect","Architect-level direction for turning a design into working UI — the handoff contract, component ownership versus screen-level layout, interaction and state conventions, design QA gates, and the review habits that keep an implementation faithful without frozen pixels. Use before any specific UI implementation skill.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M79TS4N6A4D2QQ433VXS5D0R","test-strategy-architect","Architect-level test strategy — allocating assertions across unit, integration, contract and end-to-end layers, designing for testability through dependency boundaries, fixture and data strategy, and the flake and coverage policies that keep a suite trustworthy. Use when defining how a codebase is tested.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Ftesting-and-deployment-architect\u002Ftest-strategy-architect\u002FSKILL.md",[],[]]