Results for “emulator”

Next.js adapter for embedding emulators directly in a Next.js app via @emulators/adapter-next. Use when the user needs to embed emulators in Next.js, set up same-origin OAuth for Vercel preview deployments, create an emulate catch-all route handler, configure Auth.js/NextAuth with embedded emulators, add persistence to embedded emulators, or wrap next.config with withEmulate. Triggers include "Next.js emulator", "adapter-next", "embedded emulator", "same-origin OAuth", "Vercel preview", "createEmulateHandler", "withEmulate", or any task requiring emulators inside a Next.js app.

The English summary is being prepared. Showing the original description.

Control an Android phone or emulator through Orca using adb, the Android device connection tool. View the device live, perform touch and keyboard actions, install and launch apps, inspect interface structure, and read logs.

• Check app behavior on an Android phone or emulator
• Repeat taps, swipes, and text entry
• Install apps and check runtime permissions

Nuxt adapter for embedding emulators directly in a Nuxt app via @emulators/adapter-nuxt. Use when the user needs to embed emulators in Nuxt, set up same-origin OAuth for preview deployments, create an emulate catch-all server route, configure persistence for embedded Nuxt emulators, or wrap nuxt.config with withEmulate. Triggers include "Nuxt emulator", "adapter-nuxt", "embedded emulator", "same-origin OAuth", "createEmulateHandler", "withEmulate", or any task requiring emulators inside a Nuxt app.

The English summary is being prepared. Showing the original description.

Firebase Emulator の起動・停止・状態確認。「エミュレーター起動」「emulator start」「emulator stop」「エミュレーター停止」「エミュレーター状態」などのキーワードで自動適用。

The English summary is being prepared. Showing the original description.

Access the Firebase Emulator Suite (Firestore, Auth, Functions, Hub) via REST and Admin SDK without trial-and-error. Use this skill whenever you read/write/query/clear Firestore Emulator data, create test users or obtain ID tokens from the Auth Emulator, verify Functions triggers, seed/export emulator data, or hit unexpected 403/404 from an emulator endpoint. Consult it BEFORE curling any emulator port — it encodes the auth header and host-resolution rules that otherwise cause retries.

The English summary is being prepared. Showing the original description.

Create and integrate the machine-level core of a new EMULATORS emulator, including Computer and Emulator derivatives, memory and port maps, chip ownership and wiring, clock coordination, model configuration, commands, formatters, executables, and Visual Studio projects. Use when scaffolding a machine namespace, adding a model or regional variant, assembling existing components into a computer, or making a new emulator build and start.

The English summary is being prepared. Showing the original description.

Plan, scaffold, implement, and integrate a complete new emulated computer or console in the EMULATORS repository. Use when Codex creates a new machine, platform, hardware model, or emulator executable; decides which existing CPUs, chips, memory, I/O, video, sound, ROM, and framework classes to reuse or extend; or coordinates several emulator subsystems into a bootable tested system.

The English summary is being prepared. Showing the original description.

Control a running iOS Simulator on macOS from Orca’s live device pane. Perform taps, gestures, typing, button presses, and rotation, and inspect the interface element hierarchy to check app changes in the simulator.

• Check iOS app changes in the simulator
• Reproduce gestures and text entry
• Check the display after rotating the device

Design and implement unit, conformance, integration, timing, boot, trace, video, audio, and regression tests for EMULATORS processors, chips, peripherals, and complete machines. Use when creating a verification strategy for a new emulator, converting hardware documentation into tests, adding diagnostic programs or golden artifacts, measuring behavioral coverage, or proving that components interact correctly.

The English summary is being prepared. Showing the original description.

Parse and interpret execution debug logs generated by the EMULATORS framework, correlating each CPU instruction block with its VIC-II, CIA, SID, interrupt, stop, raster, badline, and memory-access cycles. Use for .LOG traces from EMULATORS when diagnosing cycle timing, raster effects, CPU stalls, IRQ/NMI entry, instruction/chip synchronization, or when reconstructing execution around a PC or mapped register.

The English summary is being prepared. Showing the original description.

Apply the local C++ coding conventions of the EMULATORS framework. Use when Codex adds, edits, reviews, or scaffolds C++ code in this repository, especially new classes, headers, cpp files, CORE/COMMODORE module code, emulator components, registers, chips, memory, sound, IO, commands, or InfoClass-derived objects.

The English summary is being prepared. Showing the original description.

Build and run EMULATORS locally on Windows with the repository-compatible Visual Studio configuration and SDL runtime architecture. Use whenever Codex compiles, links, tests, launches, or smoke-tests an EMULATORS executable on Windows.

The English summary is being prepared. Showing the original description.

Let an AI play Pokemon through an emulator, using screenshots and game memory to guide movement, dialogue, and battles. The skill covers browser viewing, progress tracking, and saving or resuming play with a user-provided ROM.

