How to split a bloated AI agent prompt into modular skills and use a fast Decision Model to route only the instructions and tools each user question actually needs.

When you build an AI assistant for a web application — say, an Online Travel & Flight Booking Assistant — it always starts simple. You write a short system prompt and attach one or two tools, like search_bookings and cancel_booking .

Fast-forward a few months. Your assistant now supports searching flights, switching UI tabs, applying multi-field filters, downloading boarding passes, checking refund eligibility, rebooking flights, and answering baggage policy questions.…