svelte

svelte is a cursor rule for Cursor from ItamarZand88/awesome-agent-conventions. It costs 471 tokens per session, scanned A, a copy of svelte, MIT.

A set of coding guidelines for Svelte, a tool for building web interfaces with small reusable components. It covers component structure, reactive updates, shared state, routing, forms, and performance.

In plain words
What is it for?
Use it when creating or reviewing Svelte or SvelteKit components, stores, routes, forms, and related TypeScript or JavaScript files.
Why use it?
It gives an agent consistent patterns for organizing Svelte code and managing updates and shared data. This helps avoid unnecessarily complex components and inefficient page behavior.

Cursor rule for Cursor

Written for Cursor: a Cursor rule (.mdc).

Good fit Use it when creating or reviewing Svelte or SvelteKit components, stores, routes, forms, and related TypeScript or JavaScript files.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/itamarzand88/awesome-agent-conventions/svelte
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.

Clone the repo
git clone --depth 1 https://github.com/ItamarZand88/awesome-agent-conventions

Made for: Cursor.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for svelte

README.md
[![agentmods](https://agentmods.dev/badge/rules/itamarzand88/awesome-agent-conventions/svelte.svg)](https://agentmods.dev/rules/itamarzand88/awesome-agent-conventions/svelte)
Your own site
<a href="https://agentmods.dev/rules/itamarzand88/awesome-agent-conventions/svelte"><img src="https://agentmods.dev/badge/rules/itamarzand88/awesome-agent-conventions/svelte.svg" alt="Measured on agentmods" height="20"></a>
Per session 471 This file is loaded in full into every session.
When invoked 471 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 91% copy Near-identical to another mod 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.1 $0.00471 $0.00471
Opus 5 $0.00235 $0.00235
Sonnet 5 $0.00094 $0.00094
Haiku 4.5 $0.00047 $0.00047

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

Security

Grade A, and why

svelte 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 8d 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.

Origin

This is a copy

91% identical to svelte — 1 line differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

conventions/agent-rules/examples/awesome-cursorrules-svelte/svelte.mdc · 88 lines

How it starts

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


description: "Svelte best practices and patterns for modern web applications" globs: /*.svelte, src//.ts, src/**/.js alwaysApply: false

Svelte Best Practices

Component Structure

  • Keep components small and focused
  • Use proper TypeScript integration
  • Implement proper props typing
  • Use proper event dispatching
  • Keep markup clean and readable
  • Use proper slot implementation

Reactivity

  • Use proper reactive declarations
  • Implement proper stores
  • Use proper reactive statements
  • Handle derived values properly
  • Use proper lifecycle functions
  • Implement proper bindings

State Management

  • Use proper Svelte stores
  • Keep stores modular
  • Use proper derived stores
  • Implement proper actions
  • Handle async state properly
  • Use proper store subscriptions

Performance

  • Use proper component lazy loading
  • Implement proper transitions
  • Use proper animations
  • Avoid unnecessary reactivity
  • Use proper event forwarding
  • Implement proper key blocks

Routing

  • Use SvelteKit for routing
  • Implement proper layouts
  • Use proper route parameters
  • Handle loading states properly
  • Implement proper error pages
  • Use proper navigation methods

Forms

  • Use proper form bindings
  • Implement proper validation
  • Handle form submission properly
  • Show proper loading states
  • Use proper error handling
  • Implement proper form reset

TypeScript Integration

  • Use proper component types
  • Implement proper prop types
  • Use proper event types
  • Handle proper type inference
  • Use proper store types
  • Implement proper action types

Testing

  • Write proper unit tests
  • Implement proper component tests
  • Use proper testing libraries
  • Test stores properly
  • Implement proper mocking
  • Test async operations

Best Practices

  • Follow Svelte style guide
  • Use proper naming conventions
  • Keep components organized
  • Implement proper error handling
  • Use proper event handling
  • Document complex logic

Read the full file on GitHub · 88 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. 8d ago First seen · 88 lines · 471 tokens per session scan A e913559041aa

Subscribe to this mod's changes

svelte is a cursor rule published in the GitHub repository ItamarZand88/awesome-agent-conventions (31 stars, last pushed 1mo ago), licensed MIT. It adds 471 tokens to every session, about $0.0024 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to svelte, differing in 1 line, and is treated as a copy.