re-bridge

Use when working on historical compiler path, RE-derived code, morph designer bridge, type 2/3 branches, sanitized handoffs, stage byte layout, passthrough sentinel, trust tiers, or any code in trench

SKILL.md.claude/skills/re-bridge/SKILL.md

Before writing any code, read these files:

docs/context/re-findings.md — proven compiler facts, type branches, byte layout, sentinel values
docs/context/trust-hierarchy.md — which artifacts are safe to implement from
docs/context/identity.md — TRENCH is a stress simulator, not an emulation

Key constraints:

Data flows one way: DIRTY → sanitized → CLEAN. Never reverse.
Only Tier 1 and Tier 2 artifacts are implementation-ready. Tier 3 = orientation only. Tier 4 = do not implement.
MorphDesigner is NOT the fix for forge quality — it's a small deterministic compiler, same ceiling as RBJ.
No ROM dumps, binary blobs, or address-derived artifacts in shipping code.
No heritage branding (E-mu, Morpheus, Z-Plane) in anything that ships.

Related in development

update-docs-vercel-next-js

This skill should be used when the user asks to "update documentation for my changes", "check docs for this PR", "what d...

docstring-pytorch-pytorch

Write docstrings for PyTorch functions and methods following PyTorch conventions. Use when writing or updating docstring...

at-dispatch-v2

Convert PyTorch AT_DISPATCH macros to AT_DISPATCH_V2 format in ATen C++ code. Use when porting AT_DISPATCH_ALL_TYPES_AND...