Run any Skill in Manus with one click

build-loop-ibr-bridge

Stars1

Forks0

UpdatedJuly 2, 2026 at 22:06

Routing bridge to the IBR plugin for UI visual verification. Build-loop prefers IBR `scan` / `scan_macos` when the IBR plugin is installed; otherwise falls back to build-loop's own `native-ax-driver` / `ui-validator`. Never falls back to nm/strings. NOT for API registration (use `api-registry-bridge`) or PRD grounding (use `prd-bridge`).

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

tyroneross

tyroneross/build-loop

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	build-loop:ibr-bridge
description	Routing bridge to the IBR plugin for UI visual verification. Build-loop prefers IBR `scan` / `scan_macos` when the IBR plugin is installed; otherwise falls back to build-loop's own `native-ax-driver` / `ui-validator`. Never falls back to nm/strings. NOT for API registration (use `api-registry-bridge`) or PRD grounding (use `prd-bridge`).
version	0.3.0
user-invocable	false

IBR Bridge (Primary-When-Present, Native-Fallback)

Build-loop routes UI visual verification through IBR when the IBR plugin is installed, and through its own native verifiers when it isn't. There is no third path — nm/strings/git grep over symbols never satisfies the visual-evidence gate (enforced by skills/build-loop/scanners/require-visual-evidence.mjs at chunk-close and Phase 4-B).

The previous "explicit-only" policy was reversed 2026-06-04 because it left the macOS path without a default visual verifier in projects that didn't have IBR — the symbol-only escape hatch then carried briefs past the (prose-only) verify mandate.

Routing rule

At Phase 1 Assess, the orchestrator reads state.json.availablePlugins.ibr (populated by detect-plugins.mjs).

Build-loop need	Primary (when `availablePlugins.ibr == true`)	Fallback (when IBR absent)
Web UI verify	IBR `scan` against the dev-server route	`ui-validator` agent + browser/screenshot tooling
macOS UI verify	IBR `scan_macos` against the running `.app`	`native-ax-driver` (`skills/native-ax-driver/`) pid-anchored AX-tree + screenshot
iOS sim UI verify	IBR `scan` against the booted sim (when supported)	`xcrun simctl io booted screenshot` + `idb ui` for interaction
Visual-evidence at chunk-close	Whichever of the above ran	(same)

