원클릭으로
mapache-n64-preview
Use the Mapache pi-n64 browser emulator preview contract for ROM artifacts.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Use the Mapache pi-n64 browser emulator preview contract for ROM artifacts.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | mapache-n64-preview |
| description | Use the Mapache pi-n64 browser emulator preview contract for ROM artifacts. |
Use this skill after building a Nintendo 64 homebrew ROM in a Mapache pi-n64 session.
Write /workspace/.mapache/preview.json to override the ROM path or emulator core:
{
"mode": "n64",
"rom": "build/custom.z64",
"core": "mupen64plus_next"
}
Accepted core values are "n64", "mupen64plus_next", and "parallel-n64". The older "parallel_n64" spelling is accepted and normalized to EmulatorJS's documented "parallel-n64" core id. Use "n64" first for broad browser compatibility; it lets EmulatorJS select the default N64 core.
The browser preview is useful for fast iteration, but it does not claim hardware accuracy. Validate serious compatibility with a modern native N64 emulator or real hardware.
QA a Mapache preview with the runner-owned browser QA command, status checks, console logs, screenshots, and structured reports.
Host an app or API behind the Mapache preview gateway.
Work from or create GitHub issues with repository context, labels, clarification, and implementation flow.
Build static web output where the Mapache preview canvas can serve it.
Run or compose Mapache browser QA tests from checked-in e2e/qa case manifests using Chrome DevTools. Use when the user explicitly asks for QA testing, smoke testing, browser testing, end-to-end testing, or a named QA case, and when issue-workflow changes frontend behavior and requires QA before PR completion.
Use when the user provides a GitHub issue number and wants Codex to complete the whole implementation workflow: update local main from remote, read the issue and comments, create an issue-named branch, implement and test the change, compose and run QA for frontend changes, commit, push, open a pull request, return to main, and comment or label the issue when blocked or waiting on user action.