Agent skill · civitai
svelte-review
Run the three SvelteKit review agents (correctness, Svelte 5 idiom + UI conventions, abstraction) over a feature segment in apps/moderator, apps/auth or apps/creator-studio, and consolidate their findings. Use before calling a segment done, or when asked to review Svelte app work.
What it needs
About 3k tokens when loaded.
What this skill does
SvelteKit segment review The standard pre-completion review for the SvelteKit apps. A segment is not done until this has run and its findings are resolved. The conventions being enforced are docs/svelte-app-standard.md plus the reviewed app's own CLAUDE.md. These three lanes are pre-authorised. They do not count against a standing instruction not to spawn subagents unasked — running them needs no separate permission, and neither does chasing a lane that goes idle. That covers the review lanes only; everything else about spawning is unchanged. 1. Scope the segment Work out exactly what is under review and say so before spawning anything: A "segment" is one slice of work — a page, a panel group, a service and its route. If the diff spans several unrelated slices, review them one at a time; findings from a mixed diff are hard to act on. Include uncommitted changes: the review exists to run before the commit. Name the app. All three agents take the app directory as their scope, and the UI half of the idiom review differs per app — apps/auth uses neither @civitai/ui nor text-dark-2 yet. 2. Fan out Agent Reviews --- --- svelte-correctness-review Logic, data shape, auth scope, failure paths svelte-idiom-review Svelte 5 idiom + the shared UI/styling conventions svelte-abstraction-review Duplication, missing components, placement Give each the same scope: the app directory, the file list, and any context it can't recover from the code — what the segment is meant to do, and what was deliberately left out. Running them serially is the safe default. Three at once is heavy, and on one occasion coincided with the session dying mid-review; serial has been reliable. Spawn them together only when the segment is small. The three overlap at the edges by design; deduplicate at step 4. 3. If the segment was PORTED, add a fourth pass The three above compare the code to itself and to the standard. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills civitai/svelte-review