Claude Skills by AI-native-Systems-Research

Cross-check a Certus component's nested Spec Kit `specs/**/spec.md` specifications against its generated implementation and tests, then summarize semantic translation mismatches with source evidence. Use when auditing whether generated code faithfully implements component requirements, acceptance scenarios, interfaces, defaults, constraints, errors, or success criteria; when checking implementation drift after generation or code changes; or when asked to compare a component spec with code. Th...

Cross-check a Certus component's abstract verification artifacts (a `verif/` Creusot mirror, a `#[cfg(kani)] mod verification`, or a Spin `.pml` model) against its concrete shipped implementation, then summarize concrete-code/abstract-code drift with source evidence. Use when auditing whether a formal-verification harness still faithfully mirrors the code it claims to prove, when checking for vacuous contracts or unmatched assumptions after code changes, or when validating what `component-poi...

Deliberately introduce a controlled number of specification/code misalignments ("poisons") into a single Certus component on a throwaway branch, in order to test translation-verification tooling such as `component-check-spec-translation`. Each poison intentionally desynchronizes the component's `spec.md` from its implementation while keeping the code compiling. Use only for red-team / evaluation of the audit skills, never on a branch intended to merge.

Checks that any component that is being used by another component is only accessed through the component's interface and does not interact directly with the struct.

Cross-check a Certus component's nested Spec Kit `specs/**/spec.md` specifications against its generated implementation and tests, then summarize semantic translation mismatches with source evidence. Use when auditing whether generated code faithfully implements component requirements, acceptance scenarios, interfaces, defaults, constraints, errors, or success criteria; when checking implementation drift after generation or code changes; or when asked to compare a component spec with code. Th...

Cross-check a Certus component's abstract verification artifacts (a `verif/` Creusot mirror, a `#[cfg(kani)] mod verification`, or a Spin `.pml` model) against its concrete shipped implementation, then summarize concrete-code/abstract-code drift with source evidence. Use when auditing whether a formal-verification harness still faithfully mirrors the code it claims to prove, when checking for vacuous contracts or unmatched assumptions after code changes, or when validating what `component-poi...

Bootstrap a new component from an existing one, preserving its provided interfaces and receptacles under a different component name.

Create a new actor component skeleton

Create a new component skeleton

Create a new version of a component

Deliberately introduce a controlled number of misalignments into BOTH sides of a single Certus component on a throwaway branch — some seeded as spec.md/code mismatches (concrete side) and some as code/verif mismatches (abstract side) — so a red-team run can exercise `component-check-spec-translation` and `component-check-verif-translation` at once. The two poison sets are independent (no coupling): each is meant to be caught by its own audit. Use only for evaluation of the audit skills, never...

Deliberately introduce a controlled number of concrete-code/abstract-code misalignments ("verif poisons") into a single Certus component on a throwaway branch, in order to test formal-verification drift tooling (Creusot mirror/equality checks, Kani assume-audits, and `tools-spin-sync`). Each poison intentionally desynchronizes the component's verification artifacts (a `verif/` Creusot mirror, a `#[cfg(kani)] mod verification`, or a Spin `.pml` model) from the shipped implementation while keep...

Deliberately introduce a controlled number of specification/code misalignments ("poisons") into a single Certus component on a throwaway branch, in order to test translation-verification tooling such as `component-check-spec-translation`. Each poison intentionally desynchronizes the component's `spec.md` from its implementation while keeping the code compiling. Use only for red-team / evaluation of the audit skills, never on a branch intended to merge.

Remove a component from the code base.

Ensure a component implementation is synchronized with its specifications.

Ensure the per-component README.md are up to date and correctly reflect the code.

Update or create design artifacts for a certus-server-yaml profile

Extract verifiable correctness properties from ONE component artifact — a spec, the source code, or a verification harness/verif — at a fixed, comparable granularity, with coverage by construction.

Compare performance of the current branch against another branch (default unstable)

Measure raw hardware bandwidth ceilings for all data paths (NVMe, GPU, memory, P2P, GDS, GDRCopy) on the current platform

Run all four KV-offload benchmark variants (NoOffload, CPUOffload, SharedStorage, Certus-SPDK) against the same 12-turn ShareGPT replay and present throughput in one side-by-side table. Use when the user wants to compare offload backends end-to-end.

Measure system performance of this platform using

Save current session transcript to markdown with per-turn token counts, cost breakdown, and context usage.

Set up the claude-codex-bridge so Claude Code can talk to OpenAI Codex CLI (and vice versa) via MCP.

Present a summary of the code base including lines of source code and complexity metrics.

Formally verify a component's properties with Creusot and annotate its interface definitions

Add Coq 8.20 as an additional prover to an existing Creusot installation, for verification conditions that SMT solvers cannot discharge

Build and maintain a simplified spec-to-proof documentation set for Creusot by extracting properties from component specs, tracking assumptions/trusted boundaries, and generating drift/coverage reports.

Prepare an existing Cargo project to use Creusot formal verification

Install the Creusot Rust verification tool

Initialize a new directory with spec-kit (specify) and install the spec-kit-sync extension

Create a new Spin/Promela formal verification model for a system property

Synchronize Spin/Promela models with current source code and re-verify

Create a Creusot verification for a Certus component from BOTH its spec and its Rust code — at function granularity with spec-derived contracts — prove it, and emit a plain-English `PROPERTIES.md` recording exactly what was proved (with evidence). Use for the normal verify-and-document workflow (not the blind property-extraction experiment).

Identify what to verify in real-world Rust code, extract the pure core, and drive it to a full Creusot proof

Create Kani harnesses for a Certus component from BOTH its spec and its Rust code — at function granularity, calling the real function under spec-derived pre/postconditions — run them, and emit a plain-English `PROPERTIES.md` of what was verified (with evidence). Use for the normal verify-and-document workflow (not the blind property-extraction experiment).

Verify a Rust component using Kani model checking — stub unsafe/FFI dependencies, write harnesses targeting arithmetic and state invariants, audit kani::assume calls against production guards, fix gaps, and re-verify.

Update the component description files for the knowledge base

Ensure a component implementation is synchronized with its specifications.

Ensure the per-component README.md are up to date and correctly reflect the code.

Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.

Generate a custom checklist for the current feature based on user requirements.

Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.

Analyze drift between specs and implementation. Compares requirements

Auto-commit changes after a Spec Kit command completes

Create a feature branch with sequential or timestamp numbering

Initialize a Git repository with an initial commit

Detect Git remote URL for GitHub integration

Validate current branch follows feature branch naming conventions

Execute the implementation plan by processing and executing all tasks defined in tasks.md