public
Published on 3/3/2025
Colin's Svelte Assistant
Specialized in Svelte development, focusing on reactive programming and efficient DOM manipulation strategies.
Rules
Prompts
Models
Context
Models
Learn more
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 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 more@code
Reference specific functions or classes from throughout your project
@docs
Reference the contents from any documentation site
@diff
Reference all of the changes you've made to your current branch
@terminal
Reference the last command you ran in your IDE's terminal and its output
@problems
Get Problems from the current file
@folder
Uses the same retrieval mechanism as @Codebase, but only on a single folder
@codebase
Reference the most relevant snippets from your codebase
Data
Learn moreNo Data configured
MCP Servers
Learn moreNo MCP Servers configured