write-compressor

Develop compression encoders with decoder state synchronization and dual simulation verification.

127|27|Updated Mar 27, 2026

Search Tags:#verification #simulation #compression #decoder #arithmetic-coding #encoder #state-synchronization

Ready to run

npx skills add https://github.com/lazyFrogLOL/Harness_Engineering --skill write-compressor-lazyfroglol

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: write-compressor
Source: https://github.com/lazyFrogLOL/Harness_Engineering/tree/main/skills/write-compressor
Command: npx skills add https://github.com/lazyFrogLOL/Harness_Engineering --skill write-compressor-lazyfroglol

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps developers create compression encoders that produce output fully compatible with existing decoders, especially for arithmetic coding where exact state alignment is critical.

Core Features & Use Cases

Decoder‑first analysis: Build a simulator of the target decoder to trace state transitions before writing the encoder.
Incremental implementation: Start with single‑bit encoding, then add integer and sequence handling before tackling full‑file compression.
Dual simulation verification: Run encoder and decoder side‑by‑side, asserting state and output parity after each operation.
State synchronization guidance: Detailed checks for renormalization, probability model updates, and range calculations.
Verification workflow: Unit‑test driven development, extensive debug output, and minimal test‑case strategy.

Quick Start

Ask the write-compressor skill to outline the steps for creating a single‑bit arithmetic encoder that matches a given decoder.

Frequently Asked Questions about write-compressor

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

FAQPage Schema

How do I build a compression encoder compatible with an existing decoder?▼

Build a compatible compression encoder by first creating a simulator of the target decoder to trace state transitions, then implementing the encoder incrementally using unit-test driven development to ensure exact state synchronization.

How does state synchronization work for arithmetic coding encoders?▼

State synchronization for arithmetic coding encoders requires dual simulation verification, running encoder and decoder side-by-side while asserting state and output parity after each operation to catch renormalization and probability model mismatch errors.

What is the best way to start implementing an arithmetic coding encoder?▼

Start implementing an arithmetic coding encoder by building a single-bit encoder that matches the target decoder, then progressively add integer and sequence handling before attempting full-file compression.

Why does my custom compression encoder produce invalid output for an existing decoder?▼

Your custom compression encoder likely produces invalid output due to state desynchronization during renormalization or probability model updates, requiring stepwise decoder analysis and dual simulation verification to debug.

Can I use dual simulation to verify bit-level compression schemes?▼

Yes, you can use dual simulation to verify bit-level compression schemes by running your custom encoder and the target decoder simultaneously, asserting state and output parity after each operation to validate compatibility.

Do I need to analyze the decoder before writing a custom encoder?▼

Yes, you need to perform decoder-first analysis before writing a custom encoder, building a simulator to trace state transitions and understand the probability model updates required for exact output compatibility.