Repository navigation
Description
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
- Standardize research, adoption, pinning and authoring of agent skills #641: the decision record and scorecard. If the template has not landed yet, use its acceptance criteria as the checklist.
- Bundled upstream skills: reviewable updates and clear redistribution terms #581: reviewable updates and clear redistribution terms for bundled upstream skills.
- Measure skill activation and adherence with a claude plugin eval suite #651: add the activation cases below to the eval suite.
- Listing budget (finding 1 in Spike: evaluate whether agents select and apply the right skills #642): report how many description characters the PR adds, and do not push existing skills down to name-only.
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.jsondeclares, andsvelte-checkpasses. - 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.mdis updated.
Follow-up from the skill coverage audit (#637).
🤖 Generated with Claude Code
Metadata
Metadata
Assignees
Labels
Type
Fields
Priority
Start date
Target date
Effort
Projects
- StatusShow more project fields✅ Done
Activity
docs: record skill coverage across the portfolio (#655)
chore: agent-claim #652 nonce=de454996fe6144dd713e49163fb7ca2f
devantler commentedon Nov 10, 2026
Decision record: adopt
svelte-core-bestpractices, rejectsvelte-code-writerChecked on 2026-11-10 against
main(f57eb03) and the upstream tag@sveltejs/mcp@0.1.30.svelte-core-bestpracticessvelte-code-writersveltejs/ai-tools, maintained by the Svelte teamnpx @sveltejs/mcpwith no version, so every call downloads and executes whatever is latestnpxand network access in every hostAdopted:
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 hostedsveltedocumentation 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 throughnpx.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
docs(coverage): record the Svelte adoption and the Astro removal (#672)