Contextual Tutorial Cards
ForgeFarm keeps one next action visible, names the key, and advances only when the world state proves completion.
KUBO VALUE: lower onboarding frictionFeature Transfer / Prompt Examples
Steal the proven interaction patterns—not the old visual skin. ForgeFarm contributes tight operator loops, stateful equipment, persistent telemetry, and spatial objectives. ForgeKubo keeps its current Autosteer curriculum, Kubota equipment, camera system, and modern interface.
Best Transfer Candidates
ForgeKubo already has camera switching, an Autosteer lesson, field overlay, attachment selection, fault injection, and scoring. These additions make the experience feel less like one feature demo and more like a complete operator session.
ForgeFarm keeps one next action visible, names the key, and advances only when the world state proves completion.
KUBO VALUE: lower onboarding frictionDetached, attached, folded, lowered, active, and incompatible states turn implement setup into actual procedure.
KUBO VALUE: procedural competenceSpeed, fuel, operating mode, field state, implement state, and time remain visible without opening a menu.
KUBO VALUE: cause-and-effect clarityA small map, current field, landmarks, coverage percentage, overlap, and missed strips provide spatial purpose.
KUBO VALUE: measurable field skillReplace the farm economy with trainer-assigned jobs: setup, coverage, fault recovery, attachment swap, and assessment.
KUBO VALUE: repeatable curriculum loopInteractive Example
Each prompt is scoped as a small, testable vertical slice. It asks ForgeBot to inspect both live apps, preserve Kubo’s current behavior, implement the feature, and verify the deployed journey.

Stop inside the Equipment Yard, align the hitch, then connect the implement.
Prompt Anatomy
Point to the exact ForgeFarm behavior to study, not “make Kubo more game-like.”
Specify what changes: farm contracts become training missions; crop yield becomes coverage quality.
Keep Kubo’s camera controls, field overlay, attachment choices, lesson state, and visual language intact.
Require the complete live journey, responsive checks, state transitions, console review, and deployed verification.