Rekonquest
Community@Rekonquest
Rekonquest provides a gated six-step Rust build pipeline for Ordo apps, enforcing sealed crates, frozen message contracts, and verified Tokio bus coupling.
Agent Skills by Rekonquest
Showing 12 vetted skills indexed across 1 GitHub repositories.
Rekonquestordo-build-test
Runs whole-system testing and independent review on a coupled Ordo build before launch-proofing.
Rekonquestordo-crate-couple
Wire built Rust crates onto a Tokio message bus one connection at a time with per-wiring verification.
Rekonquestordo_rust_architecture
Guides building, repairing, and reviewing Rust crates in Ordo Cargo workspaces.
Rekonquestordo-launch-proof
Validates Ordo app completion by launching the binary and proving a live UiInput round-trip.
Rekonquestordo-build-intake
Captures complete requirements records through clarifying questions before Ordo app builds begin.
Rekonquestordo-uxi-builder
Designs operator-friendly Ordo application interfaces with surfaced controls, logs, and human-like verification.
Rekonquestordo-build-pipeline
Sequences six gated build steps for autonomously constructing Ordo applications.
Rekonquestordo-error-router
Routes build gate failures into bounded autonomous retries or hard halts.
Rekonquestrust-vibe-coder
Implements and verifies Rust changes in Cargo workspaces under Ordo architecture rules.
Rekonquestordo-build-blueprint
Generates a frozen crate blueprint with message contracts, dependency DAG, and topological build order.
Rekonquestspiderweb-bus
Implements a layered spiderweb bus architecture for routing data between nodes in Rust.
Rekonquestordo-crate-build
Builds Ordo blueprint crates one at a time with anti-stub and warnings-as-errors gates.
Frequently Asked Questions About Rekonquest
FAQPage SchemaWhat tasks can I accomplish with Rekonquest's Ordo skills?▼
You can run a complete gated Ordo app build: capture requirements, produce a blueprint with frozen claw-protocol message contracts and a dependency DAG, build sealed crates in topo order, couple them onto the Tokio bus, run exhaustive tests, and launch-proof with a proven UiInput round-trip.
Who are these skills designed for?▼
They target Rust developers and coding agents working in Ordo-style projects under Jesse's architecture — specifically the coding and rust_vibe_coder modes. The planner role uses ordo-build-pipeline to sequence steps, while coder roles execute individual step skills like crate-build and crate-couple.
How does the build pipeline enforce quality?▼
Each of the six steps has an entry condition and exit gate returning a GateResult. Crates must compile clean with no stubs or silenced warnings, coupling verifies each wiring individually, and launch-proof requires a real bus round-trip — not just a screenshot — with zero deferred debt.
What happens when a build step fails?▼
The ordo-error-router handles every GateResult::Fail by classifying the fix as bounded or unbounded. Bounded fixes enter a Debugger loop capped at three re-gated retries logged to a retry ledger; unbounded failures halt and surface to the user. Deferred-unverifiable wirings are tracked as debt, never routed as errors.
What prerequisites do these skills require?▼
Most skills require tool access (requires_tools: true) and operate within Rust Cargo workspaces using the Tokio runtime. The spiderweb-bus skill, covering Jesse's proprietary layered bus architecture, requires no tools and should be read before writing any bus or data-routing code.