mechanical-port-acrazie
Mechanical Port / Acrazie
Port a selected source-to-target language boundary with faithful structural mirroring and an objective test oracle. Do not redesign or introduce hybrid FFI as an unapproved shortcut.
Project loading boundary
Published-library defaults remain model-invocable within the requested task. An
explicit project kit or stricter current instruction takes precedence: propose
this skill from available metadata and wait for the user's explicit command before
reading its instructions. Apply the same gate to each dependency before reading
or dispatching its instructions. Use $skill-name in Codex or /skill-name in
Claude Code. One invocation does not activate a chain; do not read or delegate
an unactivated skill as a bypass. Each re-review of a new snapshot requires a new
reviewer activation in an explicit kit, and returning to the implementer requires
its explicit activation. Ordinary library defaults retain scoped implicit handoffs.
These gates are not filesystem access controls or proof of live host behavior;
unresolved global homonyms may block a strict gate claim.