agency-engineering-wasm-performance-engineer

Diagnoses and optimizes Rust and C++ to WebAssembly compilation and execution bottlenecks.

Updated Jul 14, 2026
One-click install
npx skills add https://github.com/AI-Staffing-Solution-Consultants-LLC/core-engineering-system --skill agency-engineering-wasm-performance-engineer-ai-staffing-solution-consultants-llc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agency-engineering-wasm-performance-engineer
Source: https://github.com/AI-Staffing-Solution-Consultants-LLC/core-engineering-system/tree/main/.agents/skills/wasm-performance-engineer
Command: npx skills add https://github.com/AI-Staffing-Solution-Consultants-LLC/core-engineering-system --skill agency-engineering-wasm-performance-engineer-ai-staffing-solution-consultants-llc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Rust and C++ code compiled to WebAssembly often suffers from slow load times, large binary sizes, and runtime execution bottlenecks that are hard to diagnose without specialized knowledge of the Wasm toolchain. ## Core Features & Use Cases - Compilation Optimization: Guides tuning of compiler flags and toolchain settings for Rust and C++ targets compiling to Wasm. - Execution Bottleneck Analysis: Identifies runtime performance issues in Wasm modules such as memory allocation patterns and JS-Wasm boundary overhead. - Use Case: A team shipping a Rust-based Wasm module in the browser notices slow startup and janky execution; use this Skill to pinpoint the compilation and runtime bottlenecks and apply targeted optimizations. ## Quick Start Analyze my Rust to WebAssembly build and identify the compilation and execution bottlenecks slowing down my module.

Frequently Asked Questions about agency-engineering-wasm-performance-engineer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I optimize Rust to WebAssembly compilation performance?▼

Optimize Rust to Wasm compilation by tuning compiler flags such as opt-level and LTO, stripping debug symbols, and reducing dependencies that inflate the binary. This Skill guides diagnosis of which compilation settings cause size and speed regressions.

How to find execution bottlenecks in WebAssembly modules?▼

Wasm execution bottlenecks typically come from frequent JS-Wasm boundary crossings, excessive memory allocation, and unoptimized hot loops. Profiling the module's runtime behavior and inspecting generated code reveals where optimization effort pays off.

Does C++ compile to WebAssembly with the same toolchain as Rust?▼

No, C++ compiles to Wasm primarily through Emscripten, while Rust uses the wasm32 target with wasm-bindgen and wasm-pack. Both produce Wasm modules but differ in runtime glue code and interop patterns.

Why is my WebAssembly binary so large after compilation?▼

Large Wasm binaries usually result from debug symbols, unused dependencies, and disabled optimizations. Enabling release-mode optimization, link-time optimization, and dead-code elimination significantly reduces output size.

When should I not use WebAssembly for performance-critical code?▼

Wasm is not ideal when workloads need direct DOM access, heavy string manipulation across the JS boundary, or SIMD features unsupported in target browsers. In those cases native code or optimized JavaScript may perform better.