メニュー
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.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
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.
Overlay/floating UI conventions in the AMC web repo — use the homegrown `portal` action from $lib/utils/portal (svelte-portal package is not used/dependency), as done in Tooltip and Modal. Read before building modals, tooltips, or popovers.
| name | pakop-wasm |
| description | 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. |
wasm/pakop/ (Pakop.csproj, .NET 10 browser WASM, no Blazor); provides pak-file inspection and hashing (list, list_hash, get_datatables_names, print_exports) used by the /pak routes (src/routes/pak/). Built on CUE4Parse.pnpm build:pakop (dotnet build -c Release; required before pnpm dev/pnpm build, rerun after C# changes — in CI the wasm.yml workflow builds it once and shares the artifact). Requires .NET SDK 10 + dotnet workload install wasm-tools../bin/Release/net10.0/wwwroot/_framework/dotnet.js directly. The bundler-friendly dotnet.js statically imports every runtime .wasm asset, so Vite bundles the whole graph with content-hashed names into _app/immutable/assets/. Since Vite 8.1, its built-in wasm-ESM integration intercepts direct .wasm imports and expects a default export from the parsed module — the .NET runtime's .wasm blobs don't have one, which breaks the build (MISSING_EXPORT "default"). vite-plugins/dotnet-wasm-asset.ts (dotnetWasmAssetPlugin, registered first in vite.config.ts) works around this by resolving those specific _framework/**/*.{wasm,pdb,dat} imports with a ?url suffix, which is exempt from that interception and resolves as a plain asset URL.pakop is the committed shim wasm/pakop/index.js + index.d.ts: it statically imports /assets/_framework/dotnet.js, initializes via top-level await, then exposes synchronous functions delegating to [JSExport] methods in Interop.cs. list_hash returns JSON-parsed plain objects.const { list_hash } = await import('pakop');
dotnet format wasm/pakop --verify-no-changes (enforced by lefthook) and require a rebuild (pnpm build:pakop) before the frontend sees them.optimizeDeps.exclude: ['pakop'] and server.fs.allow includes wasm/; the pnpm workspace glob is wasm/* (direct children only — the dotnet build output contains a copied package.json that a deep glob would pick up as a duplicate workspace package).Related: [[architecture]], [[git-hooks]], [[path-aliases]]