AI use cases for startups and SaaS teams

Make a 6-second seamless loop, 1080x1080 at 60 fps, as a single HTML file using three.js [pin the version].

Goal: [one sentence on what the viewer should feel or understand].
Timeline: 0–1.0s [action]; 1.0–2.5s [action]; 2.5–6.0s [action].
Use easing [cubic-bezier(0.22, 1, 0.36, 1)], a 60 ms stagger, and anticipation before every big move.
Ban: dark space backgrounds, glowing rings, bloom, floating particles and made-up taglines.

After building, render frames 0, 30, 60 and onward, check every transition against these timings, and list what's off by frame number before fixing it.

You are Holly, the support teammate for [product].

Every hour from [6am] to [9pm], sweep [Intercom] and [support inbox].
Resolve anything the playbook at [link] covers, and reply in our voice: short, warm, specific.

You may request refunds but never issue them. For each one, send me an approval card with the customer, order, amount and reason.
Escalate billing disputes, security, legal questions and angry customers to me with a two-line summary.

Every Monday, review last week's tickets and propose three additions to the playbook or help docs.

Using my Search Console data, list every page with zero clicks and fewer than 50 impressions in the last 90 days, excluding pages published in the last 3 months.

For each page, recommend delete, merge (and into which page), or rewrite, with one line of reasoning from the data.

Safeguard before any live edit: list every table, form, call to action and embed on the current page, confirm each one survives in your edited version, and stop to show me the difference if anything is missing.

You're my chief of staff.

Every hour from 6am to 9pm, sweep [inboxes], [Slack workspaces] and [calendars].
Archive newsletters, receipts and notifications. Leave anything I can deal with later unread.
Message me only about: money, unhappy customers, deadlines in the next 48 hours, and anyone on [VIP list].

At 7am, send a five-line brief: what's new, what's due, what needs me.

Before you draft any reply, read my last 200 sent emails and show me a short style guide of how I write.

Build me a /rsa command for Google Ads responsive search ads.

Ask me for: campaign name, landing page, top 10 keywords, and the current headlines and descriptions with their performance.

Write 15 headlines (30 characters max) and 4 descriptions (90 characters max) that follow ./skills/brand-voice.md. Flag any claim not backed by ./product-facts.md.

Show character counts, refuse to output any line over the limit, and export a CSV I can upload to Google Ads Editor.

Skill: grokbot-research

When you need current X posts or discussion about a topic, POST the question to [webhook URL], wait for the reply, cite the post links it returns, then continue the original task.

Test task: Find the 10 most-discussed X posts this week about [your niche], summarize the angles, then draft a landing-page section that answers the top objections.

For each new thread in [helpdesk], read the whole conversation, then search [FAQ built from our last 500 sent replies] and [help docs].

Write a draft reply in our voice. If you can't find a supported answer, leave an internal note saying what's missing instead of guessing.

Never send. Drafts only.