fmt

.changeset/dark-cows-itch.md

@@ -1,5 +0,0 @@
----
-'@sveltejs/opencode': patch
----
-
-fix: better subagent instructions to use MCP or skill

.changeset/rich-wolves-double.md

@@ -0,0 +1,5 @@
+---
+'@sveltejs/mcp': patch
+---
+
+feat: display similar result & error at the end

packages/mcp-server/src/mcp/handlers/tools/get-documentation.ts

@@ -91,16 +91,56 @@ export async function get_documentation_handler({
 		}
 	});
 
-	const has_any_success = results.some((result) => result.success);
-	let final_text = results.map((r) => r.content).join('\n\n---\n\n');
+	const successes = results.filter((r) => r.success);
+	const failed_sections = sections.filter(
+		(s) =>
+			!available_sections.some(
+				(a) => a.title.toLowerCase() === s.toLowerCase() || a.slug === s || a.url === s,
+			),
+	);
 
-	if (!has_any_success) {
-		const formatted_sections = await format_sections_list();
-
-		final_text += `\n\n---\n\n${SECTIONS_LIST_INTRO}\n\n${formatted_sections}\n\n${SECTIONS_LIST_OUTRO}`;
+	if (successes.length > 0 && failed_sections.length === 0) {
+		return successes.map((r) => r.content).join('\n\n---\n\n');
 	}
 
-	return final_text;
+	const parts: string[] = [];
+
+	if (successes.length > 0) {
+		parts.push(successes.map((r) => r.content).join('\n\n---\n\n'));
+	}
+
+	const fuzzy_results = failed_sections.map((requested) => {
+		const lower = requested.toLowerCase();
+		const matches = available_sections.filter(
+			(a) =>
+				a.title.toLowerCase().includes(lower) ||
+				a.slug.includes(lower) ||
+				lower.includes(a.slug.split('/').pop() ?? '') ||
+				a.use_cases.toLowerCase().includes(lower),
+		);
+		return { requested, matches };
+	});
+
+	const has_fuzzy = fuzzy_results.some((r) => r.matches.length > 0);
+
+	// Full list only when no successes and no fuzzy matches
+	if (successes.length === 0 && !has_fuzzy) {
+		const formatted_sections = await format_sections_list();
+		parts.push(`${SECTIONS_LIST_INTRO}\n\n${formatted_sections}\n\n${SECTIONS_LIST_OUTRO}`);
+	}
+
+	// Similar results then errors
+	for (const { requested, matches } of fuzzy_results) {
+		if (matches.length > 0) {
+			const match_list = matches.map((m) => `- title: ${m.title}, section: ${m.slug}`).join('\n');
+			parts.push(
+				`${matches.length} similar result${matches.length > 1 ? 's' : ''} for "${requested}":\n${match_list}`,
+			);
+		}
+		parts.push(`Section not found: "${requested}".`);
+	}
+
+	return parts.join('\n\n---\n\n');
 }
 
 export function get_documentation(server: SvelteMcp) {

packages/opencode/index.ts

@@ -64,71 +64,9 @@ export const svelte_plugin: Plugin = async (ctx) => {
 				input.agent['svelte-file-editor'] = {
 					color: '#ff3e00',
 					mode: 'subagent',
-					prompt: `You are a Svelte 5 expert responsible for writing, editing, and validating Svelte components and modules. You have access to the Svelte MCP server which provides documentation and code analysis tools. Always use the tools from the svelte MCP server to fetch documentation with \`get_documentation\` and validating the code with \`svelte_autofixer\`. If the autofixer returns any issue or suggestions try to solve them.
-
-If the MCP tools are not available you can use the \`svelte-code-editor\` skill to learn how to use the \`@sveltejs/mcp\` cli to access the same tools.
-
-If the skill is not available you can run \`npx @sveltejs/mcp@latest -y --help\` to learn how to use it.
-
-## Available MCP Tools
-
-### 1. list-sections
-
-Lists all available Svelte 5 and SvelteKit documentation sections with titles and paths. Use this first to discover what documentation is available.
-
-### 2. get-documentation
-
-Retrieves full documentation for specified sections. Accepts a single section name or an array of section names. Use after \`list-sections\` to fetch relevant docs for the task at hand.
-
-**Example sections:** \`$state\`, \`$derived\`, \`$effect\`, \`$props\`, \`$bindable\`, \`snippets\`, \`routing\`, \`load functions\`
-
-### 3. svelte-autofixer
-
-Analyzes Svelte code and returns suggestions to fix issues. Pass the component code directly to this tool. It will detect common mistakes like:
-
-- Using \`$effect\` instead of \`$derived\` for computations
-- Missing cleanup in effects
-- Svelte 4 syntax (\`on:click\`, \`export let\`, \`<slot>\`)
-- Missing keys in \`{#each}\` blocks
-- And more
-
-## Workflow
-
-When invoked to work on a Svelte file:
-
-### 1. Gather Context (if needed)
-
-If you're uncertain about Svelte 5 syntax or patterns, use the MCP tools:
-
-1. Call \`list-sections\` to see available documentation
-2. Call \`get-documentation\` with relevant section names
-
-### 2. Read the Target File
-
-Read the file to understand the current implementation.
-
-### 3. Make Changes
-
-Apply edits following Svelte 5 best practices:
-
-### 4. Validate Changes
-
-After editing, ALWAYS call \`svelte-autofixer\` with the updated code to check for issues.
-
-### 5. Fix Any Issues
-
-If the autofixer reports problems, fix them and re-validate until no issues remain.
-
-## Output Format
-
-After completing your work, provide:
-
-1. Summary of changes made
-2. Any issues found and fixed by the autofixer
-3. Recommendations for further improvements (if any)
-`,
+					prompt: `You are a specialized Svelte coder. Always use the tools from the svelte MCP server to fetch documentation with \`get_documentation\` and validating the code with \`svelte_autofixer\`. If the autofixer returns any issue or suggestions solve them before summarizing the changes for the main agent.`,
 					description:
-						'Specialized Svelte 5 code editor. MUST BE USED PROACTIVELY when creating, editing, or reviewing any .svelte file or .svelte.ts/.svelte.js module and MUST use the tools from the MCP server or the `svelte-code-writer` skill if they are available. Fetches relevant documentation and validates code using the Svelte MCP server tools.',
+						'Specialized Svelte 5 code editor. MUST BE USED PROACTIVELY when creating, editing, or reviewing any .svelte file or .svelte.ts/.svelte.js module and MUST use the tools from the MCP server. Fetches relevant documentation and validates code using the Svelte MCP server tools.',
 					permission: {
 						bash: 'ask',
 						edit: 'allow',

plugins/svelte/agents/svelte-file-editor.md

@@ -1,15 +1,11 @@
 ---
 name: svelte-file-editor
-description: Specialized Svelte 5 code editor. MUST BE USED PROACTIVELY when creating, editing, or reviewing any .svelte file or .svelte.ts/.svelte.js module and MUST use the tools from the MCP server or the `svelte-file-editor` skill if they are available. Fetches relevant documentation and validates code using the Svelte MCP server tools.
+description: Specialized Svelte 5 code editor. MUST BE USED PROACTIVELY when creating, editing, or reviewing any .svelte file or .svelte.ts/.svelte.js module and MUST use the tools from the MCP server. Fetches relevant documentation and validates code using the Svelte MCP server tools.
 permissionMode: acceptEdits
 ---
 
 You are a Svelte 5 expert responsible for writing, editing, and validating Svelte components and modules. You have access to the Svelte MCP server which provides documentation and code analysis tools. Always use the tools from the svelte MCP server to fetch documentation with `get_documentation` and validating the code with `svelte_autofixer`. If the autofixer returns any issue or suggestions try to solve them.
 
-If the MCP tools are not available you can use the `svelte-code-editor` skill to learn how to use the `@sveltejs/mcp` cli to access the same tools.
-
-If the skill is not available you can run `npx @sveltejs/mcp@latest -y --help` to learn how to use it.
-
 ## Available MCP Tools
 
 ### 1. list-sections