Source Seam Invariants

Extract and assert textual invariants at production call sites in Rust codebases.

3|3|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/quaid-app/quaid --skill source-seam-invariants
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Source Seam Invariants
Source: https://github.com/quaid-app/quaid/tree/main/.squad/skills/source-seam-invariants
Command: npx skills add https://github.com/quaid-app/quaid --skill source-seam-invariants

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps ensure that critical production call sites and branches stay intact by asserting exact textual invariants across code bases.

Core Features & Use Cases

  • Guard production seams by capturing required arguments, guards, and filters at call sites.
  • Validate refactor safety by locking in specific production patterns against unintended widening.
  • Use with cross-platform Rust codebases to protect pivotal logic during migrations.

Quick Start

Run a seam-invariant check against a production file to verify that the exact call-site patterns remain intact.

Frequently Asked Questions about Source Seam Invariants

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

FAQPage Schema
How do I prevent regressions when refactoring production Rust code?▼

Prevent regressions during Rust refactoring by identifying and locking exact production call-site invariants. This Skill extracts required arguments, guards, and filters at critical seams, then asserts those textual patterns in tests to ensure pivotal logic remains intact across migrations.

What are production seams in static analysis and when do I need to guard them?▼

Production seams are critical call sites where specific arguments, guards, and filters must remain intact. You need to guard them during cross-platform Rust migrations or refactors to prevent unintended widening of production behavior and ensure refactor safety.

How do I assert invariants at specific call sites in a Rust codebase?▼

Assert invariants at Rust call sites by performing explicit production file analysis to extract the smallest necessary patterns, then documenting and testing explicit guard and assert patterns against those exact textual invariants to lock the required behavior.

Can I use source seam invariants for cross-platform Rust migrations?▼

Yes, source seam invariants apply directly to cross-platform Rust codebases where production behavior must be preserved across refactors. The process captures required arguments and filters at pivotal call sites to validate refactor safety during migrations.

What's the best way to validate refactor safety without breaking existing production branches?▼

Validate refactor safety by locking specific production patterns against unintended widening through invariant extraction. Capture exact textual invariants at call sites and apply explicit guard and assert patterns that are documented and tested to keep branches intact.

Why do my refactored Rust functions break production behavior even when tests pass?▼

Refactored Rust functions break production behavior when call-site invariants widen unintentionally. Locking the smallest necessary required arguments, guards, and filters through explicit assert patterns prevents these regressions when standard tests fail to catch textual pattern changes.