無料GitHub で公開

emulators-chip-builder

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.

Commnets/EMULATORS

インストール方法を見る

含まれるファイル（3）

SKILL.md3.0 KB
agents/openai.yaml224 B
references/chip-contract.md1.2 KB

SKILL.md（原文）

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Build an EMULATORS Chip

When compiling, testing, or executing on Windows, use $emulators-windows-build-runtime.

Required Context

Read references/chip-contract.md.
Read .codex/skills/emulators-new-machine/references/workspace-artifacts.md. Store completed chip contracts and other code-generation support in the active .codex/work/ scope, never in docs/.
Inspect include/CORE/Chip.hpp, include/CORE/ChipRegisters.hpp, their implementations, and the nearest chip family.
Use $emulators-framework-cpp-style for C++ changes and $emulators-fmt-audit when InfoStructure output changes.
Use an existing chip-specific audit skill when the target or reused component matches it.

Workflow

Identify the exact chip revision, package-visible contract, clock domains, register map, reset values, side effects, interrupt outputs, and undocumented assumptions.
Compare target behavior with existing chips. Reuse only behavior supported by evidence; place board-specific wiring in a derived machine class or adapter.
Fill the chip contract before implementation. Resolve read/write asymmetry, write-one actions, read-clear behavior, open bits, mirrors, latches, and event ordering.
Implement state and register semantics before connecting the machine. Keep register objects responsible for register-visible behavior and the chip responsible for wider state progression, following the nearest framework pattern.
Implement clocked state machines with explicit transition points. Preserve subcycle ordering when it affects bus access, interrupts, audio, or pixels.
Model signals and interrupts as emulated state, not host callbacks with hidden timing.
Add focused tests for reset, every register operation, boundary transitions, interrupt acknowledgement, simultaneous events, and variant differences.
Add a small machine-wiring test after isolated chip tests pass.

Fidelity Rules

Distinguish not implemented, approximated, and verified behavior.
Avoid speculative pin-level complexity when the requested accuracy cannot observe it, but retain extension points for known future requirements.
Avoid per-cycle allocation and repeated lookup in hot paths.
Never infer register semantics from power-on values or names alone.
Do not hide board polarity, address decoding, or interrupt routing inside a generic chip.

Completion Evidence

Report the revision modeled, generic and machine-specific classes, register coverage, timing granularity, tests run, external references used, and all approximations or unknowns.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

ログインしてレビューを書く

同じリポジトリのスキル

概要と使いどころ

c64-1541-audit

無料

Validate Commodore 1540/1541/1541C/1541-II compatible disk-drive behavior in EMULATORS, including IEC serial bus protocol, device numbers, KERNAL traps, CBM DOS commands/status, D64 image parsing, BAM/directory/file chains, PETSCII filenames, 6502 drive CPU/ROM/RAM expectations, 6522 VIA wiring, GCR/track/sector geometry, motor/head timing, and compatibility boundaries for 1541-like devices. Use when Codex reviews or edits C64, VIC-20, C264, COMMODORE disk, serial I/O, D64, CBM DOS, IEC, VIA, GCR, or 1541 drive code.

日本語の概要は準備中です。原文の説明を表示しています。