メニュー
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.
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.
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 | architecture |
| description | 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. |
This is a SvelteKit site using Svelte 5 with TypeScript, built for the ASEAN Motor Club community.
@sveltejs/adapter-static with fallback: 'fallback.html' — a hybrid: pages are prerendered where possible (export const prerender = 'auto' in src/routes/+layout.ts), and everything else runs as an SPA via the fallback page.build/. The site must remain statically buildable — no server-side runtime./stream (explicitly ignored in svelte.config.js).messages/{en,id,ms,th,tl,vi}.json; compiled output in src/lib/paraglide/ (generated — never edit manually).pnpm paraglide:compile.['custom-svelteReactiveLocale', 'baseLocale'], persisted in localStorage key siteLocale.src/hooks.ts via reroute + deLocalizeUrl.amc-uno-css-config package (a GitHub dependency) and extended in unocss.config.ts.@unocss/extractor-svelte (not svelte-scoped mode).unocss.config.ts has a blocklist to avoid false-positive class extraction (e.g. paraglide m. / m['...'] calls, bare m2/w10-style tokens).wasm/pakop/ (Pakop.csproj, CUE4Parse-based; no Blazor).pnpm build:pakop (dotnet build -c Release; required before pnpm dev/pnpm build); requires .NET 10 SDK + dotnet workload install wasm-tools. The pakop shim imports dotnet.js straight from the dotnet build output; the bundler-friendly dotnet.js statically imports all runtime assets, so Vite bundles them with hashed names into _app/immutable/assets/.pakop is the committed shim wasm/pakop/index.js/index.d.ts (pnpm-workspace.yaml includes wasm/**; the app depends on pakop: workspace:*).await import('pakop') (see src/routes/pak/)..proto definitions in src/lib/api/proto/; generated _pb.ts files in src/lib/api/proto/generated/ via pnpm proto:generate (buf, config in buf.gen.yaml). Runtime is @bufbuild/protobuf.eslint.config.js). Git hooks via lefthook (lefthook.yml).@vitest/browser-playwright, chromium) for component tests in a real browser; plain node tests for pure TS.pnpm storybook) for UI component development.Related: [[project-structure]], [[path-aliases]], [[app-shell]], [[env-config]], [[pakop-wasm]]