Skip to content

Adopt the Svelte team's skills for the SvelteKit products #652

Description

@devantler

Problem

Three products build their web front ends with SvelteKit and TypeScript: business-site web/, wedding-app and ascoachingogvaner. No bundled skill covers Svelte. frontend-design and web-design-guidelines are framework-neutral, and astro only fits the two Astro sites (the KSail docs and the KHoist website). The skill coverage audit (#637) records this as a confirmed gap.

Proposal

Evaluate the Svelte team's own skills from sveltejs/ai-tools (MIT, maintained by the Svelte core team). If they pass, install them with gh skill install, so that upstream provenance and the daily updater apply:

  • svelte-core-bestpractices: guidance only, so low risk.
  • svelte-code-writer: only if its tool use passes review. It runs Svelte's documentation and analysis CLI, so check what it executes, whether it needs network access, and whether it works in Copilot and Codex as well as Claude Code.

Record the adopt-or-reject decision with #641's rubric: provenance, licence, maintenance, supply chain, compatibility and upkeep. Add the licence row and notice the catalogue requires.

Dependencies

Test scenarios

  • Should trigger: "Add a form action to this SvelteKit route that validates the RSVP input" loads svelte-core-bestpractices.
  • Near miss: "Add a page to the KSail docs site" loads astro, not a Svelte skill.
  • Adherence: generated components use the Svelte major version that the project's package.json declares, and svelte-check passes.
  • Over-trigger guard: "What branch am I on?" loads no skill.

Acceptance criteria

  • The decision (adopt or reject, with reasons) is recorded on this issue.
  • If adopted: installed with upstream provenance, both manifests and the catalogue updated, plugin version bumped, CI green.
  • The activation cases are in Measure skill activation and adherence with a claude plugin eval suite #651's suite, or listed there if the suite has not landed yet.
  • The SvelteKit row in docs/skill-coverage.md is updated.

Follow-up from the skill coverage audit (#637).

🤖 Generated with Claude Code

Activity

  1. added theissue type on Nov 4, 2026
  2. moved this to 📥 Backlog in 🌊 Project Boardon Nov 4, 2026
  3. added 2 commits that reference this issue on Nov 4, 2026
  4. moved this from 📥 Backlog to 🏃🏻‍♂️ In Progress in 🌊 Project Boardon Nov 10, 2026
  5. devantler commented on Nov 10, 2026

    @devantler
    ContributorAuthor

    🤖 Generated by the Agentic Engineer (interactive Claude Code session)

    Decision record: adopt svelte-core-bestpractices, reject svelte-code-writer

    Checked on 2026-11-10 against main (f57eb03) and the upstream tag @sveltejs/mcp@0.1.30.

    Criterion (#641's list) svelte-core-bestpractices svelte-code-writer
    Function Guidance for Svelte 5: reactivity, events, styling, library integration. It fills the framework gap for the three SvelteKit products Tells the agent to run a documentation and autofixer CLI
    Provenance sveltejs/ai-tools, maintained by the Svelte team Same
    Licence MIT. The notice and licence row are in the plugin's third-party notices and the catalogue Same
    Maintenance Active: the upstream was pushed to today, and its last release was on 2026-11-04 Same
    Supply chain Text only. It runs nothing and needs no network Runs npx @sveltejs/mcp with no version, so every call downloads and executes whatever is latest
    Compatibility Plain skill text, so it works in Claude Code, Copilot and Codex Needs Node, npx and network access in every host
    Tests Passes the pinned spec validator and the licence and provenance checks in CI Not evaluated further
    Upkeep The daily updater proposes upstream changes as reviewable PRs Would add an unpinned runtime dependency to review on every release

    Adopted: svelte-core-bestpractices. It has been bundled since 7.0.0 (#650), installed with its upstream provenance (repository, path, tag and tree hash in the skill's metadata), with both manifests, the catalogue and the plugin version updated in that release.

    Rejected: svelte-code-writer. Its whole function is to run an unpinned package on each call. The plugin already bundles the Svelte team's hosted svelte documentation server, which offers the same documentation lookup and autofixer as read-only tools with nothing to download, so the skill would add risk and no capability. #650 made the same call for every skill that runs tools through npx.

    Listing budget: the adopted skill's description is 244 characters. No other description changed.

    Activation cases are listed on #651 (comment), because the suite has not landed yet.

    Coverage overview: #672 marks the SvelteKit row covered and records both decisions. It also corrects the Astro row, which still said the Astro skill was bundled.

    🤖 Generated with Claude Code

  6. moved this from 🏃🏻‍♂️ In Progress to ✅ Done in 🌊 Project Boardon Nov 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Fields

    Priority

    None yet

    Start date

    None yet

    Target date

    None yet

    Effort

    None yet

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions