svelte-mcp-feedback
Svelte MCP feedback
Turn a user-corrected mistake into actionable feedback for the Svelte MCP autofixer in sveltejs/ai-tools.
1. Identify the autofixer opportunity
Use the conversation and the code you just worked on to identify:
- The incorrect code you produced and the user's correction.
- The Svelte or SvelteKit rule that explains the correction.
- A reusable code pattern the MCP could detect, and the fix or suggestion it could provide.
Include SvelteKit JavaScript/TypeScript files such as +page.ts, +layout.server.ts, +server.ts, hooks.server.ts, and svelte.config.js; feedback is not limited to .svelte files.
Only proceed if there is a concrete, generalizable Svelte/SvelteKit mistake. A changed product requirement, a personal naming preference, or an unrelated application bug does not justify an autofixer issue. If the correction is ambiguous, clarify it while continuing the user's task.
Apply the user's correction and complete the requested work. Reporting feedback should not leave the original mistake unfixed.