prototype-loop

Automate UI porting and framework gap fixing with AOT analysis and PR monitoring.

1|Updated Jul 11, 2026

Search Tags:#development loop #pr monitoring #ui porting #framework gap fixing #aot analysis

Ready to run

npx skills add https://github.com/danielraffel/burl --skill prototype-loop

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: prototype-loop
Source: https://github.com/danielraffel/burl/tree/main/.agents/skills/prototype-loop
Command: npx skills add https://github.com/danielraffel/burl --skill prototype-loop

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, cmake, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a structured development loop for porting UIs to Pulp, finding and fixing framework gaps, and coordinating multi-PR work.

Core Features & Use Cases

Focused Development Loop: Codifies the leveraged-prototype dev loop for closing framework gaps during UI parity work.
AOT Analyzer Integration: Guided by AOT analyzer to identify framework gaps.
PR Monitoring: Coordinates multi-PR upstream work with real-time PR state monitoring.
Platform-Specific Work: Handles single-platform validation during iteration and cross-platform validation before landing.

Quick Start

Run the 'pulp loop' command to enter focus mode and begin the prototype loop for UI porting or framework gap fixing.

Frequently Asked Questions about prototype-loop

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I streamline UI porting and framework gap fixing during development?▼

To streamline UI porting and framework gap fixing, you can use a structured development loop that integrates AOT analysis to identify gaps and coordinates PR monitoring for multi-PR upstream work.

What is the best way to coordinate batch PR work for UI parity?▼

The best way to coordinate batch PR work for UI parity is using a development loop that monitors real-time PR states, handling single-platform validation during iteration and cross-platform validation before landing.

Do I need gh and cmake to automate the development loop for UI porting?▼

Yes, you need gh and cmake installed because the development loop requires them for tooling integration when automating UI porting and framework gap fixing workflows.

How does AOT analysis identify framework gaps during UI porting?▼

AOT analysis identifies framework gaps during UI porting by guiding the focused development loop, which codifies the prototype process for closing framework gaps during high-feedback UI parity work.

When should I use a focused development loop for cross-platform validation?▼

You should use a focused development loop for cross-platform validation before landing UI porting changes, ensuring that single-platform validation during iteration translates correctly across platforms.