porting-to-rs

What problem does it solve?

This skill guides safe, spec-aligned porting of a GraphReFly slice from TypeScript to the Rust workspace without drifting from the canonical post-Phase 13.6.A behavior.

Core Features & Use Cases

• Spec-first Rust porting workflow: Enforces reading and implementation against the canonical Rust spec document, not current TS structure.
• Parallelized research + architecture HALT: In full mode, requires a “HALT → Architecture Discussion → user approval” step before any code changes for the slice.
• Parity-grade implementation loop: Directs implementation, rule-referenced tests, clippy/fmt self-checks, and (when applicable) parity-test scenario widening.
• Cross-repo drift prevention: Uses migration-status, porting-deferred, flowcharts, and TLA+ research to avoid reintroducing deferred concerns or violating handle-protocol/lock/refcount invariants.

Quick Start

Use the porting-to-rs skill when you want to implement or extend a GraphReFly Rust port slice in graphrefly-rs based on the canonical TS/Rust spec, by running it with a task description like: porting-to-rs --light “implement Rust parity for the next dispatcher slice and add the required self-test coverage”