skill-gallery

Landing page de SaaS

Una página de marketing para Rotaline, una herramienta ficticia de planificación de guardias: sección hero con una ilustración del producto, funcionalidades, pasos, resultados, testimonios, precios con selector mensual/anual, preguntas frecuentes y pie de página.

prompts/landing-saas.md · versión 1. Todos los skills lado a lado: cada columna es un skill y cada fila, un agente.

Texto del prompt

En inglés, tal como se envió a los agentes. No se traduce.

Build a marketing landing page for Rotaline, a fictional SaaS product. Rotaline is an on-call scheduling and shift handoff tool for engineering teams of 5 to 50 people. It replaces spreadsheets and chat threads for deciding who is on call, and it makes sure the next person knows what happened during the previous shift.

## Sections and content

1. **Header.** Wordmark "Rotaline". Navigation links: Features, How it works, Pricing, FAQ. A "Sign in" link and a "Start free trial" button. On small screens the navigation must still be reachable.

2. **Hero.** Headline: "Know who's on call. Hand off without losing the thread." Supporting line: "Rotaline builds fair on-call rotations, routes alerts to the right person, and turns every shift change into a written handoff." Two calls to action: "Start free trial" and "See how it works". Include an illustration of the product (a schedule view with a few named shifts) made with inline SVG or HTML/CSS.

3. **Customer strip.** Label: "On-call teams at these companies use Rotaline". Five fictional company names: Northgate Labs, Plinth, Corvid Systems, Halden Bank, Murmur.

4. **Features.** Six features, each with a title and a one or two sentence description:
   - Rotation builder: daily, weekly or follow-the-sun rotations across time zones.
   - Swaps and overrides: request a swap in two clicks; the team lead approves it from email or chat.
   - Escalation policies: multi-step escalation by push notification, SMS and phone call.
   - Handoff notes: a structured note at every shift change, with open incidents carried over automatically.
   - Calendar sync: shifts appear in Google Calendar, Outlook or any iCal client.
   - Fairness report: on-call hours per person, including nights and weekends, so load stays even.

5. **How it works.** Three numbered steps:
   1. Connect your alerting tools with a webhook or one of 40 built-in integrations.
   2. Build a rotation and an escalation policy for each service.
   3. Hand off at the end of each shift; Rotaline reminds the outgoing person and notifies the incoming one.

6. **Results.** Three figures with labels: "38% fewer missed pages", "4 min median time to acknowledge", "2,100 teams on Rotaline".

7. **Testimonials.** Three quotes, each with a name, role and company:
   - "We used to argue about who covered the holidays. Now the fairness report settles it before anyone asks." (Dana Whitfield, Engineering Manager, Plinth)
   - "The handoff note is the feature I didn't know I needed. I start every shift knowing what's still burning." (Ravi Menon, Site Reliability Engineer, Halden Bank)
   - "Setting up follow-the-sun across three offices took one afternoon." (Sofia Brandt, Head of Infrastructure, Corvid Systems)

8. **Pricing.** A monthly / annual billing toggle that updates the displayed prices. Three plans:
   - Free: $0. Up to 5 users, 1 rotation, push and email alerts.
   - Team: $9 per user per month billed monthly, $7 billed annually. Unlimited rotations, SMS and phone alerts, handoff notes, calendar sync. Mark this plan as the most popular.
   - Business: $16 per user per month billed monthly, $13 billed annually. Everything in Team plus SSO/SAML, audit log, fairness report, 99.95% uptime SLA.
   Each plan has a call-to-action button.

9. **FAQ.** Five questions with answers that expand and collapse:
   - Can I import my existing schedule from a spreadsheet?
   - What happens if nobody acknowledges an alert?
   - Do you charge for SMS and phone calls?
   - Can contractors or people outside my company be on a rotation?
   - How does the free trial work?
   Write a short answer (one to three sentences) for each.

10. **Final call to action.** Text: "Start a 14-day free trial. No credit card required." An email input and a "Start free trial" button.

11. **Footer.** Four link columns: Product (Features, Pricing, Integrations, Changelog), Company (About, Careers, Contact), Resources (Docs, Status, Blog), Legal (Privacy, Terms). Copyright line: "© 2026 Rotaline, Inc." Links may point to `#`.

## Output requirements

