From svelte-5
Generates structured @component JSDoc documentation for Svelte components by reading files, analyzing props, dependencies, and interface. Auto-invokes when documenting .svelte files.
npx claudepluginhub fubits1/svelte-skills --plugin svelte-5This skill uses the workspace's default tool permissions.
Write a `<!-- @component -->` JSDoc comment block at the top of a `.svelte` file. The comment is processed by svelte2tsx into a JSDoc block on the component class — IDE hover tooltips render it directly.
Mandates invoking relevant skills via tools before any response in coding sessions. Covers access, priorities, and adaptations for Claude Code, Copilot CLI, Gemini CLI.
Share bugs, ideas, or general feedback.
Write a <!-- @component --> JSDoc comment block at the top of a .svelte file. The comment is processed by svelte2tsx into a JSDoc block on the component class — IDE hover tooltips render it directly.
@component block — structured, tab-indented, at the very top of the file (before <script>).<!--
@component
One-line summary of what this component does.
## Section heading
- Bullet point with key information
- Another bullet point
@see {@link ./RelatedFile.ts} for details on X
@example
```svelte
<MyComponent prop={value} />
```
-->
@component on its own line, description starts on the next line.@component — the filename IS the name. Write @component, not @component MyComponent.##), lists (-), code blocks (triple backtick), inline code. All render in IDE hover.@example, @see, @deprecated, @since, @author, {@link}. These are rendered by TypeScript's language service.@param, @returns, @slot, @event — they have no effect at the component level. Document props with JSDoc on their declarations inside <script>.@component is enough. Don't pad simple components with unnecessary structure..stories.svelte).ts filesAfter writing the comment, check that the file still parses by reading the first few lines to confirm the comment is well-formed HTML.