Rust Ai Native Terraform logo

Rust Ai Native Terraform

Organization
vibevm
rust-ai-native-terraform

Adopt the AI-Native discipline on an existing (brownfield) Rust codebase — inventory-not-gate, the three registries, characterization goldens, then card raids crate by crate. Use once per codebase (or to resume a partial adoption); the recurring counterpart is /rust-ai-native-sweep.

Overview

Publishervibevm
Repositoryvibevm
Skill namerust-ai-native-terraform
Stars
285
Forks
83
Bundled files
Instructions only
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by vibevm on GitHub. Read the source before you install it.

Installation

Install the Rust Ai Native Terraform AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/vibevm/vibevm/tree/main/vibevm/vibedeps/org.vibevm.fractality.delegation-rules/1.0.0/vibevm/vibedeps/org.vibevm.ai-native.rust-ai-native-lang/1.0.0/vibevm/vibespecs/skills/rust-ai-native-terraform
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/vibevm/vibevm.git /tmp/vibevm
mkdir -p .claude/skills
cp -r /tmp/vibevm/vibevm/vibedeps/org.vibevm.fractality.delegation-rules/1.0.0/vibevm/vibedeps/org.vibevm.ai-native.rust-ai-native-lang/1.0.0/vibevm/vibespecs/skills/rust-ai-native-terraform .claude/skills/rust-ai-native-terraform
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Rust Ai Native Terraform in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Rust Ai Native Terraform on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Rust Ai Native Terraform is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Terraform a Rust codebase (brownfield adoption) {#root}

@fact:EXECUTING-THE-BROWNFIELD-PROTOCOL You are executing the BROWNFIELD protocol (spec://org.vibevm.ai-native/core-ai-native/mechanisms/BROWNFIELD-PROTOCOL-v0.1 — shipped copy under vibedeps/flow-core-ai-native/<version>/spec/mechanisms/; read it before the first phase, and skim 03-RAID-PLAYBOOK + 05-CAMPAIGN-FORM for the campaign machinery). @status:impl/done

@fact:founding-principles-lead The founding principles: @status:impl/done

  • @fact:PRINCIPLE-INVENTORY-NOT-GATE inventory, not gate (the only precondition is "the workspace compiles"); @status:impl/done
  • @fact:PRINCIPLE-ASPIRATION-MUST-BE-LABELED aspiration is legal only when labeled; @status:impl/done
  • @fact:PRINCIPLE-CONTRADICTION-IS-DATA contradiction is data; @status:impl/done
  • @fact:PRINCIPLE-CHARACTERIZATION-IS-THE-TRUTH-OF-RECORD characterization is the truth-of-record; @status:impl/done
  • @fact:PRINCIPLE-MONOTONE-UTILITY monotone utility. @status:impl/done

@fact:DO-NOT-BULLDOZE-AN-INHABITED-WORLD Do not bulldoze an inhabited world. @status:impl/done

@fact:TOOLCHAIN-INSTALL-OR-RUN-IN-PLACE Toolchain: rust-ai-native (install once: cargo install --path vibedeps/<stack-slot>/crates/rust-ai-native-cli, or run via cargo run --manifest-path vibedeps/<stack-slot>/Cargo.toml -p rust-ai-native-cli --bin rust-ai-native -- <args>). @status:impl/done

Phase −1 — inventory (record reality; change nothing) {#phase-inventory}

  1. @fact:INVENTORY-PRECONDITION Precondition: cargo build --workspace succeeds. (Red build → fix the build first; that is the one true gate.) @status:impl/done
  2. @fact:INVENTORY-INIT rust-ai-native init — policies + empty registries. Every crate starts exempt-with-a-reason; nothing is gated yet, and that is correct. @status:impl/done
  3. @fact:INVENTORY-TESTS-BASELINE Fill discipline/registry/tests-baseline.json with reality: run the suite once (cargo nextest run --workspace --no-fail-fast), record every failing test as failing-known with a since date and a debt id — do NOT fix them now (drive-by repairs destroy the accounting). @status:impl/done
  4. @fact:INVENTORY-HARVEST-INTENT Harvest intent into discipline/registry/intent.json: WAL "Next" / TASKS / ROADMAP items, <!-- REVIEW --> markers, load-bearing TODO/FIXME. The carry-over guarantee: at exit every harvested intention is done | rescoped | rejected(reason) — zero unaccounted. @status:impl/done
  5. @fact:INVENTORY-FILE-DEBT File debt into discipline/registry/debt.json: failing tests, known-unimplemented specs, contradictions found while reading — each with severity, evidence, disposition, and touch: tripwires on its watched paths. @status:impl/done
  6. @fact:INVENTORY-CHARACTERIZE Characterize currently-passing observable behavior (golden transcripts under discipline/golden/, normalized for volatile fields): these pin "don't break it" independently of whether tests or docs are trustworthy. A pinned bug is visible debt; an unpinned bug is a landmine. @status:impl/done
  7. @fact:INVENTORY-SPECMAP rust-ai-native specmap — mint the (initially small) index; commit the whole inventory as its own topic commits. @status:impl/done

Phase 0 — the first spec units {#phase-first-spec-units}

@fact:WRITE-THE-FIRST-SPEC-DOCUMENTS Write the project's first spec/ documents for the subsystems you will touch first: anchored headings ({#req-…}), kind lines (`req r1`). @status:impl/done

@fact:UNIMPLEMENTED-BY-PLAN-UNITS-ARE-MARKED-PLANNED Unimplemented-by-plan units are marked planned — zero coverage there is expected, not red. @status:impl/done

@fact:TAG-IMPLEMENTING-MODULES-AS-YOU-GO Tag the implementing modules (specmark::scope!("spec://<ns>/…")) as you go; rust-ai-native specmap after each batch keeps the index green. @status:impl/done

Phases 1…N — card raids, crate by crate {#card-raids}

@fact:raid-per-crate-in-dependency-order-lead Per the Raid Playbook skeleton (scope & freeze → card order → phases → batches → differential safety → exit criteria), and per crate in dependency order: @status:impl/done

  1. @fact:RAID-DRAIN-THE-CRATE Drain the crate: unwraps out of domain code (restructure beats testify), one thiserror enum per layer with REQ-citing messages, a doctest per public seam, cells with oracles where variance exists. rust-ai-native conform check --scope <crate> is the per-crate lens; rust-ai-native fast-loop --cell <crate> keeps the loop under budget. @status:impl/done
  2. @fact:RAID-FLIP Flip: add the crate to conform.toml's [rust] gated (remove its [[rust.exempt]] entry) — legal only at zero findings; a flip must never widen the baseline. @status:impl/done
  3. @fact:RAID-BEHAVIOR-CHANGES-CARRY-AN-ORACLE Behavior changes carry a differential oracle (card scaffold-d); golden transcripts must fail loudly when stale, never auto-update. @status:impl/done
  4. @fact:RAID-PHASE-CLOSES-WITH-THE-FLOOR-GREEN Each phase closes with the floor green (rust-ai-native floor) and its own topic commits, per the Campaign Form's phase-gate discipline. @status:impl/done

@fact:TRACK-THE-CAMPAIGN-PER-CAMPAIGN-FORM Track the campaign per 05-CAMPAIGN-FORM: a cold-executable PLAN, the BASELINE numbers you started from, PREDICTIONS, a LOG, and a closing REPORT. @status:impl/done

@fact:CAMPAIGN-RESUME-POINTER Resume pointer: with a WAL — the standing line at each phase boundary; without — the PLAN's status line + LOG tail (06-WAL-CONVENTION §4). @status:impl/done

Exit criteria {#exit-criteria}

@fact:EXIT-CRITERIA rust-ai-native floor green with every crate either gated or exempt-with-a-living-reason; the test-gate baseline shrunk truthfully (promotions, not silence); the carry-over guarantee met (every intent done | rescoped | rejected); the REPORT written. @status:impl/done

@fact:HELD-BY-THE-RECURRING-SWEEP From here the tree is held by the recurring sweep: /rust-ai-native-sweep. @status:impl/done

The generation-time assistant (before you edit, not instead of the floor) {#generation-time-assistant}

@fact:STACK-SHIPS-AN-AGENTIC-TYPE-ORACLE The stack ships an agentic type oracle. @status:impl/done

@fact:check-the-hypothetical-content-lead Before writing a nontrivial .rs edit, check the HYPOTHETICAL content instead of paying a red floor iteration: @status:impl/done

sh
vibe bin exec rust-ai-native-tcg -- validate src/cells/<cell>.rs \
    --content-from - --root .   # the edit on stdin; exit 1 = would fail

@fact:MCP-ALTERNATIVE or, when the vibevm MCP server is mounted, call tcg_validate with language: "rust" and the content argument (plus tcg_scope / tcg_complete / tcg_type for in-scope symbols, type-valid completions, and quick info). @status:impl/done

@fact:RESPONSES-CARRY-THE-SAME-CONFORM-FINDINGS Responses carry the SAME conform findings as the gate, flagged baselined or new, with guide-citing advice — a new finding in the answer means the floor WILL go red if you write that edit. @status:impl/done

@fact:ORACLE-PREREQUISITE Prerequisite: rust-analyzer on the machine (rustup component add rust-analyzer — a stack obligation). @status:impl/done

@fact:ORACLE-HONESTY Honesty: the oracle is rust-analyzer, not rustc; a clean answer shortens the distance to green, and the floor stays the truth (TCG-ORACLE-RUST §5). @status:impl/done

Frequently asked questions

What does the Rust Ai Native Terraform AI skill do?

Adopt the AI-Native discipline on an existing (brownfield) Rust codebase — inventory-not-gate, the three registries, characterization goldens, then card raids crate by crate. Use once per codebase (or to resume a partial adoption); the recurring counterpart is /rust-ai-native-sweep.

Why use Rust Ai Native Terraform on TypingMind?

Because you install it once and use it with any model. Rust Ai Native Terraform is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Rust Ai Native Terraform in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/vibevm/vibevm/tree/main/vibevm/vibedeps/org.vibevm.fractality.delegation-rules/1.0.0/vibevm/vibedeps/org.vibevm.ai-native.rust-ai-native-lang/1.0.0/vibevm/vibespecs/skills/rust-ai-native-terraform. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Rust Ai Native Terraform?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Rust Ai Native Terraform?

As many as you like. As long as a model supports skills, you can use Rust Ai Native Terraform with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Rust Ai Native Terraform AI skill free?

It is published on GitHub by vibevm. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