I scored this repo for AI-Readiness and it got 38%,

[Wolfe-Jam]

Inspired by @MathiasWP's story 👏, decided to share this here.

I scored this repo for AI-Readiness and it got 38%, so I built a tool to improve the score, and now it gets 100%. The two files are below — now AI knows what I'm working on and is optimized for my exact project.

Before (38%)

# sveltejs/svelte
project:
  name: svelte-monorepo
  goal: monorepo for svelte and friends
  main_language: TypeScript
  type: frontend
  frontend: SvelteKit

After (100%)

# sveltejs/svelte
project:
  name: svelte
  goal: Cybernetically enhanced web apps
  main_language: TypeScript
  type: framework
  framework: svelte
stack:
  frontend: SvelteKit
  state_management: Runes
  backend: SvelteKit
  api_type: Server Routes
  runtime: Node.js
  build: Vite
  cicd: GitHub Actions
human_context:
  who: Svelte core team and open-source contributors
  what: Compiler-first web framework — components compile to vanilla JS with no runtime overhead
  why: Web development should be simple, fast, and accessible to everyone
  where: npm (svelte, @sveltejs/kit), used in production worldwide
  when: Created 2016 by Rich Harris, Svelte 5 (Runes) released 2024
  how: Open-source, MIT licensed, community-driven with full-time maintainers

[oliviacraft]

Great timing on this — the AI-readiness scoring concept captures something real. Structured project context (whether YAML, CLAUDE.md, or the GEMINI_SYSTEM_MD format) makes a measurable difference in output quality.

A layer worth adding beyond project metadata: the behavioral rules that prevent version-specific drift. For Svelte 5 specifically, AI tools trained mostly on Svelte 4 examples will default to the old patterns without explicit guidance:

## Svelte 5 Rules
- Runes only. No reactive declarations ($:), no stores (writable/readable/derived).
- $state, $derived, $effect, $props — these are the primitives. Use them.  
- $effect runs after the DOM updates. Never use it to compute values — use $derived instead.
- Event handlers: onclick={fn} not on:click={fn}
- Snippets for reusable template fragments. Children via {#snippet children()}{/snippet} + {@render children()}
- No createEventDispatcher — use callback props instead
- SvelteKit: server-only data in +page.server.ts, shared in +page.ts

These seven rules eliminate the most common Svelte 5 drift we have seen. The project metadata tells the AI what you are building; the behavioral rules tell it which patterns are allowed.

We published a free Svelte 5 CLAUDE.md starter with the full 15-rule set: https://gist.github.com/oliviacraft/2d7f21b68741593b292c01401772ca01

[Wolfe-Jam]

Thanks Olivia. Layer separation is the right frame: FAF for what's true (project metadata), MD for what's
allowed (behavioral rules). Different lanes — they don't compete, they complement each other, FAF defines, MD
instructs. Your Svelte 5 rules are a clean reference; bookmarked.