svelte-5

A set of coding guidelines for Svelte 5, a web interface framework, using its Runes system for state, computed values, side effects, properties, events, and reusable content blocks.

In plain words
What is it for?
Use it when building or reviewing Svelte 5 components, especially components that manage changing data, calculated values, side effects, callback properties, or snippets.
Why use it?
It gives the coding agent current Svelte 5 patterns so state changes, component inputs, event handling, and reusable markup are handled consistently.

Cursor rule

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add rules/renvia-code/best-cursor-rules/svelte-5
Clone the repo
git clone --depth 1 https://github.com/Renvia-code/best-cursor-rules
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 1,768 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.01768
Opus 5 $0.00000 $0.00884
Sonnet 5 $0.00000 $0.00354
Haiku 4.5 $0.00000 $0.00177

Measured 2d ago against content hash c4d0aa26d2fa, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

svelte-5 scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

rules/frameworks/svelte-5.mdc · 379 lines

How it starts

The opening of the file, as written. The whole thing — 379 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Svelte 5 Best Practices

Overview

Feature Svelte 5
Reactivity Runes ($state, $derived, $effect)
Props $props() rune
Events Callback props
Snippets Replace slots

Runes (New Reactivity System)

$state - Reactive State

<script>
  // Simple state
  let count = $state(0)
  
  // Object state (deeply reactive)
  let user = $state({
    name: 'John',
    email: '[email protected]'
  })
  
  function increment() {
    count++  // Direct mutation works
  }
  
  function updateName(name) {
    user.name = name  // Deep reactivity
  }
</script>

<button onclick={increment}>
  Count: {count}
</button>

$derived - Computed Values

<script>
  let count = $state(0)
  let doubled = $derived(count * 2)
  
  // Complex derivations
  let items = $state([1, 2, 3, 4, 5])
  let total = $derived(items.reduce((a, b) => a + b, 0))
  let evenItems = $derived(items.filter(n => n % 2 === 0))
</script>

<p>Count: {count}, Doubled: {doubled}</p>

$effect - Side Effects

<script>
  let count = $state(0)
  
  // Runs when dependencies change
  $effect(() => {
    console.log('Count changed:', count)
    
    // Cleanup function (optional)
    return () => {
      console.log('Cleaning up')
    }
  })
  
  // Pre-effect (runs before DOM updates)
  $effect.pre(() => {
    // Useful for measuring DOM before updates
  })
</script>

Props

Basic Props with $props()

<script>
  let { name, count = 0, onUpdate } = $props()
</script>

<div>
  <h2>{name}</h2>
  <p>Count: {count}</p>
  <button onclick={() => onUpdate?.(count + 1)}>
    Increment
  </button>
</div>

TypeScript Props

<script lang="ts">
  interface Props {
    name: string
    count?: number
    onUpdate?: (value: number) => void
  }
  
  let { name, count = 0, onUpdate }: Props = $props()
</script>

Spread Props

<script>
  let { class: className, ...rest } = $props()
</script>

<div class={className} {...rest}>
  Content
</div>

Read the full file on GitHub · 379 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 379 lines · 0 tokens per session scan A c4d0aa26d2fa

Subscribe to this mod's changes

svelte-5 is a cursor rule published in the GitHub repository Renvia-code/best-cursor-rules (12 stars, last pushed 9mo ago), licensed CC0-1.0. It costs nothing until one of its globs matches a file; then it loads 1,768 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.