diff --git a/documentation/docs/20-commands/20-sv-add.md b/documentation/docs/20-commands/20-sv-add.md
index d8fc782e8..7c0b56ada 100644
--- a/documentation/docs/20-commands/20-sv-add.md
+++ b/documentation/docs/20-commands/20-sv-add.md
@@ -63,28 +63,3 @@ Prevents installing dependencies
 - [`tailwindcss`](tailwind)
 - [`vitest`](vitest)
 
-## Community add-ons
-
-> [!NOTE]
-> Community add-ons are currently **experimental**. The API may change. Don't use them in production yet!
-
-> [!NOTE]
-> Svelte maintainers have not reviewed community add-ons for malicious code!
-
-Community add-ons are npm packages published by the community. Look out for add-ons from your favorite libraries and tools. _(soon)_ many are building `sv` add-ons to make integration a one-liner. You can find them [on npm](https://www.npmx.dev/search?q=keyword:sv-add) by searching for keyword: `sv-add`.
-
-```sh
-# Install a community add-on by org
-npx sv add @supacool
-
-# Use a local add-on (for development or custom/private add-ons)
-npx sv add file:../path/to/my-addon
-
-# Mix and match official and community add-ons
-npx sv add eslint @supacool
-
-# Also works when creating a new project directly
-npx sv create --add eslint @supacool
-```
-
-Want to create your own? Check the [Add-on Docs](community).
diff --git a/documentation/docs/30-add-ons/99-community.md b/documentation/docs/30-add-ons/99-community.md
index 438d25fca..4e7823093 100644
--- a/documentation/docs/30-add-ons/99-community.md
+++ b/documentation/docs/30-add-ons/99-community.md
@@ -2,221 +2,5 @@
 title: [create your own]
 ---
 
-> [!NOTE]
-> Community add-ons are currently **experimental**. The API may change. Don't use them in production yet!
 
-This guide covers how to create, test, and publish community add-ons for `sv`.
 
-## Quick start
-
-The easiest way to create an add-on is using the `addon` template:
-
-```sh
-npx sv create --template addon [path]
-```
-
-The project has a `README.md` and `CONTRIBUTING.md` to guide you along.
-
-## Project structure
-
-Typically, an add-on looks like this:
-
-```js
-// @noErrors
-import { transforms } from '@sveltejs/sv-utils';
-import { defineAddon, defineAddonOptions } from 'sv';
-
-// your add-on definition, the entry point
-export default defineAddon({
-	id: 'your-addon-name',
-
-	// optional: one-liner shown in prompts
-	shortDescription: 'does X',
-
-	// optional: link to docs/repo
-	homepage: 'https://...',
-
-	// Define options for user prompts (or passed as arguments)
-	options: defineAddonOptions()
-		.add('who', {
-			question: 'To whom should the addon say hello?',
-			type: 'string' // boolean | number | select | multiselect
-		})
-		.build(),
-
-	// preparing step, check requirements and dependencies
-	setup: ({ dependsOn }) => {
-		dependsOn('tailwindcss');
-	},
-
-	// actual execution of the addon
-	run: ({ isKit, cancel, sv, options, directory }) => {
-		if (!isKit) return cancel('SvelteKit is required');
-
-		// Add "Hello [who]!" to the root page
-		sv.file(
-			directory.kitRoutes + '/+page.svelte',
-			transforms.svelte(({ ast, svelte }) => {
-				svelte.addFragment(ast, `<p>Hello ${options.who}!</p>`);
-			})
-		);
-	}
-});
-```
-
-> `sv` is responsible for the file system - `sv.file()` accepts a `path` to the file and a callback function to modify it.
-> `@sveltejs/sv-utils` is responsible for the content - `transforms.svelte()` provides you with the proper AST and utils to modify the file. See [sv-utils](/docs/cli/sv-utils) for the full API.
-
-## Development
-
-You can run your add-on locally using the `file:` protocol:
-
-```sh
-cd /path/to/test-project
-npx sv add file:../path/to/my-addon
-```
-
-This allows you to iterate quickly without publishing to npm.
-
-The `file:` protocol also works for custom or private add-ons that you don't intend to publish - for example, to standardize project setup across your team or organization.
-
-> [!NOTE]
-> It is not necessary to build your add-on during development.
-
-## Testing
-
-The `sv/testing` module provides utilities for testing your add-on:
-
-```js
-import { setupTest } from 'sv/testing';
-import { test, expect } from 'vitest';
-import addon from './index.js';
-
-test('adds hello message', async () => {
-	const { content } = await setupTest({
-		addon,
-		options: { who: 'World' },
-		files: {
-			'src/routes/+page.svelte': '<h1>Welcome</h1>'
-		}
-	});
-
-	expect(content('src/routes/+page.svelte')).toContain('Hello World!');
-});
-```
-
-## Publishing
-
-### Bundling
-
-Community add-ons are bundled with [tsdown](https://tsdown.dev/) into a single file. Everything is bundled except `sv`. (It is a peer dependency provided at runtime.)
-
-### `package.json`
-
-Your add-on must have `sv` as a peer dependency and **no** `dependencies` in `package.json`:
-
-```jsonc
-{
-	"name": "@your-org/sv",
-	"version": "1.0.0",
-	"type": "module",
-	// entrypoint during development
-	"exports": {
-		".": "./src/index.js"
-	},
-	"publishConfig": {
-		"access": "public",
-		// entrypoint on build
-		"exports": {
-			".": { "default": "./dist/index.js" }
-		}
-	},
-	// cannot have dependencies
-	"dependencies": {},
-	"peerDependencies": {
-		// minimum version required to run by this addon
-		"sv": "^0.13.0"
-	},
-	// Add this keyword so users can discover your add-on
-	"keywords": ["sv-add"]
-}
-```
-
-### Naming convention
-
-Name your package `@your-org/sv`. Users install it by typing just the org:
-
-```sh
-# npm package: @your-org/sv
-npx sv add @your-org
-```
-
-> [!NOTE]
-> Unscoped packages are not supported yet
-
-### Export options
-
-`sv` first tries to import `your-package/sv`, then falls back to the default export. This means you have two options:
-
-1. **Default export** (recommended for dedicated add-on packages):
-
-   ```json
-   {
-   	"exports": {
-   		".": "./src/index.js"
-   	}
-   }
-   ```
-
-2. **`./sv` export** (for packages that also export other functionality):
-   ```json
-   {
-   	"exports": {
-   		".": "./src/main.js",
-   		"./sv": "./src/addon.js"
-   	}
-   }
-   ```
-
-### Publish to npm
-
-```sh
-npm login
-npm publish
-```
-
-> `prepublishOnly` automatically runs the build before publishing.
-
-## Next steps
-
-You can optionally display guidance in the console after your add-on runs:
-
-```js
-// @noErrors
-import { color } from '@sveltejs/sv-utils';
-
-export default defineAddon({
-	// ...
-	nextSteps: ({ options }) => [
-		`Run ${color.command('npm run dev')} to start developing`,
-		`Check out the docs at https://...`
-	]
-});
-```
-
-## Version compatibility
-
-Your add-on should specify a minimum `sv` version in `peerDependencies`. Your user will get a compatibility warning if their `sv` version has a different major version than what was specified.
-
-## Examples
-
-See the [official add-on source code](https://github.com/sveltejs/cli/tree/main/packages/sv/src/addons) for some real world examples.
-
-## Architecture
-
-The Svelte CLI is split into two packages with a clear boundary:
-
-- **`sv`** = **where and when** to do it. It owns paths, workspace detection, dependency tracking, and file I/O. The engine orchestrates add-on execution.
-- **`@sveltejs/sv-utils`** = **what** to do to content. It provides parsers, language tooling, and typed transforms. Everything here is pure - no file system, no workspace awareness.
-
-This separation means transforms are testable without a workspace and composable across add-ons.
diff --git a/documentation/docs/50-api/20-sv-utils.md b/documentation/docs/50-api/20-sv-utils.md
index 4a714618d..5e364bd61 100644
--- a/documentation/docs/50-api/20-sv-utils.md
+++ b/documentation/docs/50-api/20-sv-utils.md
@@ -2,230 +2,3 @@
 title: sv-utils
 ---
 
-> [!NOTE]
-> `@sveltejs/sv-utils` is currently **experimental**. The API may change. Full documentation is not yet available.
-
-`@sveltejs/sv-utils` is an add-on utilty for parsing, transforming, and generating code..
-
-```sh
-npm install -D @sveltejs/sv-utils
-```
-
-## transforms
-
-`transforms` is a collection of parser-aware functions that lets you modify the files via abstract syntax tree (AST). It accepts a callback function. The return value is designed to be be passed directly into `sv.file()`. The parser choice is baked into the transform type - you can't accidentally parse a vite config as Svelte because you never call a parser yourself.
-
-Each transform injects relevant utilities into the callback, so you only need one import:
-
-```js
-import { transforms } from '@sveltejs/sv-utils';
-
-transforms.script(/* ... */);
-transforms.svelte(/* ... */);
-// ...
-```
-
-### `transforms.script`
-
-Transform a JavaScript/TypeScript file. The callback receives `{ ast, comments, content, js }`.
-
-```js
-// @noErrors
-import { transforms } from '@sveltejs/sv-utils';
-
-sv.file(
-	files.viteConfig,
-	transforms.script(({ ast, js }) => {
-		js.imports.addDefault(ast, { as: 'foo', from: 'foo' });
-		js.vite.addPlugin(ast, { code: 'foo()' });
-	})
-);
-```
-
-### `transforms.svelte`
-
-Transform a Svelte component. The callback receives `{ ast, content, svelte, js }`.
-
-```js
-// @noErrors
-import { transforms } from '@sveltejs/sv-utils';
-
-sv.file(
-	layoutPath,
-	transforms.svelte(({ ast, svelte }) => {
-		svelte.addFragment(ast, '<Foo />');
-	})
-);
-```
-
-### `transforms.svelteScript`
-
-Transform a Svelte component with a `<script>` block guaranteed. Pass `{ language }` as the first argument. The callback receives `{ ast, content, svelte, js }` where `ast.instance` is always non-null.
-
-```js
-// @noErrors
-import { transforms } from '@sveltejs/sv-utils';
-
-sv.file(
-	layoutPath,
-	transforms.svelteScript({ language: 'ts' }, ({ ast, svelte, js }) => {
-		js.imports.addDefault(ast.instance.content, { as: 'Foo', from: './Foo.svelte' });
-		svelte.addFragment(ast, '<Foo />');
-	})
-);
-```
-
-### `transforms.css`
-
-Transform a CSS file. The callback receives `{ ast, content, css }`.
-
-```js
-// @noErrors
-import { transforms } from '@sveltejs/sv-utils';
-
-sv.file(
-	files.stylesheet,
-	transforms.css(({ ast, css }) => {
-		css.addAtRule(ast, { name: 'import', params: "'tailwindcss'" });
-	})
-);
-```
-
-### `transforms.json`
-
-Transform a JSON file. Mutate the `data` object directly. The callback receives `{ data, content, json }`.
-
-```js
-// @noErrors
-import { transforms } from '@sveltejs/sv-utils';
-
-sv.file(
-	files.tsconfig,
-	transforms.json(({ data }) => {
-		data.compilerOptions ??= {};
-		data.compilerOptions.strict = true;
-	})
-);
-```
-
-### `transforms.yaml` / `transforms.toml`
-
-Same pattern as `transforms.json`, for YAML and TOML files respectively. The callback receives `{ data, content }`.
-
-### `transforms.text`
-
-Transform a plain text file (.env, .gitignore, etc.). No parser - string in, string out. The callback receives `{ content, text }`.
-
-```js
-// @noErrors
-import { transforms } from '@sveltejs/sv-utils';
-
-sv.file(
-	'.env',
-	transforms.text(({ content }) => {
-		return content + '\nDATABASE_URL="file:local.db"';
-	})
-);
-```
-
-### Aborting a transform
-
-Return `false` from any transform callback to abort - the original content is returned unchanged.
-
-```js
-// @noErrors
-import { transforms } from '@sveltejs/sv-utils';
-
-sv.file(
-	files.eslintConfig,
-	transforms.script(({ ast, js }) => {
-		const { value: existing } = js.exports.createDefault(ast, { fallback: myConfig });
-		if (existing !== myConfig) {
-			// config already exists, don't touch it
-			return false;
-		}
-		// ... continue modifying ast
-	})
-);
-```
-
-### Standalone usage & testing
-
-Transforms are curried functions - call them with the callback, then apply to content:
-
-```js
-import { transforms } from '@sveltejs/sv-utils';
-
-const transform = transforms.script(({ ast, js }) => {
-	js.imports.addDefault(ast, { as: 'foo', from: 'foo' });
-});
-const result = transform('export default {}');
-```
-
-### Composability
-
-For cases where you need to mix and match transforms and raw edits, use `sv.file` with a content callback and invoke the curried transform manually:
-
-```js
-// @noErrors
-sv.file(path, (content) => {
-	// curried
-	const transform = transforms.script(({ ast, js }) => {
-		js.imports.addDefault(ast, { as: 'foo', from: 'bar' });
-	});
-
-	// parser manipulation
-	content = transform(content);
-
-	// raw string manipulation
-	content = content.replace('foo', 'baz');
-
-	return content;
-});
-```
-
-Add-ons can also export reusable transform functions:
-
-```js
-// @errors: 7006
-import { transforms } from '@sveltejs/sv-utils';
-
-// reusable - export from your package
-export const addFooImport = transforms.svelte(({ ast, svelte, js }) => {
-	svelte.ensureScript(ast, { language });
-	js.imports.addDefault(ast.instance.content, { as: 'Foo', from: './Foo.svelte' });
-});
-```
-
-```js
-sv.file('+page.svelte', addFooImport);
-sv.file('index.svelte', addFooImport);
-```
-
-## Parsers (low-level)
-
-`transforms` will fit most users needs (e.g., conditional parsing, error handling around the parser). If not, `parse` is a low-level API available to you:
-
-```js
-// @noErrors
-import { parse } from '@sveltejs/sv-utils';
-
-const { ast, generateCode } = parse.script(content);
-const { ast, generateCode } = parse.svelte(content);
-const { ast, generateCode } = parse.css(content);
-const { data, generateCode } = parse.json(content);
-const { data, generateCode } = parse.yaml(content);
-const { data, generateCode } = parse.toml(content);
-const { ast, generateCode } = parse.html(content);
-```
-
-## Language tooling
-
-Namespaced helpers for AST manipulation:
-
-- **`js.*`** - imports, exports, objects, arrays, variables, functions, vite config helpers, SvelteKit helpers
-- **`css.*`** - rules, declarations, at-rules, imports
-- **`svelte.*`** - ensureScript, addSlot, addFragment
-- **`json.*`** - arrayUpsert, packageScriptsUpsert
-- **`html.*`** - attribute manipulation
-- **`text.*`** - upsert lines in flat files (.env, .gitignore)