cpp-parity-porting

スター1

フォーク0

更新日2026年4月16日 12:47

Port one upstream ome-zarr-py surface to standalone native C++ without touching the frozen snapshot.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

strmt7

strmt7/ome-zarr-C

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

C++ Parity Porting

Use this skill when converting an upstream Python module or helper.

Workflow

Read the upstream implementation from source_code_v.0.15.0/.
Keep semantics in cpp/native/. Use cpp/tools/ for standalone executable entrypoints and cpp/api/ only for a thin C ABI over already-native semantics.
Port behavior first, including exception types and messages when they are observable.
Do not add Python-object semantics. If the upstream surface is hard to model because it depends on Python runtime behavior, keep that behavior in the frozen development oracle until a native model is designed and tested.
Load immutable-parity-proof before making any parity or native-coverage claim.
Add differential tests against the upstream snapshot.
If the observable output includes absolute paths and the surface is read-only, run the upstream and converted implementations against the same fixture path to avoid false stdout mismatches.
Do not keep Python-object semantics in C++ implementation code. Optional interoperability belongs in cpp/api/ as raw buffers and JSON, not as pybind or CPython object dispatch.
After parity holds, load benchmark-first and cpp-performance-optimization before making performance changes.
Do not describe a surface as pure-native unless the semantics live in cpp/native/.

このリポジトリの他の Skills

同じリポジトリ

browser-fallback

strmt7/ome-zarr-C

Use a deterministic browser workflow only when direct fetch or extraction is insufficient for a public-web task.

2026-04-171

verification-loop

strmt7/ome-zarr-C

Run the smallest correct verification lane and report it precisely.

2026-04-171

compliance-and-rate-limit

strmt7/ome-zarr-C

Keep public-web research compliant, bounded, and efficient through rule checks, caching, and backoff instead of evasive scraping.

2026-04-171

cpp-performance-optimization

strmt7/ome-zarr-C

Optimize a parity-proven ome-zarr native C++ surface for measurable speedups by improving data layout, copies, cache behavior, and boundary design without changing behavior.

2026-04-171

benchmark-first

strmt7/ome-zarr-C

Benchmark converted code against the frozen upstream implementation before making performance claims.

2026-04-171

pybind11-runtime-parity

strmt7/ome-zarr-C

Legacy reference only. Current main does not use pybind11 ports; use this only to understand old debt before removing it.

2026-04-161

name	cpp-parity-porting
description	Port one upstream ome-zarr-py surface to standalone native C++ without touching the frozen snapshot.
origin	repo-local

C++ Parity Porting

Use this skill when converting an upstream Python module or helper.

Workflow

Read the upstream implementation from source_code_v.0.15.0/.
Keep semantics in cpp/native/. Use cpp/tools/ for standalone executable entrypoints and cpp/api/ only for a thin C ABI over already-native semantics.
Port behavior first, including exception types and messages when they are observable.
Do not add Python-object semantics. If the upstream surface is hard to model because it depends on Python runtime behavior, keep that behavior in the frozen development oracle until a native model is designed and tested.
Load immutable-parity-proof before making any parity or native-coverage claim.
Add differential tests against the upstream snapshot.
If the observable output includes absolute paths and the surface is read-only, run the upstream and converted implementations against the same fixture path to avoid false stdout mismatches.
Do not keep Python-object semantics in C++ implementation code. Optional interoperability belongs in cpp/api/ as raw buffers and JSON, not as pybind or CPython object dispatch.
After parity holds, load benchmark-first and cpp-performance-optimization before making performance changes.
Do not describe a surface as pure-native unless the semantics live in cpp/native/.