- Write concise, technical TypeScript or JavaScript code with accurate examples.
- Use functional and declarative programming patterns; avoid unnecessary classes except for state machines.
- Prefer iteration and modularization over code duplication.
- Structure files: component logic, markup, styles, helpers, types.
- Follow Svelte's official documentation for setup and configuration: https://svelte.dev/docs
- Use lowercase with hyphens for component files (e.g.,
components/auth-form.svelte). - Use PascalCase for component names in imports and usage.
- Use camelCase for variables, functions, and props.
- Implement proper component composition and reusability.
- Use Svelte's props for data passing.
- Leverage Svelte's reactive declarations for local state management.
- Ensure proper semantic HTML structure in Svelte components.
- Implement ARIA attributes where necessary.
- Ensure keyboard navigation support for interactive elements.
- Use Svelte's bind:this for managing focus programmatically.
- Embrace Svelte's simplicity and avoid over-engineering solutions.
- Use SvelteKit for full-stack applications with SSR and API routes.
- Prioritize Web Vitals (LCP, FID, CLS) for performance optimization.
- Follow Svelte's best practices for component composition and state management.
- Ensure cross-browser compatibility by testing on multiple platforms.
- Keep your Svelte and SvelteKit versions up to date.
Svelte And Sveltekit General Rules
[Applies to: **/*.svelte] Applies general Svelte and SvelteKit best practices, including file structure, component development, and state management.
Tryboy869
Updated Svelte And Sveltekit General Rules by Tryboy869 · 6dfec83
npx skillmds@latest add tryboy869/svelte-and-sveltekit-general-rules-2 File contents
---name: svelte-and-sveltekit-general-rules-2description: [Applies to: **/*.svelte] Applies general Svelte and SvelteKit best practices, including file structure, component development, and state management.---- Write concise, technical TypeScript or JavaScript code with accurate examples.- Use functional and declarative programming patterns; avoid unnecessary classes except for state machines.- Prefer iteration and modularization over code duplication.- Structure files: component logic, markup, styles, helpers, types.- Follow Svelte's official documentation for setup and configuration: https://svelte.dev/docs- Use lowercase with hyphens for component files (e.g., `components/auth-form.svelte`).- Use PascalCase for component names in imports and usage.- Use camelCase for variables, functions, and props.- Implement proper component composition and reusability.- Use Svelte's props for data passing.- Leverage Svelte's reactive declarations for local state management.- Ensure proper semantic HTML structure in Svelte components.- Implement ARIA attributes where necessary.- Ensure keyboard navigation support for interactive elements.- Use Svelte's bind:this for managing focus programmatically.- Embrace Svelte's simplicity and avoid over-engineering solutions.- Use SvelteKit for full-stack applications with SSR and API routes.- Prioritize Web Vitals (LCP, FID, CLS) for performance optimization.- Follow Svelte's best practices for component composition and state management.- Ensure cross-browser compatibility by testing on multiple platforms.- Keep your Svelte and SvelteKit versions up to date.
Tryboy869/senjutsu-coding-agent/tree/main/senjutsu/skills/svelte-and-sveltekit-general-rules commit 6dfec8323f
Frequently asked questions
Run npx skillmds@latest add tryboy869/svelte-and-sveltekit-general-rules-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.
[Applies to: **/*.svelte] Applies general Svelte and SvelteKit best practices, including file structure, component development, and state management. It is listed under Web & Frontend on SkillMD.
This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.
Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.
Tryboy869 (@tryboy869) published this skill. Their other Agent Skills are listed on their SkillMD profile.