- Write exactly one file named `index.html` in the current working directory. Put all HTML, CSS and JavaScript in that file.
- Do not reference remote images. Any images, icons or illustrations must be inline SVG or CSS.
- You may load fonts from Google Fonts and JavaScript or CSS libraries from well-known public CDNs (for example cdnjs, jsDelivr or unpkg).
- The page must work when `index.html` is opened directly from disk, and it must be usable at both desktop (1440px wide) and mobile (390px wide) viewport widths.
- All visible text is in English. Use the names, numbers and copy given above; write any additional copy a section needs.
- Do the whole task in one pass. Do not ask questions; make your own decisions and finish with the file written.

Las celdas con skill añaden una frase al final: Use the <name> skill. (Claude Code) o Use the $<name> skill. (Codex).

Nativo
Codex

Codex nativo

OK
Codex · nativo — Landing page de SaaS, captura (Escritorio, parte superior de la página)Codex · nativo — Landing page de SaaS, captura (Móvil, parte superior de la página)
Modelo
gpt-6.1-sol · high
Tiempo
7m 51s
Tokens
in 424k · out 24.5k
Skill usado
n/a
Recursos externos
fonts.googleapis.com, fonts.gstatic.com
Fecha de ejecución
2026-10-25

a11y · grave: 1▶ vídeo

👍 0 · Votar

Codex + frontend-design

OK
Codex + frontend-design — Landing page de SaaS, captura (Escritorio, parte superior de la página)Codex + frontend-design — Landing page de SaaS, captura (Móvil, parte superior de la página)
Modelo
gpt-6.1-sol · high
Tiempo
7m 57s
Tokens
in 370k · out 23.5k
Skill usado
Sí
Recursos externos
fonts.googleapis.com, fonts.gstatic.com
Fecha de ejecución
2026-10-25

a11y · grave: 1▶ vídeo

👍 0 · Votar

Codex + ui-ux-pro-max

OK
Codex + ui-ux-pro-max — Landing page de SaaS, captura (Escritorio, parte superior de la página)Codex + ui-ux-pro-max — Landing page de SaaS, captura (Móvil, parte superior de la página)
Modelo
gpt-6.1-sol · high
Tiempo
7m 14s
Tokens
in 462k · out 22.0k
Skill usado
Sí
Recursos externos
fonts.googleapis.com, fonts.gstatic.com
Fecha de ejecución
2026-10-25

a11y · grave: 1▶ vídeo

👍 0 · Votar

Codex + web-design-engineer

OK
Codex + web-design-engineer — Landing page de SaaS, captura (Escritorio, parte superior de la página)Codex + web-design-engineer — Landing page de SaaS, captura (Móvil, parte superior de la página)
Modelo
gpt-6.1-sol · high
Tiempo
7m 02s
Tokens
in 330k · out 22.0k
Skill usado
Sí
Recursos externos
fonts.googleapis.com, fonts.gstatic.com
Fecha de ejecución
2026-10-25

a11y · grave: 1▶ vídeo

👍 0 · Votar

Codex + taste-skill

OK
Codex + taste-skill — Landing page de SaaS, captura (Escritorio, parte superior de la página)Codex + taste-skill — Landing page de SaaS, captura (Móvil, parte superior de la página)
Modelo
gpt-6.1-sol · high
Tiempo
7m 15s
Tokens
in 890k · out 23.1k
Skill usado
Sí
Recursos externos
fonts.googleapis.com, fonts.gstatic.com
Fecha de ejecución
2026-10-26

a11y · grave: 2▶ vídeo

👍 0 · Votar

Codex + frontend-ui-engineering

OK
Codex + frontend-ui-engineering — Landing page de SaaS, captura (Escritorio, parte superior de la página)Codex + frontend-ui-engineering — Landing page de SaaS, captura (Móvil, parte superior de la página)
Modelo
gpt-6.1-sol · high
Tiempo
9m 28s
Tokens
in 886k · out 24.2k
Skill usado
Sí
Recursos externos
fonts.googleapis.com, fonts.gstatic.com
Fecha de ejecución
2026-10-26

a11y · grave: 1▶ vídeo

👍 0 · Votar

Codex + theme-factory

OK
Codex + theme-factory — Landing page de SaaS, captura (Escritorio, parte superior de la página)Codex + theme-factory — Landing page de SaaS, captura (Móvil, parte superior de la página)
Modelo
gpt-6.1-sol · high
Tiempo
5m 57s
Tokens
in 221k · out 20.8k
Skill usado
Sí
Recursos externos
fonts.googleapis.com, fonts.gstatic.com
Fecha de ejecución
2026-10-26

