From e1b3ec95e115ffe0832b7def5bc2aac4728ddf21 Mon Sep 17 00:00:00 2001 From: buttercat1791 Date: Sat, 24 May 2025 19:35:41 -0500 Subject: [PATCH] Update Svelte component rules --- .cursor/rules/svelte-style.mdc | 2 ++ 1 file changed, 2 insertions(+) diff --git a/.cursor/rules/svelte-style.mdc b/.cursor/rules/svelte-style.mdc index c23295e..66a97d0 100644 --- a/.cursor/rules/svelte-style.mdc +++ b/.cursor/rules/svelte-style.mdc @@ -21,6 +21,8 @@ Observe the the following style guidelines when programming Svelte components or - Avoid trying to trigger reactivity by reassigning state variables unless other options have failed. - Write components in TypeScript, and prefer strong typing for variables, props, and function signatures. - Limit component logic to rendering concerns. Extract business logic into separate TypeScript modules, and import functions and classes into Svelte components as needed. +- Use PascalCase when naming Svelte components. +- Keep component files under 500 lines, when possible. ## Component Code Organization Example