Airy Flight Booking Landing
Busca primero. Respira. Reserva
Diseña una landing de reserva de vuelos ligera y espaciosa: buscador a la vista en la primera pantalla, tarifas completas y honestas, y señales de confianza en el orden en que de verdad preocupan a los viajeros.

Instálala en 3 pasos
Sin registro. Sin herramientas CLI. Elige tu IA, copia una línea y pégala.
¿Prefieres hacerlo tú mismo? Compra la habilidad ($4.99), descarga el ZIP desde la confirmación de compra, descomprímelo en el directorio que se muestra arriba y reinicia tu sesión de IA — el mismo resultado. ¿Ya la compraste? Tu asistente de IA puede descargarla por ti.
Qué incluye
Un SKILL.md (la guía paso a paso) + una plantilla inicial. Una vista previa:
Airy Flight Booking Landing
When to use
- You are launching or redesigning a flight booking page and visitors bounce before they ever search
- Your current landing page buries the search box under banners, pop-ups, and marketing copy
- You want a page that feels calm and spacious — generous whitespace, one clear action — instead of a wall of deals
- You need to show fares and trust signals without resorting to fake urgency or countdown timers
- Your booking flow starts on a landing page that must work as well on a phone as on a desktop
Workflow
- Put search first (input: booking flow → output: hero section)
The hero is the search box, full stop. Origin, destination, dates, passengers, one search button — visible without scrolling, on every screen size. The headline above it says one thing: what the traveler can do here. Everything else — deals, destinations, testimonials — lives below the search, because a visitor who came to search should never have to hunt for the search. - Show fares honestly (input: fare data → output: fare display)
Display fares with the full price a traveler will actually pay, including the fees and taxes you know about, and label what is included. Show a small set of real example fares ("London → Lisbon from £X") drawn from actual inventory or a clearly labeled typical range — never a teaser price no one can book. If a fare is an estimate, say so next to the number. - Build trust in order (input: policies + support facts → output: trust section)
Place trust signals in the order a traveler worries: what happens if plans change (change/cancellation terms in plain words), how payment works and what protection applies, and how to reach a human (support hours and channels). Each claim must be verifiable on your own site — link to the policy page it comes from. A trust badge you cannot explain is decoration, not trust. - Keep the page light (input: full content → output: laid-out page)
Lay out with air: generous whitespace, one idea per section, short lines, one typeface family with two or three weights. Use real destination photography or clean illustration — one strong image per section, not a collage. Every section must justify its place: if removing it would not change a visitor's decision, remove it. - Verify the journey (input: finished page → output: tested page)
Walk the page as a traveler: search, see results, reach the booking step, find the cancellation terms, and reach support — on a phone and on a desktop, on a slow connection. Check load time, check that the search box works with a keyboard alone, and check that every price on the page matches what the booking flow shows. Fix mismatches before launch; a fare that changes between landing page and checkout is the fastest way to lose a booking and a reputation.
Vista previa de la plantilla
Airy Flight Booking Landing — Page Template
One page = one search box above the fold. Fill in real fares and real policies before layout.
Page: {site / route focus}
Hero headline (one thing the traveler can do here): {headline} Reassurance line (one, under the search box): {e.g. change terms in plain words — linked}
Search hero (above the fold, every screen size)
Checks: [ ] Visible without scrolling | [ ] Keyboard-operable | [ ] Every field labeled | [ ] No pop-up covers the search box
Example fares (real inventory or labeled typical ranges)
El paquete de la habilidad (SKILL.md + plantilla) está escrito en inglés.


