免费在 GitHub 公开

emulators-cpu-builder

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.

中文简介正在准备中。当前显示原文说明。

Commnets/EMULATORS

查看安装方法

包含的文件（3）

SKILL.md3.2 KB
agents/openai.yaml218 B
references/processor-workbook.md1.8 KB

SKILL.md（原文）

安装前可以查看交给 AI 代理的指令内容。

Build an EMULATORS CPU

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

Required Context

Read references/processor-workbook.md before designing instructions or tests.
Read .codex/skills/emulators-new-machine/references/workspace-artifacts.md. Store the completed processor workbook and other code-generation support in the active .codex/work/ scope, never in docs/.
Inspect include/CORE/CPU*, include/CORE/Instruction.hpp, their implementations, and the closest CPU family under include/ and src/.
Inspect TestCPU, Test6500, TestZ80, TestInst6500, or TestInstZ80 patterns when relevant.
Use $emulators-framework-cpp-style for all C++ work.

Workflow

Establish authoritative manuals, exact processor revision, clock/bus contract, reset state, interrupt modes, and treatment of undocumented behavior.
Compare the target with existing CPU families at register, opcode, addressing, bus, interrupt, and timing levels. Choose independently among reuse, configuration, derivation, adapter, and new implementation.
Complete the processor workbook before bulk-generating instruction classes. Give every opcode a deliberate status: implemented, alias, undocumented, illegal, model-specific, or unsupported.
Implement architecture and registers first, then reset and interrupts, addressing primitives, instruction families, decode/disassembly, transactions, and timing.
Preserve observable bus ordering and conditional cycles. Treat correct final registers with incorrect accesses or timing as a failure whenever the accuracy target exposes them.
Separate invariant family behavior from variant-specific behavior. Do not put machine wiring into a reusable CPU namespace.
Add tests alongside each instruction family. Build expected results from the specification, not from the implementation under test.
Add boundary and interaction tests after opcode coverage: page/address wrapping, stack limits, interrupt entry/return, reset, wait/halt states, prefix decoding, illegal instructions, self-modifying code, and overlapping bus requests as applicable.
Compile and run the narrowest processor tests, then at least one machine-level smoke test when integration exists.

Instruction Acceptance

For every supported opcode verify decode length and operands, state and flag results, address rules, ordered bus accesses, base and conditional cycles, interrupt boundaries, disassembly, and supported variant differences.

Completion Evidence

Report opcode and variant coverage, commands run, failing or unavailable external vectors, timing granularity achieved, undocumented behavior policy, and remaining gaps. Do not describe a processor as complete while opcodes or interrupt states remain implicitly unclassified.

评价

还没有评价。欢迎分享你的使用感受。

无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

同一仓库的技能

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.

中文简介正在准备中。当前显示原文说明。