Tauri app store — key-value persistence with Store vs LazyStore

Prerequisites: a Tauri v2 project needing lightweight persistent storage — the skill is a workflow guide the agent follows, not software Install "Tauri app store — key-value persistence with Store vs LazyStore" for me. It gives my agent @full-stack-skills' store guidance: decide between Store and LazyStore based on load timing, define the storage file location and schema, restrict access via capabilities and scope, and validate the persistence lifecycle and error handling — producing store-selection guidance and a settings persistence plan, with links to the official v2.tauri.app store docs. Apache-2.0 licensed. Repository: https://github.com/full-stack-skills/tauri-skills/blob/main/skills/tauri-app-store/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "tauri-app-store". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. nothing — it's a methodology; ask the agent about Store vs LazyStore or settings persistence for my Tauri project). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.