llms.txt is an open proposal for a short Markdown file that lists a project's key docs and links, so AI tools can find them without crawling every page.

Where should llms.txt be deployed?

At /llms.txt on your documentation site, or in your repository root. Tools read it when they fetch it; nothing loads it automatically.

# SvelteKit 5 & Svelte 5 Runes Specialist

> Modern SvelteKit 5 standards enforcing Svelte 5 Runes ($state, $derived, $props), server load functions, and form actions.

## Quick Reference

- **Framework**: SvelteKit 5 & Svelte 5

- **Language**: TypeScript

- **Styling & UI**: Tailwind CSS

- **Database / Persistence**: PostgreSQL / SQLite

- **Architectural Philosophy**: modern

## Core Architectural Invariants

- **Feature-Colocated Structure**: Group components, hooks, tests, and utils inside domain feature folders.

- **Guard Clauses & Early Returns**: Exit early from functions to eliminate deeply nested if-else pyramids.

- **Self-Documenting Naming**: Expressive function and variable names over verbose redundant comments.

## Operational Guardrails & Prohibited Patterns

- **Inspect Before Acting**: Always read and understand existing code and imports before suggesting changes.

- **Minimal Surgical Diffs**: Touch only lines relevant to prompt. Preserve existing comments and formatting.

- **Concise & Direct Tone**: Skip conversational pleasantries. Deliver focused diffs and a short rationale.

## Mandatory Project Directives

- Never mix Svelte 4 reactivity syntax with Svelte 5 runes.

- Keep server-only code strictly in *.server.ts files.

## Implementation Reference

### Preferred Patterns

```typescript

interface Props {

initialCount?: number;

}

let { initialCount = 0 }: Props = $props();

let count = $state(initialCount);

let double = $derived(count * 2);

</script>

```

### Discouraged Anti-Patterns

```typescript

// Discouraged: Legacy Svelte 3/4 syntax

export let initialCount = 0;

let count = initialCount;

$: double = count * 2;

</script>

```

## Verification Commands & Workflows

1. Use Svelte 5 runes: $state(), $derived(), $effect(), and $props().

2. Ban legacy Svelte 3/4 'let' reactivity and '$: ' reactive labels.

3. Load data server-side in +page.server.ts load() functions.

4. Execute mutations using standard SvelteKit Form Actions with use:enhance.

## Context Documents & Specs

- [System Architecture](ARCHITECTURE.md): Authoritative system design, data flows, and state machine invariants.

- [AI Multi-Agent Spec](AGENTS.md): Universal specification for autonomous coding agent operations.

Frontend · Any LLM tool that fetches it

SvelteKit & Svelte 5 llms.txt

An llms.txt for a SvelteKit & Svelte 5 project: a short Markdown map of what it is and where the key docs and code live.

Path: llms.txt
Loads: Fetched on request
Format: Markdown index (.txt)
Used by: Any LLM tool that fetches it

All llms.txt presets and how llms.txt works

What this file tells the agent

An llms.txt gives language models and agents a short Markdown map of your SvelteKit & Svelte 5 project: what it is and where the key docs and code live, so a tool that fetches it can go straight to the right files.

Use Svelte 5 runes: `$state()`, `$derived()`, and `$props()`.
Never use obsolete Svelte 3/4 `export let` or `$: ` reactive labels.
Implement data loading in `+page.server.ts` load functions.
Handle data mutations via standard SvelteKit Form Actions with `enhance`.

Install it in one command

01
Go to your project root
The file goes at llms.txt, relative to the root.
02
Download the file
Run the command on the right. It downloads this preset and writes the file.
03
Make sure it gets used
Nothing loads llms.txt automatically. Serve it at your site root, or point agents to it from CLAUDE.md or AGENTS.md.

$ curl -fsSL "https://www.devscratchpad.tech/api/raw/llms-txt/sveltekit" -o "llms.txt"

writes llms.txt

path

llms.txt

To write the file from your own code instead, use Read your code or Convert Legacy Rules in the editor above.

More for SvelteKit & Svelte 5

Other formats

Other llms.txt presets

Questions

What is llms.txt?: llms.txt is an open proposal for a short Markdown file that lists a project's key docs and links, so AI tools can find them without crawling every page.
Where should llms.txt be deployed?: At /llms.txt on your documentation site, or in your repository root. Tools read it when they fetch it; nothing loads it automatically.

Target Standard & File Format

Identity & Activation Rules

Technology Stack Context

Engineering Philosophy

Architectural & Code Quality Conventions

Agent Behavioral Guardrails

Step-by-Step Workflow Procedures

Target File Location