engram-contract

Enforce contract-first domain model consistency across storage, API, and type definitions.

Updated Jun 29, 2026
One-click install
npx skills add https://github.com/phanijapps/engram --skill engram-contract
Or copy as Structured Prompt for Agentβ–Ό
Please help me install this Agent Skill.
Skill: engram-contract
Source: https://github.com/phanijapps/engram/tree/main/.claude/skills/engram-contract
Command: npx skills add https://github.com/phanijapps/engram --skill engram-contract

SYSTEM DOCUMENTATION & REQUIREMENTS

πŸ’‘ This Skill includes references (resource) components.

What problem does it solve?

This skill prevents architectural drift and ensures that Engram's storage, APIs, and type definitions remain consistent with the core domain model, avoiding fragmented interpretations across Rust and TypeScript implementations.

Core Features & Use Cases

  • Contract Validation: Enforces strict adherence to the domain data model during schema or ADR changes.
  • Consistency Checks: Ensures that storage-neutrality and opaque identifier policies are maintained across all system layers.
  • Use Case: When proposing a new feature that modifies the data schema, use this skill to verify that the change preserves provenance, scope, and policy requirements before committing the code.

Quick Start

Use the engram-contract skill to validate the current changes against the domain model and the contract checklist.

Frequently Asked Questions about engram-contract

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I maintain domain model consistency across Rust and TypeScript implementations?β–Ό

To maintain domain model consistency across Rust and TypeScript, enforce contract-first development principles during schema modifications to prevent architectural drift and fragmented interpretations across storage, APIs, and type definitions.

What is contract-first development for storage-neutral architectures?β–Ό

Contract-first development for storage-neutral architectures enforces strict adherence to domain data models, ensuring opaque identifier usage and provenance-aware record structures remain consistent across all system layers during updates.

How do I validate schema changes against architectural decision records?β–Ό

To validate schema changes against architectural decision records, apply contract validation checks to verify that modifications preserve provenance, scope, and policy requirements before committing the updated code.

When do I need to enforce opaque identifier usage in cross-language bindings?β–Ό

You need to enforce opaque identifier usage in cross-language bindings whenever proposing new features or modifying data schemas, ensuring updates maintain storage-neutrality and provenance-aware structures across Rust and TypeScript.

What are the limitations of using contract validation for domain data models?β–Ό

Limitations of using contract validation include the strict requirement for storage-neutrality and provenance-aware records, meaning any schema modification lacking opaque identifiers or violating architectural decision records will fail the consistency checks.