원클릭으로 Manus에서 모든 스킬 실행

yo-wasm-integration

스타28

포크0

업데이트2026년 5월 9일 13:24

Build Yo libraries for WebAssembly and publish as npm packages. Use this when working with WASM targets, Emscripten, WASI, npm packaging, JavaScript/TypeScript wrappers, or browser/Node.js integration.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

shd101wyy

shd101wyy/Yo

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Yo WASM Integration

Use this skill for compiling Yo projects to WebAssembly and packaging them for JavaScript/TypeScript consumption via npm.

When to use this skill

Use this skill when you need to:

compile a Yo project to WebAssembly (Emscripten or WASI)
set up an npm/ package directory with JavaScript/TypeScript wrappers
expose Yo functions to JavaScript via WASM memory and C ABI
integrate a Yo WASM module into a Node.js or browser project
debug WASM-specific compilation or runtime issues
publish a Yo-backed npm package

Workflow

Decide on target: Emscripten (browser + Node.js) or WASI (standalone/server).
Define WASM build steps in build.yo using build.executable with target: build.CompilationTarget.Wasm32_Emscripten and add_c_flags(...) for Emscripten settings.
Create a JavaScript wrapper in npm/ that loads the WASM module and exposes a clean API.
Add TypeScript declarations (index.d.ts) for type safety.
Test the WASM module from both Node.js and browser contexts.
Consult the WASM integration cheatsheet for patterns.

High-signal rules

In build.yo, use target: build.CompilationTarget.Wasm32_Emscripten for Emscripten WASM builds. Use step.add_c_flags(...) for Emscripten -s options.
For single-file compilation, use yo compile --cc emcc or yo compile --target wasm-wasi.
WASM functions communicate through linear memory — pass pointers and lengths, not Yo types.
JavaScript wrappers handle the string encoding/decoding boundary (TextEncoder/TextDecoder).
Use bitmask flags (powers of 2) to pass option sets through a single i32 parameter.
Yo's str and String types are internal — export raw *(u8) + usize pairs for WASM APIs.
Always test with --sanitize address on native first, then verify WASM behavior matches.
Emscripten exports are controlled by -sEXPORTED_FUNCTIONS and -sEXPORTED_RUNTIME_METHODS.
WASM modules can be loaded in Node.js using WebAssembly.instantiate or Emscripten's generated JS glue.
Errno values differ on WASM — use constants from std/libc/errno, never hardcode numbers.

Resource

WASM integration cheatsheet

이 저장소의 다른 Skills

같은 저장소

yo-core-patterns

shd101wyy/Yo

Write everyday Yo application and library code. Use this when choosing Yo types, imports, strings, Option/Result, collections, traits, boxes, pointers, and standard-library modules.

2026-06-1228

yo-syntax

shd101wyy/Yo

Write and repair Yo source code. Use this when authoring, reviewing, or debugging .yo files, especially around declarations, begin blocks, cond/match, imports, recursion, function calls, and parser-facing errors.

2026-06-1228

yo-async-effects

shd101wyy/Yo

Write Yo async code and algebraic effect handlers. Use this when working with Io, Future, JoinHandle, ctl/fn handlers, io.async, io.await, io.spawn, return, and unwind.

2026-06-1028

yo-project-workflow

shd101wyy/Yo

Build, test, scaffold, format, and manage Yo projects. Use this when working with yo init, build.yo, yo build, yo compile, yo test, yo fmt, yo install, yo fetch, yo version, or cross-platform Yo project setup.

2026-05-2528

name	yo-wasm-integration
description	Build Yo libraries for WebAssembly and publish as npm packages. Use this when working with WASM targets, Emscripten, WASI, npm packaging, JavaScript/TypeScript wrappers, or browser/Node.js integration.
argument-hint	[WASM task, target, or integration question]

Yo WASM Integration

Use this skill for compiling Yo projects to WebAssembly and packaging them for JavaScript/TypeScript consumption via npm.

When to use this skill

Use this skill when you need to:

compile a Yo project to WebAssembly (Emscripten or WASI)
set up an npm/ package directory with JavaScript/TypeScript wrappers
expose Yo functions to JavaScript via WASM memory and C ABI
integrate a Yo WASM module into a Node.js or browser project
debug WASM-specific compilation or runtime issues
publish a Yo-backed npm package

Workflow

Decide on target: Emscripten (browser + Node.js) or WASI (standalone/server).
Define WASM build steps in build.yo using build.executable with target: build.CompilationTarget.Wasm32_Emscripten and add_c_flags(...) for Emscripten settings.
Create a JavaScript wrapper in npm/ that loads the WASM module and exposes a clean API.
Add TypeScript declarations (index.d.ts) for type safety.
Test the WASM module from both Node.js and browser contexts.
Consult the WASM integration cheatsheet for patterns.

High-signal rules

In build.yo, use target: build.CompilationTarget.Wasm32_Emscripten for Emscripten WASM builds. Use step.add_c_flags(...) for Emscripten -s options.
For single-file compilation, use yo compile --cc emcc or yo compile --target wasm-wasi.
WASM functions communicate through linear memory — pass pointers and lengths, not Yo types.
JavaScript wrappers handle the string encoding/decoding boundary (TextEncoder/TextDecoder).
Use bitmask flags (powers of 2) to pass option sets through a single i32 parameter.
Yo's str and String types are internal — export raw *(u8) + usize pairs for WASM APIs.
Always test with --sanitize address on native first, then verify WASM behavior matches.
Emscripten exports are controlled by -sEXPORTED_FUNCTIONS and -sEXPORTED_RUNTIME_METHODS.
WASM modules can be loaded in Node.js using WebAssembly.instantiate or Emscripten's generated JS glue.
Errno values differ on WASM — use constants from std/libc/errno, never hardcode numbers.

Resource

WASM integration cheatsheet