Agent Skills › akeit0/okojo › okojo-engine-development

okojo-engine-development

GitHub

用于开发或调试 Okojo ECMAScript 引擎内部实现，涵盖解析器、编译器、字节码、虚拟机及内置对象模型。指导最小化变更与性能优化工作流。

.agents/skills/okojo-engine-development/SKILL.md akeit0/okojo

Trigger Scenarios

Okojo 引擎核心功能开发引擎相关 Bug 调试编译器或 VM 性能优化

Install

npx skills add akeit0/okojo --skill okojo-engine-development -g -y

More Options

Non-standard path

npx skills add https://github.com/akeit0/okojo/tree/main/.agents/skills/okojo-engine-development -g -y

Use without installing

npx skills use akeit0/okojo@okojo-engine-development

指定 Agent (Claude Code)

npx skills add akeit0/okojo --skill okojo-engine-development -a claude-code -g -y

安装 repo 全部 skill

npx skills add akeit0/okojo --all -g -y

预览 repo 内 skill

npx skills add akeit0/okojo --list

SKILL.md

Frontmatter

{
    "name": "okojo-engine-development",
    "description": "Develop or debug Okojo ECMAScript engine internals. Use for parser, compiler, bytecode, VM, object-model, or built-in implementation work; use the linked specialist skill only when its task matches."
}

Okojo Engine Development

Use this skill only for Okojo engine implementation or debugging. Read ../../../AGENTS.md for repository rules; this skill does not replace them.

Route only when needed

Language/compiler/VM investigation: use the V8 reference and read ../../../docs/performance/OKOJO_VM_DEEP_INSPECTION_METHOD.md when the task is non-trivial.
VM-loop optimization: also read ../../../docs/performance/OKOJO_VM_LOOP_OPTIMIZATION_FOUNDATION.md (workflow) and ../../../docs/performance/OKOJO_VM_DISPATCH_REDUCTION_PROPOSALS.md (active plan) only for that optimization work.
Test262 campaigns: use okojo-test262, not this workflow.
Okojo.Node/Ink debugging: use okojo-node-ink-debug, not this workflow.

API/package/namespace migration, documentation-only edits, and mechanical refactoring do not require this skill.

Minimal default

Inspect the relevant code and tests, make the smallest correct change, and follow the focused-test/full-suite workflow in AGENTS.md. Use V8 for language/compiler/VM behavior and Node for built-in behavior when a semantic reference is needed.

For compiler-only optimization experiments, compare the emitted Okojo bytecode/opcodes with the target first; do not inspect C# IL/JIT for a change that cannot affect them. Run the shortest representative benchmark only after the opcode artifact reaches a plausible target or the comparison is inconclusive. Use C# IL/JIT inspection only when the VM/runtime implementation changed and that native code can be affected; use longer benchmark runs only after the focused check warrants them.

Do not load the deep references or specialist skills unless the current task actually needs them.