← Products

Dev
⚙ Needs: a Tauri v2 project needing a startup/splashscreen ex…

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

At a glance
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.

Version:

@
Created by: @full-stack-skills
⌁

Install

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://github.com/full-stack-skills/tauri-skills/blob/main/skills/tauri-app-splashscreen/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-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.

?

Questions

How do I install a build?

Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build 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 build before installing it.