메뉴
Test setup in the AMC web repo — the two Vitest projects (browser component tests vs node unit tests), file-naming rules that decide which project runs a test, and how to run them. Read before writing or running tests.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
The pakop C#/.NET WASM module (CUE4Parse-based) — what it does (pak-file inspection/hashing), how to build it (pnpm build:pakop), and how to consume it (lazy dynamic import). Read before touching wasm/pakop or the pak routes.
How to fetch data in the AMC web app — the apiClient helper, visibility-aware polling / EventSource / WebSocket wrappers in src/lib/api/_api.ts, per-domain API modules, and protobuf decoding. Read before adding any network call.
The AMC app shell — hooks.server.ts prerender-time head injection (SEO meta, theme-color, font preloads, icons), hooks.ts URL delocalization, and asset import suffixes (?no-inline, ?url). Read before changing global head tags, fonts, SEO metadata, or hooks.
High-level architecture of the AMC web app — SvelteKit static/SPA hybrid, Vite plugin pipeline, i18n strategy, WASM modules, dev-server proxies. Read before making structural or build-related changes.
Utility function conventions in the AMC web repo — es-toolkit for lodash-like helpers (lodash-es was removed), but check src/lib/utils first. Read before adding utility helpers.
Import path aliases ($lib, $messages) and workspace packages used in the AMC web repo. Read when writing imports or resolving where a module comes from.
| name | testing |
| description | Test setup in the AMC web repo — the two Vitest projects (browser component tests vs node unit tests), file-naming rules that decide which project runs a test, and how to run them. Read before writing or running tests. |
Vitest with two projects defined in vitest.config.ts (which merges vite.config.ts). The file name decides which project runs a test:
| Project | File pattern | Environment |
|---|---|---|
comp | src/**/*.svelte.{test,spec}.ts | Real Chromium via Playwright browser provider (headless) |
unit | src/**/*.{test,spec}.ts (rest) | Node |
<Name>.svelte.test.ts and use vitest-browser-svelte to render components in the real browser..test.ts files next to the code (see src/lib/utils/*.test.ts, src/lib/schema/track.test.ts, src/lib/api/_api.test.ts).pnpm test # single run, all projects — prefer this
pnpm test:unit # watch mode
pnpm exec vitest run --project unit # node tests only
pnpm exec vitest run path/to/file.test.ts # one file
pnpm test also runs in the lefthook pre-commit pipeline, so keep tests fast and deterministic — see [[git-hooks]].
tests/ tree.pnpm check (svelte-check) is the type-level gate and runs separately from Vitest.Related: [[codebase-patterns]], [[git-hooks]], [[architecture]]