a11y · grave: 1▶ vídeo

👍 0 · Votar

Claude Code

Claude Code nativo

OK
Claude Code · nativo — Landing page de SaaS, captura (Escritorio, parte superior de la página)Claude Code · nativo — Landing page de SaaS, captura (Móvil, parte superior de la página)
Modelo
claude-opus-5-5 · high
Tiempo
7m 11s
Tokens
in 30 · cache 873k · out 37.6k
Skill usado
n/a
Recursos externos
fonts.googleapis.com, fonts.gstatic.com
Fecha de ejecución
2026-10-26

a11y · grave: 1▶ vídeo

👍 0 · Votar

Claude Code + frontend-design

OK
Claude Code + frontend-design — Landing page de SaaS, captura (Escritorio, parte superior de la página)Claude Code + frontend-design — Landing page de SaaS, captura (Móvil, parte superior de la página)
Modelo
claude-opus-5-5 · high
Tiempo
17m 23s
Tokens
in 66 · cache 2.51M · out 51.7k
Skill usado
Sí
Recursos externos
fonts.googleapis.com, fonts.gstatic.com
Fecha de ejecución
2026-10-26

a11y · grave: 1▶ vídeo

👍 0 · Votar

Claude Code + ui-ux-pro-max

OK
Claude Code + ui-ux-pro-max — Landing page de SaaS, captura (Escritorio, parte superior de la página)Claude Code + ui-ux-pro-max — Landing page de SaaS, captura (Móvil, parte superior de la página)
Modelo
claude-opus-5-5 · high
Tiempo
13m 48s
Tokens
in 76 · cache 3.78M · out 59.1k
Skill usado
Sí
Recursos externos
fonts.googleapis.com, fonts.gstatic.com
Fecha de ejecución
2026-10-26

a11y: sin problemas detectados▶ vídeo

👍 0 · Votar

Claude Code + web-design-engineer

OK
Claude Code + web-design-engineer — Landing page de SaaS, captura (Escritorio, parte superior de la página)Claude Code + web-design-engineer — Landing page de SaaS, captura (Móvil, parte superior de la página)
Modelo
claude-opus-5-5 · high
Tiempo
8m 54s
Tokens
in 32 · cache 1.19M · out 54.4k
Skill usado
Sí
Recursos externos
fonts.googleapis.com, fonts.gstatic.com
Fecha de ejecución
2026-10-26

a11y · grave: 1▶ vídeo

👍 0 · Votar

Claude Code + taste-skill

OK
Claude Code + taste-skill — Landing page de SaaS, captura (Escritorio, parte superior de la página)Claude Code + taste-skill — Landing page de SaaS, captura (Móvil, parte superior de la página)
Modelo
claude-opus-5-5 · high
Tiempo
15m 57s
Tokens
in 64 · cache 3.59M · out 83.5k
Skill usado
Sí
Recursos externos
fonts.googleapis.com, fonts.gstatic.com +1
Fecha de ejecución
2026-10-26

a11y: sin problemas detectados▶ vídeo

👍 0 · Votar

Claude Code + frontend-ui-engineering

OK
Claude Code + frontend-ui-engineering — Landing page de SaaS, captura (Escritorio, parte superior de la página)Claude Code + frontend-ui-engineering — Landing page de SaaS, captura (Móvil, parte superior de la página)
Modelo
claude-opus-5-5 · high
Tiempo
9m 56s
Tokens
in 50 · cache 2.13M · out 61.5k
Skill usado
Sí
Recursos externos
fonts.googleapis.com, fonts.gstatic.com
Fecha de ejecución
2026-10-26

a11y: sin problemas detectados▶ vídeo

👍 0 · Votar

Claude Code + theme-factory

OK
Claude Code + theme-factory — Landing page de SaaS, captura (Escritorio, parte superior de la página)Claude Code + theme-factory — Landing page de SaaS, captura (Móvil, parte superior de la página)
Modelo
claude-opus-5-5 · high
Tiempo
6m 13s
Tokens
in 36 · cache 967k · out 37.4k
Skill usado
Sí
Recursos externos
fonts.googleapis.com, fonts.gstatic.com
Fecha de ejecución
2026-10-26

a11y · grave: 1▶ vídeo

👍 0 · Votar