Agent skill
vani-async-client-only
Use async components, fallbacks, and client-only islands
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/vani-async-client-only
SKILL.md
Async Components and Client-Only Islands
Instructions for async components with fallbacks and client-only rendering.
When to Use
Use this when a component needs async setup or when a section should render only on the client.
Steps
- Define a component that returns a Promise of a render function.
- Provide a
fallbackrender function for DOM mode while async work runs. - Use
clientOnly: trueto skip SSR for a component and render it on the client. - Keep explicit updates for any local state changes after load.
Arguments
- componentName - async component name (defaults to
AsyncCard) - includeFallback - whether to include a fallback (defaults to
true) - clientOnly - whether to mark the component as client-only (defaults to
false)
Examples
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.
Output
Example output:
Created: src/async-card.ts
Notes: Fallback renders in DOM mode; SSR awaits async components.
Present Results to User
Clarify when the fallback appears, how client-only rendering behaves, and list file changes.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?