{"owner":"wasmerio","repo":"wasmer","hasSkills":true,"totalSkillsCount":6,"totalTokensCount":3200,"categories":["root-instruction","copilot-instructions","claude-rule","mcp-config","marketplace","plugin-manifest"],"hasMcp":true,"mcpConfig":{"mcpServers":{"wasmer":{"command":"npx","args":["-y","@modelcontextprotocol/server-wasmer"]}}},"found":["AGENTS.md",".github/copilot-instructions.md","CLAUDE.md",".cursor/mcp.json",".claude-plugin/marketplace.json",".claude-plugin/plugin.json"],"skills":{"AGENTS.md":"# Working in this repo as an agent\n\nBefore your first edit, read `docs/CONTRIBUTING.md` and `docs/BUILD.md` in\nfull, plus the row below covering whatever you are about to touch. Skipping one\nof those docs does not exempt you from what it says.\n\nAlways read:\n\n| Read                   | For                                                    |\n| ---------------------- | ------------------------------------------------------ |\n| `docs/CONTRIBUTING.md` | PR expectations, commit format, lint gates, code style |\n| `docs/ARCHITECTURE.md` | the crate map, one place per concern, submodules       |\n| `docs/BUILD.md`        | toolchain setup, compiler backends, fast iteration     |\n| `docs/TEST.md`         | test suites, WAST spec tests, `tests/ignores.txt`      |\n| `docs/SECURITY.md`     | supported versions, how to report vulnerabilities      |\n\nRead if necessary:\n\n| If necessary        | For                            |\n| ------------------- | ------------------------------ |\n| `docs/journal.md`   | snapshot and restore internals |\n| `docs/PACKAGING.md` | distro packaging constraints   |\n| `docs/RISCV.md`     | state of RISC-V support        |\n\nTrust the repository more than any doc. `Makefile` targets and `--help`\noutput beat external docs, and docs.wasmer.io lags this repository.\n\n## Before you write code\n\nEvery new test, fixture, syscall implementation, or backend arm has a\nsibling in this repo that already does the same kind of thing. Find it and\nmatch its location, naming, and structure. If you cannot find one, say so\nbefore inventing a layout.\n\nBefore implementing a new mechanism, state the design in one or two\nsentences and get agreement. Prioritise the smallest diff that slots into\nexisting machinery. Work already done is not an argument for keeping a\nshape: if the design is wrong, say so rather than defending it.\n\n## Attribution\n\nAn agent MUST disclose that it is the one that committed its changes, and\nMUST NOT feign being a user. The human user is fully responsible for all\ncontributions.\n\n## Debugging the Runtime\n\n### Logging\n\nSet `RUST_LOG` with standard EnvFilter syntax, for example:\n\n```bash\nRUST_LOG=\"warn,wasmer_wasix=trace\" wasmer run file.wasm\n```\n\nThe `-v` to `-vvvv` flags map to warn/info/debug/trace for the targets\n`wasmer`, `wasmer_wasix`, and `virtual_fs`.\n\n`make build-wasmer-debug` builds a debug binary with tokio-console support.\n\n### Run the Workspace CLI Directly\n\n```bash\ncargo run -p wasmer-cli --features cranelift -- run file.wasm\n```\n\n### Inspect and Author Wasm\n\n- Inspect a module with `wasm-tools print file.wasm`. Pipe through `head`\n  or `grep` — the output is large.\n- Author test cases with `wasm-tools parse file.wat -o file.wasm`.\n- Reduce hard cases with `wasm-opt` and `creduce`.\n\n### Compile a C Repro to WASIX\n\n```bash\nWASIXCC_WASM_EXCEPTIONS=1 WASIXCC_PIC=1 wasixcc -g -O0 file.c -o file.wasm\n```\n\n### Debug a Failing WAST Test\n\nFind the `.wast` file under `tests/wast/`, then rerun with the\nbackend-filtered command from [docs/TEST.md](./docs/TEST.md). The runner\nprints `Running wast <path>`.\n\n## Personal execution preferences\n\nThe gitignored `AGENTS.override.md` is the user's personal addendum. When\nit exists, it overrides this file's defaults.\n",".github/copilot-instructions.md":"# GitHub Copilot Instructions\n\n## Code Writing Standards\n- Follow established code-writing standards for your language (spacing, comments, naming).\n- Consider internal coding rules for folder and function naming.\n- Follow the \"boy scout rule\": Always leave the codebase cleaner than you found it.\n\n## Comment Usage\n- Use comments sparingly and make them meaningful.\n- Avoid commenting on obvious things; use comments to explain \"why\" or unusual behavior.\n\n## Conditional Encapsulation\n- Encapsulate nested if/else statements into functions with descriptive names for clarity.\n\n## DRY Principle\n- Avoid code duplication; reuse code via functions, classes, modules, or libraries.\n- Modify code in one place if updates are needed.\n\n## Function Length & Responsibility\n- Write short, focused functions (single responsibility principle).\n- Break up long or complex functions into smaller ones.\n\n## General Code Style & Readability\n- Write readable, understandable, and maintainable code.\n- Prioritize clarity and adhere to coding standards.\n- Regularly review and refactor code for structure and maintainability.\n- Use version control (e.g., Git) for collaboration.\n\n## Naming Conventions\n- Use meaningful, descriptive names for variables, functions, and classes.\n- Names should reflect purpose and behavior; avoid names that require comments to explain intent.\n\n## Making your changes pass CI\n- Before submitting any changes\n  - Run the commands for formatting\n  - Run the linter command shown below\n  - Run tests for code you changed and everything that depends on it.\n- CI will reject code with formatting or linting issues.\n\n## Useful commands:\n- Format the code: `cargo fmt`\n- Lint and fix common mistakes: `RUSTFLAGS=\"-D dead-code -D nonstandard-style -D unused-imports -D unused-mut -D unused-variables -D unused-unsafe -D unreachable-patterns -D bad-style -D improper-ctypes -D unused-allocation -D unused-comparisons -D while-true -D unconditional-recursion -D bare-trait-objects -D function_item_references -D clippy::uninlined_format_args \" cargo clippy --all --exclude wasmer-swift --locked --fix --allow-dirty -- -D clippy::all`\n- Build the cli: `cargo build -p wasmer-cli --features cranelift,llvm,wasmer-artifact-create,static-artifact-create,wasmer-artifact-load,static-artifact-load`\n- Test the cli: `cargo test -p wasmer-cli --features cranelift,llvm,wasmer-artifact-create,static-artifact-create,wasmer-artifact-load,static-artifact-load`\n- Test WASIX: `cargo test -p wasmer-wasix --features sys`\n- Convert a wasm module to wat (always limit the output with head/grep/tail): `wasm-tools print file.wasm`\n- Convert a wat module to wasm: `wasm-tools parse file.wat -o file.wasm`\n- For really hard debugging, creduce is available\n- Optimize a wasm module and strip debug info: `wasm-opt -O3 file.wasm -o file.opt.wasm`\n- Compile a C file to a WASIX module: `WASIXCC_WASM_EXCEPTIONS=1 WASIXCC_PIC=1 wasixcc -g -O0 file.c -o file.wasm`","CLAUDE.md":"# Working in this repo as an agent\n\nBefore your first edit, read `docs/CONTRIBUTING.md` and `docs/BUILD.md` in\nfull, plus the row below covering whatever you are about to touch. Skipping one\nof those docs does not exempt you from what it says.\n\nAlways read:\n\n| Read                   | For                                                    |\n| ---------------------- | ------------------------------------------------------ |\n| `docs/CONTRIBUTING.md` | PR expectations, commit format, lint gates, code style |\n| `docs/ARCHITECTURE.md` | the crate map, one place per concern, submodules       |\n| `docs/BUILD.md`        | toolchain setup, compiler backends, fast iteration     |\n| `docs/TEST.md`         | test suites, WAST spec tests, `tests/ignores.txt`      |\n| `docs/SECURITY.md`     | supported versions, how to report vulnerabilities      |\n\nRead if necessary:\n\n| If necessary        | For                            |\n| ------------------- | ------------------------------ |\n| `docs/journal.md`   | snapshot and restore internals |\n| `docs/PACKAGING.md` | distro packaging constraints   |\n| `docs/RISCV.md`     | state of RISC-V support        |\n\nTrust the repository more than any doc. `Makefile` targets and `--help`\noutput beat external docs, and docs.wasmer.io lags this repository.\n\n## Before you write code\n\nEvery new test, fixture, syscall implementation, or backend arm has a\nsibling in this repo that already does the same kind of thing. Find it and\nmatch its location, naming, and structure. If you cannot find one, say so\nbefore inventing a layout.\n\nBefore implementing a new mechanism, state the design in one or two\nsentences and get agreement. Prioritise the smallest diff that slots into\nexisting machinery. Work already done is not an argument for keeping a\nshape: if the design is wrong, say so rather than defending it.\n\n## Attribution\n\nAn agent MUST disclose that it is the one that committed its changes, and\nMUST NOT feign being a user. The human user is fully responsible for all\ncontributions.\n\n## Debugging the Runtime\n\n### Logging\n\nSet `RUST_LOG` with standard EnvFilter syntax, for example:\n\n```bash\nRUST_LOG=\"warn,wasmer_wasix=trace\" wasmer run file.wasm\n```\n\nThe `-v` to `-vvvv` flags map to warn/info/debug/trace for the targets\n`wasmer`, `wasmer_wasix`, and `virtual_fs`.\n\n`make build-wasmer-debug` builds a debug binary with tokio-console support.\n\n### Run the Workspace CLI Directly\n\n```bash\ncargo run -p wasmer-cli --features cranelift -- run file.wasm\n```\n\n### Inspect and Author Wasm\n\n- Inspect a module with `wasm-tools print file.wasm`. Pipe through `head`\n  or `grep` — the output is large.\n- Author test cases with `wasm-tools parse file.wat -o file.wasm`.\n- Reduce hard cases with `wasm-opt` and `creduce`.\n\n### Compile a C Repro to WASIX\n\n```bash\nWASIXCC_WASM_EXCEPTIONS=1 WASIXCC_PIC=1 wasixcc -g -O0 file.c -o file.wasm\n```\n\n### Debug a Failing WAST Test\n\nFind the `.wast` file under `tests/wast/`, then rerun with the\nbackend-filtered command from [docs/TEST.md](./docs/TEST.md). The runner\nprints `Running wast <path>`.\n\n## Personal execution preferences\n\nThe gitignored `AGENTS.override.md` is the user's personal addendum. When\nit exists, it overrides this file's defaults.\n",".cursor/mcp.json":"# Model Context Protocol (MCP) Configuration\n\nPath: `.cursor/mcp.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/wasmerio/wasmer/HEAD/.cursor/mcp.json)",".claude-plugin/marketplace.json":"# Claude Plugin Marketplace Catalog\n\nPath: `.claude-plugin/marketplace.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/wasmerio/wasmer/HEAD/.claude-plugin/marketplace.json)",".claude-plugin/plugin.json":"# claude-plugin Plugin Manifest\n\nPath: `.claude-plugin/plugin.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/wasmerio/wasmer/HEAD/.claude-plugin/plugin.json)"},"files":{"AGENTS.md":"# Working in this repo as an agent\n\nBefore your first edit, read `docs/CONTRIBUTING.md` and `docs/BUILD.md` in\nfull, plus the row below covering whatever you are about to touch. Skipping one\nof those docs does not exempt you from what it says.\n\nAlways read:\n\n| Read                   | For                                                    |\n| ---------------------- | ------------------------------------------------------ |\n| `docs/CONTRIBUTING.md` | PR expectations, commit format, lint gates, code style |\n| `docs/ARCHITECTURE.md` | the crate map, one place per concern, submodules       |\n| `docs/BUILD.md`        | toolchain setup, compiler backends, fast iteration     |\n| `docs/TEST.md`         | test suites, WAST spec tests, `tests/ignores.txt`      |\n| `docs/SECURITY.md`     | supported versions, how to report vulnerabilities      |\n\nRead if necessary:\n\n| If necessary        | For                            |\n| ------------------- | ------------------------------ |\n| `docs/journal.md`   | snapshot and restore internals |\n| `docs/PACKAGING.md` | distro packaging constraints   |\n| `docs/RISCV.md`     | state of RISC-V support        |\n\nTrust the repository more than any doc. `Makefile` targets and `--help`\noutput beat external docs, and docs.wasmer.io lags this repository.\n\n## Before you write code\n\nEvery new test, fixture, syscall implementation, or backend arm has a\nsibling in this repo that already does the same kind of thing. Find it and\nmatch its location, naming, and structure. If you cannot find one, say so\nbefore inventing a layout.\n\nBefore implementing a new mechanism, state the design in one or two\nsentences and get agreement. Prioritise the smallest diff that slots into\nexisting machinery. Work already done is not an argument for keeping a\nshape: if the design is wrong, say so rather than defending it.\n\n## Attribution\n\nAn agent MUST disclose that it is the one that committed its changes, and\nMUST NOT feign being a user. The human user is fully responsible for all\ncontributions.\n\n## Debugging the Runtime\n\n### Logging\n\nSet `RUST_LOG` with standard EnvFilter syntax, for example:\n\n```bash\nRUST_LOG=\"warn,wasmer_wasix=trace\" wasmer run file.wasm\n```\n\nThe `-v` to `-vvvv` flags map to warn/info/debug/trace for the targets\n`wasmer`, `wasmer_wasix`, and `virtual_fs`.\n\n`make build-wasmer-debug` builds a debug binary with tokio-console support.\n\n### Run the Workspace CLI Directly\n\n```bash\ncargo run -p wasmer-cli --features cranelift -- run file.wasm\n```\n\n### Inspect and Author Wasm\n\n- Inspect a module with `wasm-tools print file.wasm`. Pipe through `head`\n  or `grep` — the output is large.\n- Author test cases with `wasm-tools parse file.wat -o file.wasm`.\n- Reduce hard cases with `wasm-opt` and `creduce`.\n\n### Compile a C Repro to WASIX\n\n```bash\nWASIXCC_WASM_EXCEPTIONS=1 WASIXCC_PIC=1 wasixcc -g -O0 file.c -o file.wasm\n```\n\n### Debug a Failing WAST Test\n\nFind the `.wast` file under `tests/wast/`, then rerun with the\nbackend-filtered command from [docs/TEST.md](./docs/TEST.md). The runner\nprints `Running wast <path>`.\n\n## Personal execution preferences\n\nThe gitignored `AGENTS.override.md` is the user's personal addendum. When\nit exists, it overrides this file's defaults.\n",".github/copilot-instructions.md":"# GitHub Copilot Instructions\n\n## Code Writing Standards\n- Follow established code-writing standards for your language (spacing, comments, naming).\n- Consider internal coding rules for folder and function naming.\n- Follow the \"boy scout rule\": Always leave the codebase cleaner than you found it.\n\n## Comment Usage\n- Use comments sparingly and make them meaningful.\n- Avoid commenting on obvious things; use comments to explain \"why\" or unusual behavior.\n\n## Conditional Encapsulation\n- Encapsulate nested if/else statements into functions with descriptive names for clarity.\n\n## DRY Principle\n- Avoid code duplication; reuse code via functions, classes, modules, or libraries.\n- Modify code in one place if updates are needed.\n\n## Function Length & Responsibility\n- Write short, focused functions (single responsibility principle).\n- Break up long or complex functions into smaller ones.\n\n## General Code Style & Readability\n- Write readable, understandable, and maintainable code.\n- Prioritize clarity and adhere to coding standards.\n- Regularly review and refactor code for structure and maintainability.\n- Use version control (e.g., Git) for collaboration.\n\n## Naming Conventions\n- Use meaningful, descriptive names for variables, functions, and classes.\n- Names should reflect purpose and behavior; avoid names that require comments to explain intent.\n\n## Making your changes pass CI\n- Before submitting any changes\n  - Run the commands for formatting\n  - Run the linter command shown below\n  - Run tests for code you changed and everything that depends on it.\n- CI will reject code with formatting or linting issues.\n\n## Useful commands:\n- Format the code: `cargo fmt`\n- Lint and fix common mistakes: `RUSTFLAGS=\"-D dead-code -D nonstandard-style -D unused-imports -D unused-mut -D unused-variables -D unused-unsafe -D unreachable-patterns -D bad-style -D improper-ctypes -D unused-allocation -D unused-comparisons -D while-true -D unconditional-recursion -D bare-trait-objects -D function_item_references -D clippy::uninlined_format_args \" cargo clippy --all --exclude wasmer-swift --locked --fix --allow-dirty -- -D clippy::all`\n- Build the cli: `cargo build -p wasmer-cli --features cranelift,llvm,wasmer-artifact-create,static-artifact-create,wasmer-artifact-load,static-artifact-load`\n- Test the cli: `cargo test -p wasmer-cli --features cranelift,llvm,wasmer-artifact-create,static-artifact-create,wasmer-artifact-load,static-artifact-load`\n- Test WASIX: `cargo test -p wasmer-wasix --features sys`\n- Convert a wasm module to wat (always limit the output with head/grep/tail): `wasm-tools print file.wasm`\n- Convert a wat module to wasm: `wasm-tools parse file.wat -o file.wasm`\n- For really hard debugging, creduce is available\n- Optimize a wasm module and strip debug info: `wasm-opt -O3 file.wasm -o file.opt.wasm`\n- Compile a C file to a WASIX module: `WASIXCC_WASM_EXCEPTIONS=1 WASIXCC_PIC=1 wasixcc -g -O0 file.c -o file.wasm`","CLAUDE.md":"# Working in this repo as an agent\n\nBefore your first edit, read `docs/CONTRIBUTING.md` and `docs/BUILD.md` in\nfull, plus the row below covering whatever you are about to touch. Skipping one\nof those docs does not exempt you from what it says.\n\nAlways read:\n\n| Read                   | For                                                    |\n| ---------------------- | ------------------------------------------------------ |\n| `docs/CONTRIBUTING.md` | PR expectations, commit format, lint gates, code style |\n| `docs/ARCHITECTURE.md` | the crate map, one place per concern, submodules       |\n| `docs/BUILD.md`        | toolchain setup, compiler backends, fast iteration     |\n| `docs/TEST.md`         | test suites, WAST spec tests, `tests/ignores.txt`      |\n| `docs/SECURITY.md`     | supported versions, how to report vulnerabilities      |\n\nRead if necessary:\n\n| If necessary        | For                            |\n| ------------------- | ------------------------------ |\n| `docs/journal.md`   | snapshot and restore internals |\n| `docs/PACKAGING.md` | distro packaging constraints   |\n| `docs/RISCV.md`     | state of RISC-V support        |\n\nTrust the repository more than any doc. `Makefile` targets and `--help`\noutput beat external docs, and docs.wasmer.io lags this repository.\n\n## Before you write code\n\nEvery new test, fixture, syscall implementation, or backend arm has a\nsibling in this repo that already does the same kind of thing. Find it and\nmatch its location, naming, and structure. If you cannot find one, say so\nbefore inventing a layout.\n\nBefore implementing a new mechanism, state the design in one or two\nsentences and get agreement. Prioritise the smallest diff that slots into\nexisting machinery. Work already done is not an argument for keeping a\nshape: if the design is wrong, say so rather than defending it.\n\n## Attribution\n\nAn agent MUST disclose that it is the one that committed its changes, and\nMUST NOT feign being a user. The human user is fully responsible for all\ncontributions.\n\n## Debugging the Runtime\n\n### Logging\n\nSet `RUST_LOG` with standard EnvFilter syntax, for example:\n\n```bash\nRUST_LOG=\"warn,wasmer_wasix=trace\" wasmer run file.wasm\n```\n\nThe `-v` to `-vvvv` flags map to warn/info/debug/trace for the targets\n`wasmer`, `wasmer_wasix`, and `virtual_fs`.\n\n`make build-wasmer-debug` builds a debug binary with tokio-console support.\n\n### Run the Workspace CLI Directly\n\n```bash\ncargo run -p wasmer-cli --features cranelift -- run file.wasm\n```\n\n### Inspect and Author Wasm\n\n- Inspect a module with `wasm-tools print file.wasm`. Pipe through `head`\n  or `grep` — the output is large.\n- Author test cases with `wasm-tools parse file.wat -o file.wasm`.\n- Reduce hard cases with `wasm-opt` and `creduce`.\n\n### Compile a C Repro to WASIX\n\n```bash\nWASIXCC_WASM_EXCEPTIONS=1 WASIXCC_PIC=1 wasixcc -g -O0 file.c -o file.wasm\n```\n\n### Debug a Failing WAST Test\n\nFind the `.wast` file under `tests/wast/`, then rerun with the\nbackend-filtered command from [docs/TEST.md](./docs/TEST.md). The runner\nprints `Running wast <path>`.\n\n## Personal execution preferences\n\nThe gitignored `AGENTS.override.md` is the user's personal addendum. When\nit exists, it overrides this file's defaults.\n",".cursor/mcp.json":"# Model Context Protocol (MCP) Configuration\n\nPath: `.cursor/mcp.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/wasmerio/wasmer/HEAD/.cursor/mcp.json)",".claude-plugin/marketplace.json":"# Claude Plugin Marketplace Catalog\n\nPath: `.claude-plugin/marketplace.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/wasmerio/wasmer/HEAD/.claude-plugin/marketplace.json)",".claude-plugin/plugin.json":"# claude-plugin Plugin Manifest\n\nPath: `.claude-plugin/plugin.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/wasmerio/wasmer/HEAD/.claude-plugin/plugin.json)"},"items":[{"name":"AGENTS.md","path":"AGENTS.md","rawUrl":"https://raw.githubusercontent.com/wasmerio/wasmer/HEAD/AGENTS.md","title":"AI Agent Protocol & Instructions","category":"root-instruction","format":"markdown","content":"# Working in this repo as an agent\n\nBefore your first edit, read `docs/CONTRIBUTING.md` and `docs/BUILD.md` in\nfull, plus the row below covering whatever you are about to touch. Skipping one\nof those docs does not exempt you from what it says.\n\nAlways read:\n\n| Read                   | For                                                    |\n| ---------------------- | ------------------------------------------------------ |\n| `docs/CONTRIBUTING.md` | PR expectations, commit format, lint gates, code style |\n| `docs/ARCHITECTURE.md` | the crate map, one place per concern, submodules       |\n| `docs/BUILD.md`        | toolchain setup, compiler backends, fast iteration     |\n| `docs/TEST.md`         | test suites, WAST spec tests, `tests/ignores.txt`      |\n| `docs/SECURITY.md`     | supported versions, how to report vulnerabilities      |\n\nRead if necessary:\n\n| If necessary        | For                            |\n| ------------------- | ------------------------------ |\n| `docs/journal.md`   | snapshot and restore internals |\n| `docs/PACKAGING.md` | distro packaging constraints   |\n| `docs/RISCV.md`     | state of RISC-V support        |\n\nTrust the repository more than any doc. `Makefile` targets and `--help`\noutput beat external docs, and docs.wasmer.io lags this repository.\n\n## Before you write code\n\nEvery new test, fixture, syscall implementation, or backend arm has a\nsibling in this repo that already does the same kind of thing. Find it and\nmatch its location, naming, and structure. If you cannot find one, say so\nbefore inventing a layout.\n\nBefore implementing a new mechanism, state the design in one or two\nsentences and get agreement. Prioritise the smallest diff that slots into\nexisting machinery. Work already done is not an argument for keeping a\nshape: if the design is wrong, say so rather than defending it.\n\n## Attribution\n\nAn agent MUST disclose that it is the one that committed its changes, and\nMUST NOT feign being a user. The human user is fully responsible for all\ncontributions.\n\n## Debugging the Runtime\n\n### Logging\n\nSet `RUST_LOG` with standard EnvFilter syntax, for example:\n\n```bash\nRUST_LOG=\"warn,wasmer_wasix=trace\" wasmer run file.wasm\n```\n\nThe `-v` to `-vvvv` flags map to warn/info/debug/trace for the targets\n`wasmer`, `wasmer_wasix`, and `virtual_fs`.\n\n`make build-wasmer-debug` builds a debug binary with tokio-console support.\n\n### Run the Workspace CLI Directly\n\n```bash\ncargo run -p wasmer-cli --features cranelift -- run file.wasm\n```\n\n### Inspect and Author Wasm\n\n- Inspect a module with `wasm-tools print file.wasm`. Pipe through `head`\n  or `grep` — the output is large.\n- Author test cases with `wasm-tools parse file.wat -o file.wasm`.\n- Reduce hard cases with `wasm-opt` and `creduce`.\n\n### Compile a C Repro to WASIX\n\n```bash\nWASIXCC_WASM_EXCEPTIONS=1 WASIXCC_PIC=1 wasixcc -g -O0 file.c -o file.wasm\n```\n\n### Debug a Failing WAST Test\n\nFind the `.wast` file under `tests/wast/`, then rerun with the\nbackend-filtered command from [docs/TEST.md](./docs/TEST.md). The runner\nprints `Running wast <path>`.\n\n## Personal execution preferences\n\nThe gitignored `AGENTS.override.md` is the user's personal addendum. When\nit exists, it overrides this file's defaults.\n","isInternal":false,"tokens":800,"sizeBytes":3230},{"name":"CLAUDE.md","path":"CLAUDE.md","rawUrl":"https://raw.githubusercontent.com/wasmerio/wasmer/HEAD/CLAUDE.md","title":"Claude Agent Guidelines & System Prompt","category":"claude-rule","format":"markdown","content":"# Working in this repo as an agent\n\nBefore your first edit, read `docs/CONTRIBUTING.md` and `docs/BUILD.md` in\nfull, plus the row below covering whatever you are about to touch. Skipping one\nof those docs does not exempt you from what it says.\n\nAlways read:\n\n| Read                   | For                                                    |\n| ---------------------- | ------------------------------------------------------ |\n| `docs/CONTRIBUTING.md` | PR expectations, commit format, lint gates, code style |\n| `docs/ARCHITECTURE.md` | the crate map, one place per concern, submodules       |\n| `docs/BUILD.md`        | toolchain setup, compiler backends, fast iteration     |\n| `docs/TEST.md`         | test suites, WAST spec tests, `tests/ignores.txt`      |\n| `docs/SECURITY.md`     | supported versions, how to report vulnerabilities      |\n\nRead if necessary:\n\n| If necessary        | For                            |\n| ------------------- | ------------------------------ |\n| `docs/journal.md`   | snapshot and restore internals |\n| `docs/PACKAGING.md` | distro packaging constraints   |\n| `docs/RISCV.md`     | state of RISC-V support        |\n\nTrust the repository more than any doc. `Makefile` targets and `--help`\noutput beat external docs, and docs.wasmer.io lags this repository.\n\n## Before you write code\n\nEvery new test, fixture, syscall implementation, or backend arm has a\nsibling in this repo that already does the same kind of thing. Find it and\nmatch its location, naming, and structure. If you cannot find one, say so\nbefore inventing a layout.\n\nBefore implementing a new mechanism, state the design in one or two\nsentences and get agreement. Prioritise the smallest diff that slots into\nexisting machinery. Work already done is not an argument for keeping a\nshape: if the design is wrong, say so rather than defending it.\n\n## Attribution\n\nAn agent MUST disclose that it is the one that committed its changes, and\nMUST NOT feign being a user. The human user is fully responsible for all\ncontributions.\n\n## Debugging the Runtime\n\n### Logging\n\nSet `RUST_LOG` with standard EnvFilter syntax, for example:\n\n```bash\nRUST_LOG=\"warn,wasmer_wasix=trace\" wasmer run file.wasm\n```\n\nThe `-v` to `-vvvv` flags map to warn/info/debug/trace for the targets\n`wasmer`, `wasmer_wasix`, and `virtual_fs`.\n\n`make build-wasmer-debug` builds a debug binary with tokio-console support.\n\n### Run the Workspace CLI Directly\n\n```bash\ncargo run -p wasmer-cli --features cranelift -- run file.wasm\n```\n\n### Inspect and Author Wasm\n\n- Inspect a module with `wasm-tools print file.wasm`. Pipe through `head`\n  or `grep` — the output is large.\n- Author test cases with `wasm-tools parse file.wat -o file.wasm`.\n- Reduce hard cases with `wasm-opt` and `creduce`.\n\n### Compile a C Repro to WASIX\n\n```bash\nWASIXCC_WASM_EXCEPTIONS=1 WASIXCC_PIC=1 wasixcc -g -O0 file.c -o file.wasm\n```\n\n### Debug a Failing WAST Test\n\nFind the `.wast` file under `tests/wast/`, then rerun with the\nbackend-filtered command from [docs/TEST.md](./docs/TEST.md). The runner\nprints `Running wast <path>`.\n\n## Personal execution preferences\n\nThe gitignored `AGENTS.override.md` is the user's personal addendum. When\nit exists, it overrides this file's defaults.\n","isInternal":false,"tokens":800,"sizeBytes":3230},{"name":"copilot-instructions.md","path":".github/copilot-instructions.md","rawUrl":"https://raw.githubusercontent.com/wasmerio/wasmer/HEAD/.github/copilot-instructions.md","title":"GitHub Copilot Instructions","category":"copilot-instructions","format":"markdown","content":"# GitHub Copilot Instructions\n\n## Code Writing Standards\n- Follow established code-writing standards for your language (spacing, comments, naming).\n- Consider internal coding rules for folder and function naming.\n- Follow the \"boy scout rule\": Always leave the codebase cleaner than you found it.\n\n## Comment Usage\n- Use comments sparingly and make them meaningful.\n- Avoid commenting on obvious things; use comments to explain \"why\" or unusual behavior.\n\n## Conditional Encapsulation\n- Encapsulate nested if/else statements into functions with descriptive names for clarity.\n\n## DRY Principle\n- Avoid code duplication; reuse code via functions, classes, modules, or libraries.\n- Modify code in one place if updates are needed.\n\n## Function Length & Responsibility\n- Write short, focused functions (single responsibility principle).\n- Break up long or complex functions into smaller ones.\n\n## General Code Style & Readability\n- Write readable, understandable, and maintainable code.\n- Prioritize clarity and adhere to coding standards.\n- Regularly review and refactor code for structure and maintainability.\n- Use version control (e.g., Git) for collaboration.\n\n## Naming Conventions\n- Use meaningful, descriptive names for variables, functions, and classes.\n- Names should reflect purpose and behavior; avoid names that require comments to explain intent.\n\n## Making your changes pass CI\n- Before submitting any changes\n  - Run the commands for formatting\n  - Run the linter command shown below\n  - Run tests for code you changed and everything that depends on it.\n- CI will reject code with formatting or linting issues.\n\n## Useful commands:\n- Format the code: `cargo fmt`\n- Lint and fix common mistakes: `RUSTFLAGS=\"-D dead-code -D nonstandard-style -D unused-imports -D unused-mut -D unused-variables -D unused-unsafe -D unreachable-patterns -D bad-style -D improper-ctypes -D unused-allocation -D unused-comparisons -D while-true -D unconditional-recursion -D bare-trait-objects -D function_item_references -D clippy::uninlined_format_args \" cargo clippy --all --exclude wasmer-swift --locked --fix --allow-dirty -- -D clippy::all`\n- Build the cli: `cargo build -p wasmer-cli --features cranelift,llvm,wasmer-artifact-create,static-artifact-create,wasmer-artifact-load,static-artifact-load`\n- Test the cli: `cargo test -p wasmer-cli --features cranelift,llvm,wasmer-artifact-create,static-artifact-create,wasmer-artifact-load,static-artifact-load`\n- Test WASIX: `cargo test -p wasmer-wasix --features sys`\n- Convert a wasm module to wat (always limit the output with head/grep/tail): `wasm-tools print file.wasm`\n- Convert a wat module to wasm: `wasm-tools parse file.wat -o file.wasm`\n- For really hard debugging, creduce is available\n- Optimize a wasm module and strip debug info: `wasm-opt -O3 file.wasm -o file.opt.wasm`\n- Compile a C file to a WASIX module: `WASIXCC_WASM_EXCEPTIONS=1 WASIXCC_PIC=1 wasixcc -g -O0 file.c -o file.wasm`","isInternal":false,"tokens":700,"sizeBytes":2944},{"name":"marketplace.json","path":".claude-plugin/marketplace.json","rawUrl":"https://raw.githubusercontent.com/wasmerio/wasmer/HEAD/.claude-plugin/marketplace.json","title":"Claude Plugin Marketplace Catalog","category":"marketplace","format":"json","content":"# Claude Plugin Marketplace Catalog\n\nPath: `.claude-plugin/marketplace.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/wasmerio/wasmer/HEAD/.claude-plugin/marketplace.json)","tokens":300,"sizeBytes":194},{"name":"plugin.json","path":".claude-plugin/plugin.json","rawUrl":"https://raw.githubusercontent.com/wasmerio/wasmer/HEAD/.claude-plugin/plugin.json","title":"claude-plugin Plugin Manifest","category":"plugin-manifest","format":"json","content":"# claude-plugin Plugin Manifest\n\nPath: `.claude-plugin/plugin.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/wasmerio/wasmer/HEAD/.claude-plugin/plugin.json)","tokens":300,"sizeBytes":180},{"name":"mcp.json","path":".cursor/mcp.json","rawUrl":"https://raw.githubusercontent.com/wasmerio/wasmer/HEAD/.cursor/mcp.json","title":"Model Context Protocol (MCP) Configuration","category":"mcp-config","format":"json","content":"# Model Context Protocol (MCP) Configuration\n\nPath: `.cursor/mcp.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/wasmerio/wasmer/HEAD/.cursor/mcp.json)","tokens":300,"sizeBytes":173}],"systemPromptSnippet":"<yakaai_skills repo=\"wasmerio/wasmer\">\n<!-- File: AGENTS.md (Tokens: ~800 | Category: root-instruction) -->\n# Working in this repo as an agent\n\nBefore your first edit, read `docs/CONTRIBUTING.md` and `docs/BUILD.md` in\nfull, plus the row below covering whatever you are about to touch. Skipping one\nof those docs does not exempt you from what it says.\n\nAlways read:\n\n| Read                   | For                                                    |\n| ---------------------- | ------------------------------------------------------ |\n| `docs/CONTRIBUTING.md` | PR expectations, commit format, lint gates, code style |\n| `docs/ARCHITECTURE.md` | the crate map, one place per concern, submodules       |\n| `docs/BUILD.md`        | toolchain setup, compiler backends, fast iteration     |\n| `docs/TEST.md`         | test suites, WAST spec tests, `tests/ignores.txt`      |\n| `docs/SECURITY.md`     | supported versions, how to report vulnerabilities      |\n\nRead if necessary:\n\n| If necessary        | For                            |\n| ------------------- | ------------------------------ |\n| `docs/journal.md`   | snapshot and restore internals |\n| `docs/PACKAGING.md` | distro packaging constraints   |\n| `docs/RISCV.md`     | state of RISC-V support        |\n\nTrust the repository more than any doc. `Makefile` targets and `--help`\noutput beat external docs, and docs.wasmer.io lags this repository.\n\n## Before you write code\n\nEvery new test, fixture, syscall implementation, or backend arm has a\nsibling in this repo that already does the same kind of thing. Find it and\nmatch its location, naming, and structure. If you cannot find one, say so\nbefore inventing a layout.\n\nBefore implementing a new mechanism, state the design in one or two\nsentences and get agreement. Prioritise the smallest diff that slots into\nexisting machinery. Work already done is not an argument for keeping a\nshape: if the design is wrong, say so rather than defending it.\n\n## Attribution\n\nAn agent MUST disclose that it is the one that committed its changes, and\nMUST NOT feign being a user. The human user is fully responsible for all\ncontributions.\n\n## Debugging the Runtime\n\n### Logging\n\nSet `RUST_LOG` with standard EnvFilter syntax, for example:\n\n```bash\nRUST_LOG=\"warn,wasmer_wasix=trace\" wasmer run file.wasm\n```\n\nThe `-v` to `-vvvv` flags map to warn/info/debug/trace for the targets\n`wasmer`, `wasmer_wasix`, and `virtual_fs`.\n\n`make build-wasmer-debug` builds a debug binary with tokio-console support.\n\n### Run the Workspace CLI Directly\n\n```bash\ncargo run -p wasmer-cli --features cranelift -- run file.wasm\n```\n\n### Inspect and Author Wasm\n\n- Inspect a module with `wasm-tools print file.wasm`. Pipe through `head`\n  or `grep` — the output is large.\n- Author test cases with `wasm-tools parse file.wat -o file.wasm`.\n- Reduce hard cases with `wasm-opt` and `creduce`.\n\n### Compile a C Repro to WASIX\n\n```bash\nWASIXCC_WASM_EXCEPTIONS=1 WASIXCC_PIC=1 wasixcc -g -O0 file.c -o file.wasm\n```\n\n### Debug a Failing WAST Test\n\nFind the `.wast` file under `tests/wast/`, then rerun with the\nbackend-filtered command from [docs/TEST.md](./docs/TEST.md). The runner\nprints `Running wast <path>`.\n\n## Personal execution preferences\n\nThe gitignored `AGENTS.override.md` is the user's personal addendum. When\nit exists, it overrides this file's defaults.\n\n<!-- File: CLAUDE.md (Tokens: ~800 | Category: claude-rule) -->\n# Working in this repo as an agent\n\nBefore your first edit, read `docs/CONTRIBUTING.md` and `docs/BUILD.md` in\nfull, plus the row below covering whatever you are about to touch. Skipping one\nof those docs does not exempt you from what it says.\n\nAlways read:\n\n| Read                   | For                                                    |\n| ---------------------- | ------------------------------------------------------ |\n| `docs/CONTRIBUTING.md` | PR expectations, commit format, lint gates, code style |\n| `docs/ARCHITECTURE.md` | the crate map, one place per concern, submodules       |\n| `docs/BUILD.md`        | toolchain setup, compiler backends, fast iteration     |\n| `docs/TEST.md`         | test suites, WAST spec tests, `tests/ignores.txt`      |\n| `docs/SECURITY.md`     | supported versions, how to report vulnerabilities      |\n\nRead if necessary:\n\n| If necessary        | For                            |\n| ------------------- | ------------------------------ |\n| `docs/journal.md`   | snapshot and restore internals |\n| `docs/PACKAGING.md` | distro packaging constraints   |\n| `docs/RISCV.md`     | state of RISC-V support        |\n\nTrust the repository more than any doc. `Makefile` targets and `--help`\noutput beat external docs, and docs.wasmer.io lags this repository.\n\n## Before you write code\n\nEvery new test, fixture, syscall implementation, or backend arm has a\nsibling in this repo that already does the same kind of thing. Find it and\nmatch its location, naming, and structure. If you cannot find one, say so\nbefore inventing a layout.\n\nBefore implementing a new mechanism, state the design in one or two\nsentences and get agreement. Prioritise the smallest diff that slots into\nexisting machinery. Work already done is not an argument for keeping a\nshape: if the design is wrong, say so rather than defending it.\n\n## Attribution\n\nAn agent MUST disclose that it is the one that committed its changes, and\nMUST NOT feign being a user. The human user is fully responsible for all\ncontributions.\n\n## Debugging the Runtime\n\n### Logging\n\nSet `RUST_LOG` with standard EnvFilter syntax, for example:\n\n```bash\nRUST_LOG=\"warn,wasmer_wasix=trace\" wasmer run file.wasm\n```\n\nThe `-v` to `-vvvv` flags map to warn/info/debug/trace for the targets\n`wasmer`, `wasmer_wasix`, and `virtual_fs`.\n\n`make build-wasmer-debug` builds a debug binary with tokio-console support.\n\n### Run the Workspace CLI Directly\n\n```bash\ncargo run -p wasmer-cli --features cranelift -- run file.wasm\n```\n\n### Inspect and Author Wasm\n\n- Inspect a module with `wasm-tools print file.wasm`. Pipe through `head`\n  or `grep` — the output is large.\n- Author test cases with `wasm-tools parse file.wat -o file.wasm`.\n- Reduce hard cases with `wasm-opt` and `creduce`.\n\n### Compile a C Repro to WASIX\n\n```bash\nWASIXCC_WASM_EXCEPTIONS=1 WASIXCC_PIC=1 wasixcc -g -O0 file.c -o file.wasm\n```\n\n### Debug a Failing WAST Test\n\nFind the `.wast` file under `tests/wast/`, then rerun with the\nbackend-filtered command from [docs/TEST.md](./docs/TEST.md). The runner\nprints `Running wast <path>`.\n\n## Personal execution preferences\n\nThe gitignored `AGENTS.override.md` is the user's personal addendum. When\nit exists, it overrides this file's defaults.\n\n<!-- File: .github/copilot-instructions.md (Tokens: ~700 | Category: copilot-instructions) -->\n# GitHub Copilot Instructions\n\n## Code Writing Standards\n- Follow established code-writing standards for your language (spacing, comments, naming).\n- Consider internal coding rules for folder and function naming.\n- Follow the \"boy scout rule\": Always leave the codebase cleaner than you found it.\n\n## Comment Usage\n- Use comments sparingly and make them meaningful.\n- Avoid commenting on obvious things; use comments to explain \"why\" or unusual behavior.\n\n## Conditional Encapsulation\n- Encapsulate nested if/else statements into functions with descriptive names for clarity.\n\n## DRY Principle\n- Avoid code duplication; reuse code via functions, classes, modules, or libraries.\n- Modify code in one place if updates are needed.\n\n## Function Length & Responsibility\n- Write short, focused functions (single responsibility principle).\n- Break up long or complex functions into smaller ones.\n\n## General Code Style & Readability\n- Write readable, understandable, and maintainable code.\n- Prioritize clarity and adhere to coding standards.\n- Regularly review and refactor code for structure and maintainability.\n- Use version control (e.g., Git) for collaboration.\n\n## Naming Conventions\n- Use meaningful, descriptive names for variables, functions, and classes.\n- Names should reflect purpose and behavior; avoid names that require comments to explain intent.\n\n## Making your changes pass CI\n- Before submitting any changes\n  - Run the commands for formatting\n  - Run the linter command shown below\n  - Run tests for code you changed and everything that depends on it.\n- CI will reject code with formatting or linting issues.\n\n## Useful commands:\n- Format the code: `cargo fmt`\n- Lint and fix common mistakes: `RUSTFLAGS=\"-D dead-code -D nonstandard-style -D unused-imports -D unused-mut -D unused-variables -D unused-unsafe -D unreachable-patterns -D bad-style -D improper-ctypes -D unused-allocation -D unused-comparisons -D while-true -D unconditional-recursion -D bare-trait-objects -D function_item_references -D clippy::uninlined_format_args \" cargo clippy --all --exclude wasmer-swift --locked --fix --allow-dirty -- -D clippy::all`\n- Build the cli: `cargo build -p wasmer-cli --features cranelift,llvm,wasmer-artifact-create,static-artifact-create,wasmer-artifact-load,static-artifact-load`\n- Test the cli: `cargo test -p wasmer-cli --features cranelift,llvm,wasmer-artifact-create,static-artifact-create,wasmer-artifact-load,static-artifact-load`\n- Test WASIX: `cargo test -p wasmer-wasix --features sys`\n- Convert a wasm module to wat (always limit the output with head/grep/tail): `wasm-tools print file.wasm`\n- Convert a wat module to wasm: `wasm-tools parse file.wat -o file.wasm`\n- For really hard debugging, creduce is available\n- Optimize a wasm module and strip debug info: `wasm-opt -O3 file.wasm -o file.opt.wasm`\n- Compile a C file to a WASIX module: `WASIXCC_WASM_EXCEPTIONS=1 WASIXCC_PIC=1 wasixcc -g -O0 file.c -o file.wasm`\n\n<!-- File: .claude-plugin/marketplace.json (Tokens: ~300 | Category: marketplace) -->\n# Claude Plugin Marketplace Catalog\n\nPath: `.claude-plugin/marketplace.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/wasmerio/wasmer/HEAD/.claude-plugin/marketplace.json)\n\n<!-- File: .claude-plugin/plugin.json (Tokens: ~300 | Category: plugin-manifest) -->\n# claude-plugin Plugin Manifest\n\nPath: `.claude-plugin/plugin.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/wasmerio/wasmer/HEAD/.claude-plugin/plugin.json)\n\n<!-- File: .cursor/mcp.json (Tokens: ~300 | Category: mcp-config) -->\n# Model Context Protocol (MCP) Configuration\n\nPath: `.cursor/mcp.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/wasmerio/wasmer/HEAD/.cursor/mcp.json)\n</yakaai_skills>"}