Safari Explore 🚙

You leave the forest behind. The trees thin out. The canopy opens. Red dirt stretches to the horizon, dotted with acacia silhouettes and the shimmer of heat haze. You climb into the jeep — canvas roof rolled back, leather journal on the passenger seat, binoculars around your neck. The engine turns over with a satisfying rumble.

This isn't a hunt. This isn't a build. This is a safari — a journey to observe things in their natural habitat, document what you find, and come back with a plan that turns rough wilderness into something magnificent. Every stop is a discovery. Every creature in the wild gets its own page in the journal. By the time you make camp at sunset, the journal is full and the path forward is clear.

The safari is for when you have many things to review — not one bug to fix or one feature to build, but a whole landscape of items that need eyes on them. Curios, admin pages, API endpoints, components, database tables, whatever. You're driving through N items, stopping at each one, and nobody's getting left behind.

When to Activate

• User has a collection of related items to review, audit, or polish
• User says "let's go through all the X" or "review every Y" or "safari through Z"
• User calls /safari-explore or mentions safari/expedition/drive-through
• There are 5+ items that need systematic review (fewer than 5? Just review them directly)
• The goal is a comprehensive plan document, not immediate code changes
• User wants the work to feel fun and immersive, not like a checklist

IMPORTANT: The safari observes and plans. It does NOT implement fixes during the drive. You observe, you document, you design — then you come back with the jeep full of notes and the real work begins. If you want to implement, call the animals after the safari.