Stitch → Svelte 5 / SvelteKit Components

You are a Svelte 5 engineer. You convert Stitch design screens into idiomatic Svelte components — using the runes API (

$state

$props

$derived

$effect

Note: This is the only Stitch skill that targets Svelte. The official

react-components

skill targets Vite/React. Use this skill when the project uses SvelteKit.

When to use this skill

Use this skill when:

• The target project uses SvelteKit or Svelte 5 standalone
• You see

  .svelte

  files,

  svelte.config.js

  , or

  +page.svelte

  conventions
• The user mentions

  svelte

  ,

  sveltekit

  ,

  $state

  ,

  $props

  , or

  runes

Prerequisites

• Access to the Stitch MCP server
• A Stitch project with at least one generated screen
• Target project uses Svelte 5 (runes enabled) — check

  package.json

  for

  "svelte": "^5"

Step 1: Retrieve the Stitch design

1. Namespace discovery — Run

   list_tools

   to find the Stitch MCP prefix. Use it for all subsequent calls.
2. Fetch screen metadata — Call

   [prefix]:get_screen

   to retrieve design JSON.
3. Download HTML — Use the reliable downloader:

   bash scripts/fetch-stitch.sh "[htmlCode.downloadUrl]" "temp/source.html"
   

4. Visual reference — Check

   screenshot.downloadUrl

   before writing code.

Step 2: SvelteKit file conventions

SvelteKit uses file-based routing. Map Stitch screens to this structure:

src/
├── routes/
│   ├── +layout.svelte        ← Persistent shell (nav, footer)
│   ├── +layout.ts            ← Layout load function (optional)
│   ├── +page.svelte          ← Route page component
│   ├── [route]/
│   │   ├── +page.svelte      ← Sub-route page
│   │   └── +page.ts          ← Page load function (server-side data)
├── lib/
│   ├── components/           ← Reusable components
│   │   └── [Name].svelte
│   ├── data/
│   │   └── mockData.ts       ← Decoupled static content
│   └── types/
│       └── index.ts          ← Shared types
static/                       ← Static assets

Key rules:

• Pages live in

  src/routes/

  as

  +page.svelte

• Reusable components live in

  src/lib/components/

• Import

  $lib/

  is an alias for

  src/lib/

  — always use it

Step 3: Svelte 5 runes API

Use runes exclusively. Never use the old

export let

let x = 0

$:

Props

<script lang="ts">
  interface Props {
    title: string
    description?: string
    onAction?: () => void
  }

  // $props() replaces export let
  const { title, description = 'Default text', onAction }: Props = $props()
</script>

Reactive state

<script lang="ts">
  // $state() replaces let count = 0
  let count = $state(0)
  let isOpen = $state(false)

  // $derived() replaces $: doubled = count * 2
  const doubled = $derived(count * 2)

  // $effect() replaces onMount / afterUpdate for side effects
  $effect(() => {
    console.log('count changed:', count)
  })
</script>

Event handling

<!-- Direct event attributes, no createEventDispatcher -->
<button onclick={() => count++}>Increment</button>
<button onclick={onAction}>Custom action</button>

Step 4: Scoped CSS with design tokens

Svelte scopes CSS to the component by default — use this aggressively. Map Stitch colors to custom properties in the

:root

+layout.svelte

app.css

In

src/app.css

:root {
  --color-background: #ffffff;
  --color-surface: #f4f4f5;
  --color-primary: /* dominant color from Stitch design */;
  --color-primary-foreground: #ffffff;
  --color-text: #09090b;
  --color-text-muted: #71717a;
  --color-border: #e4e4e7;
}

[data-theme='dark'] {
  --color-background: #09090b;
  --color-surface: #18181b;
  --color-primary: /* same hue, adjusted for dark bg */;
  --color-primary-foreground: #09090b;
  --color-text: #fafafa;
  --color-text-muted: #a1a1aa;
  --color-border: #27272a;
}

In each component (scoped):

<style>
  .card {
    background-color: var(--color-surface);
    border: 1px solid var(--color-border);
    color: var(--color-text);
    border-radius: 0.5rem;
    padding: 1.5rem;
  }

  .card:hover {
    /* Scoped — won't leak to parent or children */
    border-color: var(--color-primary);
  }
</style>

Dark mode toggle — Add a

$state

+layout.svelte

<script lang="ts">
  let theme = $state<'light' | 'dark'>('light')

  function toggleTheme() {
    theme = theme === 'light' ? 'dark' : 'light'
    document.documentElement.setAttribute('data-theme', theme)
  }
</script>

<svelte:element this="div" data-theme={theme}>
  {@render children()}
</svelte:element>

Step 5: Built-in transitions and animations

Svelte has first-class transition support. Apply these from the Stitch design intent:

<script lang="ts">
  import { fade, fly, slide, scale } from 'svelte/transition'
  import { cubicOut } from 'svelte/easing'

  let show = $state(false)
</script>

<!-- Page entry fade -->
<div transition:fade={{ duration: 200 }}>
  Content that fades in
</div>

<!-- Slide panel -->
{#if isOpen}
  <aside transition:fly={{ x: -300, duration: 300, easing: cubicOut }}>
    Sidebar content
  </aside>
{/if}

<!-- Collapsible section -->
{#if expanded}
  <div transition:slide={{ duration: 200 }}>
    Expandable content
  </div>
{/if}

Always respect reduced motion:

<script lang="ts">
  // Check user preference once
  const prefersReducedMotion = $state(
    typeof window !== 'undefined'
      ? window.matchMedia('(prefers-reduced-motion: reduce)').matches
      : false
  )

  // Conditionally disable transitions
  const transitionOptions = $derived(
    prefersReducedMotion ? {} : { duration: 200 }
  )
</script>

<div transition:fade={transitionOptions}>...</div>

Step 6: Accessibility in Svelte

Svelte's compiler warns about missing accessibility attributes — treat all compiler warnings as errors.

• role

  and ARIA: Add

  role

  when using non-semantic elements. Always pair with

  aria-label

  or

  aria-labelledby

  .

• bind:this

  : Use for programmatic focus management (e.g., focus trap in modals).
• Keyboard handlers: Any

  onclick

  handler on a non-interactive element needs

  onkeydown

  /

  onkeyup

  too, or use a

  <button>

  .
• Screen reader text: Use

  class="sr-only"

  (define in app.css) for visually hidden labels.

<!-- Good: button with accessible label -->
<button
  onclick={closeModal}
  aria-label="Close dialog"
  class="icon-btn"
>
  <CloseIcon />
</button>

<!-- Good: Svelte dialog with focus trap -->
<dialog
  bind:this={dialogEl}
  aria-labelledby="dialog-title"
  aria-modal="true"
>
  <h2 id="dialog-title">{title}</h2>
</dialog>

Step 7: Execution steps

1. Environment check — If

   node_modules

   missing, run

   npm install

   .
2. Data layer — Create

   src/lib/data/mockData.ts

   from design content.
3. Component drafting — Use

   resources/component-template.svelte

   as base. Replace all instances of

   StitchComponent

   with the actual component name.
4. CSS tokens — Add color tokens to

   src/app.css

   . If using

   stitch-design-system

   , import its generated

   design-tokens.css

   instead.
5. Wiring — Update

   src/routes/+page.svelte

   to import and use the new components. Import from

   $lib/components/

   .
6. Quality check — Run through

   resources/architecture-checklist.md

   .
7. Dev verification — Run

   npm run dev

   . Toggle dark mode. Test keyboard navigation.

Troubleshooting

svelte: ^5

package.json

$props()

lang="ts"

<script>

<style>

.css

prefers-reduced-motion

$lib

"paths": {"$lib/*": ["src/lib/*"]}

tsconfig.json

localStorage

<svelte:head>

Integration with other skills

• stitch-design-system — Run first to generate

  design-tokens.css

  for the CSS variable foundation.
• stitch-animate — Run after for Svelte-specific transition patterns beyond the basics above.
• stitch-a11y — Run after for a full accessibility audit when the design has complex UI patterns.

References

• resources/component-template.svelte

  — Production-ready Svelte 5 component boilerplate

• resources/architecture-checklist.md

  — Pre-ship quality checklist

• scripts/fetch-stitch.sh

  — Reliable GCS HTML downloader