菜单
Use when you have an ad-hoc Svelte component or `.svelte.js`/`.svelte.ts` module (pasted inline, scratch file, or a single existing file) and need a one-shot parity check against `svelte/compiler` without registering a persistent case.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use whenever adding an e2e compiler-output test (our JS vs the reference compiler) — a new cluster case under `tasks/compiler_tests/`.
🧩 PARITY · Turn one divergence from the Original into a test per affected case (does not fix).
Use when starting any compiler task or session before touching parser/analyze/transform/ast/codegen/css/diagnostics code, before proposing a design or writing code, and when the task grows into a new layer and you need its PRD invariants.
🔪 SDT · verdict-directed review of backend codegen/transform. Use when auditing codegen/transform for smart-analyzer / dumb-codegen violations, or when porting a transform/codegen visitor from the Original.
The required unit-test format for `crates/**/src/**` — use when writing or reviewing a Rust `#[test]`, a test helper, or an `assert_*`. Not for `tasks/compiler_tests/` (use add-test) or `tasks/diagnostic_tests/` (use add-diagnostic-test).
PRD editorial standard for docs/. Use when writing a new PRD, extending one, or reviewing changes under docs/ — and when another skill needs the PRD rules.
| name | quick-check |
| description | Use when you have an ad-hoc Svelte component or `.svelte.js`/`.svelte.ts` module (pasted inline, scratch file, or a single existing file) and need a one-shot parity check against `svelte/compiler` without registering a persistent case. |
| argument-hint | <path-or-inline-source> [--mode=auto|runes|legacy] [--generate=client|server] [--dev] [--filename=<name>] [--print=diff|ours|ref|both] |
| allowed-tools | Bash, Write |
One-shot compile of one component (compares JS + whitespace-normalized CSS) or .svelte.js/.svelte.ts module (JS only) against the reference compiler. Dispatch is by extension: .svelte.js/.svelte.ts → compile_module, else compile. Does NOT register tests or touch compiler code.
Not for: persisted finding → /dig; directory survey → just sweep-run <dir> --dry-run; permanent case → /add-test or /add-diagnostic-test; about to fix a crate → /dig first.
just quick-check <path> [flags] # existing file
printf '%s' "$SRC" | just quick-check - [flags] # inline source via stdin — no repo files
Prefer stdin for inline source: - reads stdin, the reference side gets an auto-removed temp file in /tmp, nothing lands in the repo. Type is inferred from --filename extension (default .svelte); for modules add --filename=x.svelte.js or x.svelte.ts. Use cat <<'EOF' so $state/backticks survive shell quoting. Only fall back to git-ignored scratch (tasks/quick_check/scratch.svelte{,.js,.ts}) when re-running while hand-editing; never write to tasks/compiler_tests/cases2/.
Flags (forwarded to both sides; pass through whatever the user named):
--mode=auto|runes|legacy — default runes unless <svelte:options runes={false}/>. Ignored for modules.--generate=client|server — default client.--dev — dev build.--filename=<name> — component-name resolution / module filename.--print=diff|ours|ref|both — default diff (interleaved < ours / > ref). both prints full outputs even on match; ours/ref print one side. Exit code unchanged.0 OK — JS + CSS match. Report flags applied + JS line / CSS byte counts.1 MISMATCH — diff under -- JS -- / -- CSS --; summarize divergence categories, call out first mismatching block.2 INPUT — missing file / bad args.3 PANIC — Rust panicked or no JS; name the message, guess owning layer (parser/analyze/transform/codegen).4 NODE — reference failed; likely invalid syntax or missing npm deps.Warn and skip SvelteKit/MDsveX-specific input (unresolvable imports/types). Standalone runes-in-module code is fine even with unresolved external imports.