Subagent dispatch briefs MAY name IBR scan / scan_macos as the verifier — BUT only after the orchestrator has confirmed availablePlugins.ibr == true. When it is false, the brief MUST name the native-fallback verifier instead (per the [ME] guardrail in agents/build-orchestrator.md §"Phase 3 Execute" — never name a tool the implementer can't reach).

Allowed scope

When the bridge is the primary route (IBR present):

Run scan / scan_macos against the running app or dev-server route, capture the result envelope, and pass it forward as the chunk's evidence_paths / verification text.
Use IBR token / design-system checks as comparison input.
Run a project-authored .ibr-test.json suite.
Generate .ibr-test.json drafts only when the build's plan explicitly authorizes IBR test generation.

When the bridge is the fallback route (IBR absent):

Skip with a one-line note (ibr: not installed; falling back to native-ax-driver / ui-validator); do NOT write to .ibr/.
Do NOT install or download IBR mid-build.

Forbidden

Do NOT fall back to nm / strings / git grep over compiled symbols as UI verification. The BL-1 gate (scanners/require-visual-evidence.mjs) rejects this with exit 2 and routes the chunk back to Iterate.
Do NOT invoke IBR viewer / dashboard / UI surfaces from build-loop.
Do NOT write .ibr/ unless the build's plan or the user's request requires an IBR output directory.

Output contract

The bridge returns results in the same envelope shape regardless of which route fired:

{
  "status": "ran | skipped | failed",
  "route": "ibr | native | fallback-skipped",
  "verifier": "scan_macos | scan | native-ax-driver | ui-validator | none",
  "artifacts": ["path-or-url-or-pid-anchor"],
  "verification": "<freeform text suitable for the BL-1 gate envelope>",
  "findings": [{"severity": "info|warn|blocker", "message": "..."}]
}

The orchestrator forwards verification and artifacts to the BL-1 gate envelope as the chunk's verification and evidence_paths fields.

Status: 0.3.0 (2026-06-04)

Reversed the explicit-only default. IBR is now the preferred primary when present; build-loop-owned native-ax-driver / ui-validator is the always-available fallback.
The bridge stays user-invocable: false because it's part of the orchestrator's verify-path routing, not a manual user command.
Canonical build-loop design and validation artifacts remain .build-loop/app-contract/*, ui-validator envelopes, and Review-G outputs whichever route fires.

More from this repository

same repository

handoff

tyroneross/build-loop

Compose a complete, durable build-loop handoff document from the current run state, and optionally launch a fresh session with it injected. Use when crossing a context boundary (context limit, planned restart, worktree GC). Triggers: 'hand off', 'handoff', 'new session', 'context limit', 'restart', 'fresh session', '/build-loop:compose-handoff'.

2026-07-261

ui-design

tyroneross/build-loop

Use when build-loop needs UI design direction, visual style selection, UI guidance inventory, a .build-loop/app-contract/ui.md design contract, or non-trivial web/mobile/native UI planning. Build-loop-owned design route for design-contract-specialist; selects from project tokens, recent structures, UI Guidance, IBR artifacts, Mockup Gallery, and research based on product/workflow/data/platform fit.

2026-07-251

color-engine

tyroneross/build-loop

Generate accessible color systems and solve contrast, instead of guessing hex values. Use when picking or fixing colors for any UI, chart, diagram, doc, or artifact — "what colors should this use", "is this readable", "this text fails contrast", "make a dark theme", "pick an accent". Also use before shipping any palette, to PROVE contrast rather than assert it. NOT for choosing layout, typography, or component structure.

2026-07-251

build-loop-data-plane-worktrees

tyroneross/build-loop

Use when a Build Loop run or Git worktree touches mutable non-Git state: SQLite or file-backed databases, PostgreSQL databases/schemas and migrations, generated search/vector indexes, Docker volumes or service projects, mutable file trees, caches that cannot be rebuilt safely, or external cloud/account namespaces. Inventories each surface, selects per-worktree, shared-readonly, shared-serialized, or external-namespaced isolation, registers it in the run data manifest, validates collisions before writes, and requires a terminal disposition at closeout.

2026-07-231

model-tiering

tyroneross/build-loop

Use when choosing a model tier or segment for a subagent, deciding a role descriptor (segment + tier) in frontmatter, or escalating mid-flow. Covers the two-axis taxonomy (work-role segment × 7-rung capability ladder) — Opus/Sonnet/Haiku are Anthropic-default mappings; selection is provider-portable and data-driven. NOT for benchmarking models head-to-head on a task — use `model-bakeoff`.

2026-07-231

build-loop

tyroneross/build-loop

Orchestrated build loop for multi-step code work. TRIGGER on verb language ('build', 'implement', 'create', 'add', 'ship', 'wire up', 'integrate', 'refactor', 'migrate', 'rewrite', 'replace') OR symptom language ('fix', 'broken', 'doesn't work', 'isn't loading', 'not displaying', 'missing', 'should show', 'needs to', 'make it', 'show this differently') OR any task touching 2+ files, adding/removing an endpoint, crossing an architectural boundary, or attached screenshots of a bug. SKIP one-line edits, pure Q&A, conversational clarifications, status checks, and trivial typos/renames.

2026-07-211

name	build-loop:ibr-bridge
description	Routing bridge to the IBR plugin for UI visual verification. Build-loop prefers IBR `scan` / `scan_macos` when the IBR plugin is installed; otherwise falls back to build-loop's own `native-ax-driver` / `ui-validator`. Never falls back to nm/strings. NOT for API registration (use `api-registry-bridge`) or PRD grounding (use `prd-bridge`).
version	0.3.0
user-invocable	false

IBR Bridge (Primary-When-Present, Native-Fallback)

Routing rule

At Phase 1 Assess, the orchestrator reads state.json.availablePlugins.ibr (populated by detect-plugins.mjs).

Build-loop need	Primary (when `availablePlugins.ibr == true`)	Fallback (when IBR absent)
Web UI verify	IBR `scan` against the dev-server route	`ui-validator` agent + browser/screenshot tooling
macOS UI verify	IBR `scan_macos` against the running `.app`	`native-ax-driver` (`skills/native-ax-driver/`) pid-anchored AX-tree + screenshot
iOS sim UI verify	IBR `scan` against the booted sim (when supported)	`xcrun simctl io booted screenshot` + `idb ui` for interaction
Visual-evidence at chunk-close	Whichever of the above ran	(same)

Allowed scope

When the bridge is the primary route (IBR present):

Run scan / scan_macos against the running app or dev-server route, capture the result envelope, and pass it forward as the chunk's evidence_paths / verification text.
Use IBR token / design-system checks as comparison input.
Run a project-authored .ibr-test.json suite.
Generate .ibr-test.json drafts only when the build's plan explicitly authorizes IBR test generation.

When the bridge is the fallback route (IBR absent):

Skip with a one-line note (ibr: not installed; falling back to native-ax-driver / ui-validator); do NOT write to .ibr/.
Do NOT install or download IBR mid-build.

Forbidden

Do NOT fall back to nm / strings / git grep over compiled symbols as UI verification. The BL-1 gate (scanners/require-visual-evidence.mjs) rejects this with exit 2 and routes the chunk back to Iterate.
Do NOT invoke IBR viewer / dashboard / UI surfaces from build-loop.
Do NOT write .ibr/ unless the build's plan or the user's request requires an IBR output directory.

Output contract

The bridge returns results in the same envelope shape regardless of which route fired:

{
  "status": "ran | skipped | failed",
  "route": "ibr | native | fallback-skipped",
  "verifier": "scan_macos | scan | native-ax-driver | ui-validator | none",
  "artifacts": ["path-or-url-or-pid-anchor"],
  "verification": "<freeform text suitable for the BL-1 gate envelope>",
  "findings": [{"severity": "info|warn|blocker", "message": "..."}]
}

The orchestrator forwards verification and artifacts to the BL-1 gate envelope as the chunk's verification and evidence_paths fields.

Status: 0.3.0 (2026-06-04)

Reversed the explicit-only default. IBR is now the preferred primary when present; build-loop-owned native-ax-driver / ui-validator is the always-available fallback.
The bridge stays user-invocable: false because it's part of the orchestrator's verify-path routing, not a manual user command.
Canonical build-loop design and validation artifacts remain .build-loop/app-contract/*, ui-validator envelopes, and Review-G outputs whichever route fires.