# Legacy Contracts

> Use when maintaining a legacy system whose browser, template, database, device, or deployment contracts must be preserved.

- Skill: `jukrap/legacy-contracts` (Agent Skill, multi-file: 18 files)
- Install (CLI): `npx skillmds@latest add jukrap/legacy-contracts`
- Raw SKILL.md: https://api.skillmd.com/api/skills/jukrap/legacy-contracts/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: jukrap (https://skillmd.com/u/jukrap)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/jukrap/legacy-contracts

---


# Legacy Contracts

Identify the deployed runtime and contract that the requested change touches. Keep version, encoding, selector, form, session, database, device and bridge assumptions explicit. Existing compatibility requirements do not require a general modernization workflow.

Read `references/contract-map.md` to select the relevant stack reference. Read only that reference; do not load every legacy profile. Distinguish static/fixture checks from verification in the required browser, engine, database or device. Missing runtime evidence limits the claim, not all independent implementation work.