public
Published on 2/26/2025
Svelte Assistant
Rules
Prompts
Models
Context
Models
Learn more
MCP 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 morePrompts
Learn moreReview
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>
```
New 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
Context
Learn moreReference all of the changes you've made to your current branch
Reference the most relevant snippets from your codebase
Reference the markdown converted contents of a given URL
Uses the same retrieval mechanism as @Codebase, but only on a single folder
Reference the last command you ran in your IDE's terminal and its output
Reference specific functions or classes from throughout your project
Reference any file in your current workspace