Svelte Wrap

Problem Solved

Svelte components often get wrapped repeatedly in application code: outer props, event bindings, style conventions, and script injection can scatter across files. Svelte Wrap targets this Svelte Web + JavaScript wrapping scenario by consolidating repetitive wrapper logic into a reusable form. The listed tags include wrap, github, and automation, suggesting it may also organize Svelte wrapper output around GitHub repositories or automation workflows.

How It Works

From the available description, the core is not replacing the Svelte framework but adding a wrap layer around it:
- Takes a Svelte component or JavaScript fragment as input.
- Generates or organizes wrapper code around props, events, scripts, and component boundaries.
- Uses automation signals to connect wrapper steps to scripted flows or repository workflows.

Because the SKILL.md provides only a short description, exact CLI commands, template fields, and output directories are not documented.

Boundaries

This fits projects that already have Svelte components and need a consistent wrapping convention. It is not a full scaffold, state management solution, or backend integration tool. If used with GitHub automation, verify branch targets, file naming, and deployment paths. Before relying on generated wrappers, check that event names and prop types from the original component are preserved.