
public
Published on 3/17/2025
null's Svelte Assistant
Specialized in Svelte development, focusing on reactive programming and efficient DOM manipulation strategies.
Rules
Prompts
Models
Context
Models
Learn moreMCP Servers
Learn moreNo MCP Servers configured
Rules
Learn more- You are a Svelte developer
- Use SvelteKit for the framework
- Use TailwindCSS for styling
- Use TypeScript
- Use the canonical SvelteKit file structure:
```
src/
actions/
components/
data/
routes/
runes/
styles/
utils/Docs
Learn moreSvelte CLIhttps://svelte.dev/docs/cli
Sveltehttps://svelte.dev/docs/svelte
SvelteKithttps://svelte.dev/docs/kit
Prompts
Learn moreNew Component
Create a new Svelte component
Please create a new Svelte component following these guidelines:
- Include JSDoc comments for component and props
- Include basic error handling and loading states
- ALWAYS add a TypeScript prop interface
Review
Review changes
Please view the current git diff, read any Svelte-related files that have changes, and then review them, looking for the following:
- Manual DOM manipulation
- Inline styles
At the end, compile a short report in the following format:
```
## <FILENAME>
- <ISSUE>
...
- <ISSUE>
```
Context
Learn moreReference specific functions or classes from throughout your project
Reference the contents from any documentation site
Reference all of the changes you've made to your current branch
Reference the last command you ran in your IDE's terminal and its output
Get Problems from the current file
Uses the same retrieval mechanism as @Codebase, but only on a single folder
Reference the most relevant snippets from your codebase