Tauri app splashscreen — startup screen setup and lifecycle control
Guidance for the Tauri v2 splashscreen — asset and window configuration, hide timing vs main window, slow-load handling and error fallback, avoiding white screens at startup
- What
- Guidance for the Tauri v2 splashscreen — asset and window configuration, hide timing vs main window, slow-load handling and error fallback, avoiding white screens at startup
- Cost
- Free
- Needs
- a Tauri v2 project needing a startup/splashscreen experience — the skill is a workflow guide the agent follows, not software
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @full-stack-skills' tauri-app-splashscreen skill: guidance for the Tauri v2 splashscreen — configuring splashscreen assets and window settings, deciding when to hide the splashscreen and show the main window, handling slow frontend loads and error fallback, and validating cross-platform startup behavior, with links to the official v2.tauri.app splashscreen docs. It produces a splashscreen lifecycle plan and a startup timing checklist, with a declared boundary (splashscreen configuration and lifecycle only — avoiding white screens and startup timing). Honest caveats: guidance sections are bilingual English/Chinese and distinct per skill; the gotchas/workflow tail is a shared template across the tauri-app-* series. Apache-2.0 licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Quick answer
Tauri app splashscreen is a free skill from @full-stack-skills for the Tauri v2 splashscreen. It configures splashscreen assets and window settings, decides when to hide the splashscreen and show the window, handles slow loads and error fallback, and validates startup behavior, producing a lifecycle plan and a timing checklist. Its boundary is splashscreen configuration and lifecycle only, avoiding white screens.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 77b57c4Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: a Tauri v2 project needing a startup/splashscreen experience — the skill is a workflow guide the agent follows, not software Install "Tauri app splashscreen — startup screen setup and lifecycle control" for me. It gives my agent @full-stack-skills' splashscreen guidance: configure splashscreen assets and window settings, decide when to hide the splashscreen and show the main window, handle slow frontend loads and error fallback, and validate cross-platform startup behavior — producing a splashscreen lifecycle plan and a startup timing checklist, with links to the official v2.tauri.app splashscreen docs. Apache-2.0 licensed. Repository: https://raw.githubusercontent.com/full-stack-skills/tauri-skills/77b57c4913873a0f8cab7db45116038dc18a27f0/skills/tauri-app-splashscreen/SKILL.md Pinned version: install the code at commit 77b57c4913873a0f8cab7db45116038dc18a27f0 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder 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-splashscreen". 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 splashscreen timing or white-screen avoidance 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.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 77b57c4 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.