svelte

Coding rules for Svelte, a framework for building web interfaces, covering component exports, hooks, properties, and example stories.

In plain words
What is it for?
Use them when exporting Svelte components, writing hooks, handling bindable values, or creating component stories and examples.
Why use it?
They keep the Svelte package consistent with its React counterpart and make components and examples follow the project’s expected structure.

Cursor rule for Cursor

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/chakra-ui/ark/svelte
Clone the repo
git clone --depth 1 https://github.com/chakra-ui/ark

Made for: Cursor.

Per session 255 This file is loaded in full into every session.
When invoked 255 The same file — it is already loaded in full.
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.00255 $0.00255
Opus 5 $0.00128 $0.00128
Sonnet 5 $0.00051 $0.00051
Haiku 4.5 $0.00026 $0.00026

Measured yesterday against content hash c2ed3f5a8282, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 yesterday.

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.

.cursor/rules/svelte.mdc · 39 lines

What it actually says

  • Make sure to export the *BaseProps
  • children?: Snippet already exists in HTMLArkProps<X> so no need to define it
  • Every use* hook must return and Accessor<T>
  • For *-root.svelte files where value or open is a valid prop, make sure you setup the $bindable() for it.
  • For *-context.svelte files, prefer to use render not children prop

Exporting Files

  • Always export pattern is export { default as Component }
  • Check the exports against the react package and make sure they're the same

Creating Stories

  • When creating stories, keep the format simple
  • Imports must have a Example suffix
  • All imports in examples must use @ark-ui/svelte/<component>
import BasicExample from "./examples/basic.svelte"

const meta: Meta = {
  title: 'Components / <component>',
}

export default meta

export const Basic = {
  render: () => ({
    Component: BasicExample,
  }),
}
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. yesterday First seen · 39 lines · 255 tokens per session scan A c2ed3f5a8282

Subscribe to this mod's changes

svelte is a cursor rule published in the GitHub repository chakra-ui/ark (5,367 stars, last pushed 3d ago), licensed MIT. It adds 255 tokens to every session, about $0.0013 per session on Opus 5. 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.