zplane-implementer

Execute the 4-Phase Z-Plane migration plan for E-mu H-Chip emulation.

Updated Nov 21, 2025
One-click install
npx skills add https://github.com/1hoookkk/Vessel_archive --skill zplane-implementer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: zplane-implementer
Source: https://github.com/1hoookkk/Vessel_archive/tree/main
Command: npx skills add https://github.com/1hoookkk/Vessel_archive --skill zplane-implementer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents incorrect DSP migrations by guiding implementation of the Z-Plane replacement plan while enforcing the E-mu H-Chip’s fixed-point and topology constraints.

Core Features & Use Cases

  • Phase-gated migration execution: Carries the full 4-Phase roadmap in mind to ensure work proceeds in the correct order and avoids premature visualization or interface changes.
  • H-Chip authenticity enforcement: Strictly applies 14-pole cascade requirements, inter-stage saturation behavior, fixed-point math constraints, and coefficient truncation rules.
  • ARMAdillo k-space encoding discipline: Keeps coefficient calculations in k-space (Pitch/Resonance) before decoding into the DSP structure.

Quick Start

Use the zplane-implementer skill to map UI parameters into the Z-Plane engine by executing Phase 1.1 through 1.3, explicitly ensuring fixed-point Q31/Q15 constraints and the full 14-pole TDF-II cascade are preserved.

Frequently Asked Questions about zplane-implementer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I execute a DSP core replacement while preserving H-Chip fixed-point constraints?

To execute a DSP core replacement, follow a 4-Phase migration plan that enforces 14-pole cascade topology, int32 fixed-point signal paths, and int16 coefficient truncation to maintain H-Chip authenticity.

What is ARMAdillo k-space encoding in Z-Plane DSP migration?

ARMAdillo k-space encoding is the discipline of calculating filter coefficients in k-space using Pitch and Resonance parameters before decoding them into the Z-Plane DSP structure.

How do I map UI parameters to a Z-Plane engine without breaking real-time safety?

Map UI parameters by executing Phase 1.1 through 1.3, explicitly ensuring fixed-point Q31/Q15 constraints and the full 14-pole TDF-II cascade are preserved throughout the signal path.

Does Z-Plane migration require phase-ordered execution for visualization wiring?

Yes, Z-Plane migration requires phase-ordered execution to coordinate visualization wiring and DSP replacement, avoiding premature interface changes and triggering explicit conflict warnings when steps are misaligned.

Why does my H-Chip emulation fail authenticity checks after DSP migration?

H-Chip emulation fails authenticity checks when the migration violates inter-stage saturation behavior, fixed-point math constraints, or the strict 14-pole cascade requirements required by the architecture.

What is the best way to coordinate IZPlaneEngine parameter plumbing during refactoring?

The best way to coordinate IZPlaneEngine parameter plumbing is through a phase-gated migration execution, ensuring work proceeds in the correct order without violating architectural authenticity constraints.