• Watching an AI play Pokemon in a browser
• Starting a game with a user-provided ROM
• Resuming play from a saved state

Create Appium tests that automate Android and iOS app interactions in Java, Python, or JavaScript. Configure local devices, emulators, simulators, or TestMu AI cloud devices, with guidance on element selection, waits, and gestures.

• Automate login tests for Android and iOS apps
• Create tests for local emulators and simulators
• Configure real-device tests on TestMu AI cloud

Test app interfaces on an Android emulator using ADB, a command-line device tool. Inspect element positions, perform taps and text entry, then check screenshots and React Native logs to verify behavior and investigate layout or interaction bugs.

• Verify app interfaces after UI changes
• Investigate layout and interaction bugs
• Check feature behavior through automated interactions

Create Android projects, deploy apps to devices, and manage SDK packages and emulators through the `android` command-line tool. It also supports screenshots, interface structure inspection, environment checks, and Android documentation searches.

• Creating an Android project from a template
• Deploying an APK to a device
• Managing SDK packages and emulators

Local drop-in API emulator for Vercel, GitHub, Google, Slack, Apple, Microsoft, AWS, Clerk, Linear, Twilio, and other developer APIs. Use when the user needs to start emulated services, configure seed data, write tests against local APIs, set up CI without network access, or work with the emulate CLI or programmatic API. Triggers include "start the emulator", "emulate services", "mock API locally", "create emulator config", "test against local API", "npx emulate", or any task requiring local service emulation.

The English summary is being prepared. Showing the original description.

Use this skill when controlling the AltirraSDL Atari emulator programmatically — driving the simulator from a script, capturing screenshots from a running Atari, injecting joystick/keyboard input, frame-stepping for deterministic testing, reading or writing CPU/memory/chip state, setting breakpoints or watchpoints, profiling 6502 code, loading symbols, or building automated tests against an Atari binary. Triggers on phrases like "AltirraBridge", "AltirraSDL --bridge", "AltirraBridgeServer", "Altirra Python SDK", "headless Atari emulator", "screenshot the Atari", "automate AltirraSDL", "drive the emulator from Python", "Atari debugger over a socket", "altirra_bridge package", as well as on tasks involving the bridge protocol, the Python `altirra_bridge` package, or the C `altirra_bridge.h` SDK.

The English summary is being prepared. Showing the original description.

Crear, ampliar o actualizar documentación técnica de EMULATORS en formato DOCX usando la plantilla oficial del repositorio, con portada parametrizada, índice, prólogo, capítulos de contenido, anexos, listas de ilustraciones y ecuaciones, marca de agua del autor y pie Página X | Y. Usar cuando Codex deba documentar subsistemas, arquitecturas, dispositivos, modelos, herramientas, compilación, uso, pruebas o cualquier otro aspecto del emulador y el resultado deba conservar la identidad visual de docs/UserGuide.docx.

The English summary is being prepared. Showing the original description.

Implement or extend a reusable hardware chip and its machine-specific wiring in EMULATORS, including registers, pins or logical signals, clocks, state machines, memory-mapped behavior, side effects, interrupts, DMA or bus requests, serialization, introspection, and chip tests. Use when adding a controller, timer, PIA, PPI, UART, video or sound device, custom ASIC, register bank, or a variant of an existing chip.

The English summary is being prepared. Showing the original description.

Build, audit, and modify EMULATORS runtime `.fmt` formatter files and keep them synchronized with C++ `getInfoStructure()` producers and their `.hpp` field documentation. Use when adding, renaming, or removing `InfoStructure` attributes or nested structures; diagnosing missing console fields; reviewing formatter includes, formatter names, placeholders, arrays, nested invocations, or table parameters; or changing namespace-specific `.fmt` files under `projects`.

The English summary is being prepared. Showing the original description.

Implement or extend a CPU architecture, processor variant, instruction set, addressing modes, registers, interrupts, bus transactions, disassembly, timing, and processor tests in EMULATORS. Use when adding a processor not yet emulated, deriving a CPU from F6500, FZ80, or another family, filling missing opcodes, correcting instruction semantics or cycles, or creating exhaustive instruction and interrupt tests.

The English summary is being prepared. Showing the original description.

Measure and audit C/C++ code size, namespace distribution, function complexity, nesting, recurrence, and namespace coupling in the EMULATORS framework. Use when Codex needs codebase statistics, complexity baselines, namespace comparisons, duplication indicators, hotspots, architectural growth analysis, or before/after complexity reports while excluding third-party code.

The English summary is being prepared. Showing the original description.

Implement machine input/output, I/O port decoding, external buses, host input adapters, storage and media devices, and peripherals in EMULATORS. Use when adding keyboard matrices, joysticks, controllers, cassette, cartridge, disk, printer, serial or parallel interfaces, protocol state machines, PortManager behavior, or deterministic host-to-emulated-device integration.

The English summary is being prepared. Showing the original description.