Define and enforce inductive invariants with counterexample traces and verification signals.
npx skills add https://github.com/tkersey/dotfiles --skill invariant-ace
Please help me install this Agent Skill. Skill: invariant-ace Source: https://github.com/tkersey/dotfiles/tree/main/codex/skills/invariant-ace Command: npx skills add https://github.com/tkersey/dotfiles --skill invariant-ace
This Skill helps teams transform vague safety expectations into concrete, enforceable invariants that prevent invalid states across data, protocols, and algorithms. It focuses on owning specific state and boundary mutations, then proving correctness through counterexample traces and explicit verification signals.
Use invariant-ace to structure an invariant plan for a sample module: define scope, owner, a minimal counterexample, and a single, enforceable boundary.
High-intent search queries and answers about installing and using this skill.
To define inductive invariants, you identify the state owner and the transitions that must preserve the invariant conditions. This Skill helps structure that process by establishing scope, enforcement boundaries, and an observable verification plan to prevent race conditions and stale data.
Counterexample-driven refinement is a verification method that uses concrete traces to prove correctness and catch violations early. By refining invariants via these traces, teams can identify exactly how and where data validity or concurrency boundaries fail in their protocols.
You enforce data validity by applying strong, cheap boundaries at parse, construct, API, DB, lock, and transaction levels. This approach ensures that state mutations across modules and services preserve safety conditions and prevent invalid data shapes.
Yes, you can apply formal methods for data validity without external dependencies. This Skill focuses on specifying an owner, defining scope, and creating an observable verification plan with predicates and transitions to guarantee state correctness independently.
The best way to structure an invariant plan is to define the scope, identify the owner, construct a minimal counterexample, and establish a single enforceable boundary. This creates a rock-solid state guarantee by proving correctness through explicit verification signals.
Snowflake-LabsA concise summary of your roleplay character: name,</name> personality, and/or behavior, formatted as a single string sentence. Typically不超过50字，此处省略
ArabelaTsoConverts model checker counterexample traces into executable test cases.
machenjieDesign minimal transaction boundaries preserving named business invariants.
devrelaicomClassify ZKIR claims and dispatch them to appropriate verification methods.
