Agent skill
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-forge/src/historical.rs or contracts/
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/re-bridge
SKILL.md
Before writing any code, read these files:
docs/context/re-findings.md— proven compiler facts, type branches, byte layout, sentinel valuesdocs/context/trust-hierarchy.md— which artifacts are safe to implement fromdocs/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.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?