# Contract Guardrails

> Contract safety for TS/Rust IPC changes. Use when command signatures, payloads, event types, or generated bindings may drift. Use when this capability is needed.

- Skill: `tomevault-io/contract-guardrails` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add tomevault-io/contract-guardrails`
- Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/contract-guardrails/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: tomevault-io (https://skillmd.com/u/tomevault-io)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/tomevault-io/contract-guardrails

---


# Contract Guardrails

Use this skill when touching Tauri commands/events or TS client boundary contracts.

## Required Workflow

1. Keep these version sources synchronized only during explicit release work:
- `package.json`
- `src-tauri/tauri.conf.json`
- `src-tauri/Cargo.toml`
2. For command/event or payload changes, verify contract parity:
```bash
scripts/checks.sh standard
```
3. For release-critical merges, run strict binding drift checks:
```bash
bun run bindings:check
# or
CHECK_BINDINGS_STRICT=1 scripts/checks.sh standard
```

## Command Pointers

- IPC contract registration: `src-tauri/src/ipc_contract.rs`
- TS runtime adapter boundary: `src/lib/tauri/client.ts`
- Binding drift guard: `scripts/check-generated-bindings.sh`

## Done Criteria

- Rust commands/events compile and remain registered.
- Generated TS bindings match Rust contract.
- Standard checks pass for non-doc changes.

## Alignment

- Use root AGENTS precedence.
- No implicit internal legacy assumptions.
- Fallback behavior requires explicit trigger/evidence/sunset and fallback-policy compliance.

---
> Converted and distributed by [TomeVault](https://tomevault.io/claim/allmight97) — claim your Tome and manage your conversions.
<!-- tomevault:4.0:skill_md:2026-04-13 -->