Cursor rule Cursor
Cursor rule "frontend-development" from rilldata/rill, covering frontend development guidelines, technology stack, web applications, component architecture and shared components (web-common).
16 tagged sveltekit, measured the same way as everything else here.
Browse within: svelte 10typescript 7
Cursor rule Cursor
Cursor rule "frontend-development" from rilldata/rill, covering frontend development guidelines, technology stack, web applications, component architecture and shared components (web-common).
Cursor rule Cursor
Naming conventions for files and components in the Rill web frontend codebases.
Cursor rule Cursor
Svelte best practices and patterns for modern web applications.
Cursor rule Cursor
ALWAYS follow this rule.
Cursor rule Cursor
When handling errors, use the neverthrow library to handle errors.
Cursor rule Cursor
When writing code for tailwind css make sure to do the following.
Cursor rule Cursor
You are an expert in Svelte 5, SvelteKit, TypeScript, and modern web development.
Cursor rule Cursor
Comprehensive Testing Best Practices for Svelte 5 + vitest-browser-svelte.
Cursor rule Cursor
Comprehensive Testing Best Practices for Svelte 5 + vitest-browser-svelte.
Cursor rule Cursor
Classic engineering patterns applied to SvelteKit + TypeScript + Supabase projects. Use when structuring a SvelteKit app, organizing data access, abstracting third-party services, managing shared state, improving testability, or when the user describes a problem that a Factory, Repository, Service Layer, Singleton…
Cursor rule Cursor
You are an expert SvelteKit engineer. Follow these rules ALWAYS when generating or editing code.
ofershap/sveltekit-best-practices
Cursor rule
SvelteKit Best Practices - enforces current best practices when working with SvelteKit / Svelte 5 code.
Cursor rule Cursor
Open Electricity project rules.
Cursor rule Cursor
Read and follow AGENTS.md before making changes. It is the canonical, model-neutral source for project commands, Svelte 5 conventions, testing, API design, and git safety. Task-specific procedures are in docs/agent-workflows/.