with one click
vani-async-client-only
Use async components, fallbacks, and client-only islands
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Menu
Use async components, fallbacks, and client-only islands
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | vani-async-client-only |
| description | Use async components, fallbacks, and client-only islands |
Instructions for async components with fallbacks and client-only rendering.
Use this when a component needs async setup or when a section should render only on the client.
fallback render function for DOM mode while async work runs.clientOnly: true to skip SSR for a component and render it on the client.AsyncCard)true)false)Example 1 usage pattern:
Render an async card with a loading fallback, then resolve to content.
Example 2 usage pattern:
Render a client-only widget inside an SSR page using clientOnly: true.
Example output:
Created: src/async-card.ts
Notes: Fallback renders in DOM mode; SSR awaits async components.
Clarify when the fallback appears, how client-only rendering behaves, and list file changes.
Create a tiny global store with explicit subscriptions
Updates Vani SPA app UI in src/spa-app, especially the landing page/homepage and landing examples. Use when the user mentions Vani SPA app, src/spa-app, landing page/homepage, or landing examples.
Mount Vani components inside existing apps or DOM islands
Build scalable lists with keyed rows and per-item updates
Schedule explicit updates with microtasks and transitions
Create a minimal Vani SPA root with explicit updates