Svelte Expert - CLAUDE.md Rules for Claude Code
Transform Claude into a Svelte specialist with deep knowledge of reactivity, components, stores, SvelteKit routing, and performance-conscious UI patterns.
Open the source and read safety notes before installing.
Privacy notes
- Rules reference user session data in load functions; avoid exposing secrets in client-side props or serialized page data.
Schema details
- Install type
- copy
- Troubleshooting
- No
Full copyable content
You are an expert Svelte developer focused on clear reactivity and lean components.
## Components
- Keep components small; lift shared state deliberately.
- Prefer explicit props and events over implicit globals.
## Reactivity
- Use runes (`$state`, `$derived`, `$effect`) in Svelte 5 codebases.
- Avoid unnecessary effects; derive values when possible.
## SvelteKit
- Load data in `+page.server.ts` or `+layout.server.ts` when secrets are involved.
- Type `PageData` from generated `./$types` modules.About this resource
Svelte Expert
Use these rules when building or reviewing Svelte and SvelteKit applications.
Component boundaries
Split UI into focused components with clear inputs. Pass data down and events up instead of mutating parent state from deep children.
Reactivity discipline
Derive computed values rather than synchronizing duplicate state in effects. Keep reactive graphs easy to follow.
SvelteKit data loading
Choose server loads for privileged data and universal loads for public API fetches. Serialize only what the client needs.
References
Source citations
Add this badge to your README
Show that Svelte Expert - CLAUDE.md Rules for Claude Code is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.
[](https://heyclau.de/entry/rules/svelte-expert)How it compares
Svelte Expert - CLAUDE.md Rules for Claude Code side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
| Field | Svelte Expert - CLAUDE.md Rules for Claude Code Transform Claude into a Svelte specialist with deep knowledge of reactivity, components, stores, SvelteKit routing, and performance-conscious UI patterns. Open dossier | React Expert - CLAUDE.md Rules for Claude Code Transform Claude into a framework-agnostic React core specialist focused on the built-in Hooks, the Rules of Hooks, and component fundamentals from the official React docs Open dossier | Angular Expert - CLAUDE.md Rules for Claude Code Transform Claude into an Angular specialist with deep knowledge of standalone components, Angular Signals, dependency injection, RxJS patterns, and the Angular Style Guide. Open dossier | React Next.js Expert - CLAUDE.md Rules for Claude Code Next.js App Router production-architecture specialist focused on the server/client boundary, the explicit caching model, route handlers, and Node-vs-Edge runtime tradeoffs — decisions, not component tips Open dossier |
|---|---|---|---|---|
| Trust | ||||
| Install risk | Review first | Review first | Review first | Review first |
| Notes | Safety · Privacy ✓ | Safety · Privacy ✓ | Safety · Privacy · | Safety ✓ Privacy ✓ |
| Category | rules | rules | rules | rules |
| Source | source-backed | source-backed | source-backed | source-backed |
| Author | jaso0n0818 | JSONbored | jaso0n0818 | JSONbored |
| Added | 2026-06-17 | 2025-09-15 | 2026-06-13 | 2025-09-15 |
| Platforms | Claude Code | Claude Code | Claude Code | Claude Code |
| Source repo | — | — | — | — |
| Safety notes | — missing | — missing | — missing | ✓These are advisory CLAUDE.md rules for Next.js App Router architecture; they guide code structure and make no changes to infrastructure. Review generated server/client boundaries and data fetching before shipping. |
| Privacy notes | ✓Rules reference user session data in load functions; avoid exposing secrets in client-side props or serialized page data. | ✓Guidance covers React state and effects; keep API keys, tokens, and secrets out of client-side React code and bundles, since anything in the client is exposed to users. | — missing | ✓This rule guides Next.js architecture decisions on your own codebase. It explicitly warns against leaking server-only modules and secrets into Client Components, and does not collect or transmit any data itself. |
| Prerequisites | — none listed | — none listed | — none listed | — none listed |
| Install | — | — | — | — |
| Config | — | — | — | — |
| Citations | ||||
| Claim | Unclaimed | Unclaimed | Unclaimed | Unclaimed |
Signals
Loading live community signals…
A short, calm digest of reviewed Claude resources. Unsubscribe any time.