Use when adding an interactive UI component that requires client-side JavaScript - creates a framework island with hydration strategy.
84%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Create an interactive island component following docs/ARCHITECTURE.md section 5.2.
Island: $ARGUMENTS
Read docs/ARCHITECTURE.md section 5.2.
Confirm interactivity is required - if the component is purely presentational, use /dev-create-component instead.
Determine the framework (based on project preference):
src/islands/IslandName.tsxsrc/islands/IslandName.vuesrc/islands/IslandName.svelteChoose hydration strategy:
client:load - immediately visible + interactive (above the fold)client:idle - not urgent, hydrate when browser is idleclient:visible - below the fold, hydrate when scrolled into viewclient:media="(max-width: 768px)" - only on specific viewportsclient:only="react" - skip SSR entirely (browser-API-dependent)Create the island with typed props (React example):
interface Props {
// all props must be serializable (no functions, no class instances)
}
export default function IslandName({ prop1, prop2 }: Props) {
// minimal client-side state and interactivity
return (
<div>
{/* interactive UI */}
</div>
)
}---
import IslandName from '../islands/IslandName'
---
<IslandName client:idle prop1="value" prop2={42} />Checklist:
Validate: npx astro check && npx astro build
fernandezbaptiste/specialist-agent
cd716d9
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.