Run the AI-news crew (scout, analyst, editor) to sweep the field with web search and ship a ranked briefing. Trigger when the user asks for an AI news brief, a daily or weekly AI roundup, "what shipped in AI", a model-release recap, or wants the standing cadence run.
Apply the OneWave design style (tokens + theme) to a frontend project. Trigger when the user asks to brand a site, apply the OneWave look, set up design tokens, theme an app, or fix off-brand colors and typography.
Use when the user wants to monitor, track, or compare competitors, their pricing pages, or their published content, and report what changed since the last check. Triggers on requests like "watch competitor X", "did their pricing change", "what did they ship", or "diff competitors against last time".
Use when the user wants to turn one source piece (blog post, transcript, doc, notes, or URL) into multiple channel-ready formats — posts, a thread, an email, and a video script. Triggers on "repurpose", "atomize", "turn this into", "make social content from", or "one piece into many".
Earnings-season prep for your holdings and watchlist -- report dates, what the market is actually watching per name, prior-quarter context, and a post-report debrief template. Preparation, not prediction. Use in the weeks around earnings season.
Analyze your actual holdings -- allocation, concentration, sector and theme overlap, correlated-risk flags, and the questions worth asking yourself. Works from a broker CSV export or a pasted list. Analysis only, never buy/sell advice.
One company on one page -- what the business actually does, how it makes money, recent results and guidance, valuation context, the honest bull and bear case, and the risks. Research support, not a recommendation. Use before buying, before earnings, or when a position needs a fresh look.
Scan official AI release notes, changelogs, and deprecation pages, then flag what affects the user's stack and recommend an action for each item. Trigger on requests like "what AI releases happened recently," "check if my models or tools are deprecated," "any changelog updates that affect my stack," or periodic…
Everything about one account on one page -- relationship history, stakeholder map, health signals, renewal clock, open items, and expansion openings. Use before QBRs, escalations, handoffs, or any executive ask of "where are we with X?".
Build a 15-minute pre-call brief for a sales meeting -- company research, attendee intel, tailored discovery questions, and the objections likely coming with answers ready. Use before any prospect or customer call.
Turn rough call notes or a transcript into the complete post-call package -- recap email in your voice, CRM-ready notes, and the next-step task list with dates. Use within an hour of hanging up, while it still counts.
Weekly pipeline hygiene in one pass -- surface stalled deals, name the missing next action on every open opportunity, and produce an honest forecast read. Use Monday morning or before any pipeline meeting.
Add a feature to an app you vibe-coded without breaking the three things that already worked -- read the existing patterns first, extend them instead of inventing a second way to do the same thing. Use when adding any new screen, flow, or capability to an existing codebase.
Plan and capture the demo or launch video for the app you just shipped -- the beat sheet, the clean capture setup, and the narration -- so it shows the product working instead of narrating a tour. Use after shipping, when the app needs a video for a landing page, launch post, or client handoff.
GSAP in a React or Next.js app without the leaks -- timelines over stacked tweens, useGSAP and context for cleanup, ScrollTrigger set up so it survives route changes and layout shifts. Use when building GSAP animations in a component-based app.
Make a vibe-coded app survivable by someone else -- an honest README, the decisions written down, the shortcuts listed, and a setup path a new developer can follow without you. Use before handing an app to a client, a contractor, a teammate, or your own future self.
Turn the demo into a product -- replace hardcoded arrays with a real database, stubbed sign-in with real auth, and the fake form with one that actually delivers. Use when an app looks finished but nothing it shows is true.
The small motion that makes an app feel built rather than generated -- hover, press, focus, toggles, loading, and state changes done as a consistent system in plain CSS. Use when UI feels static or lifeless, or when hover effects are scattered and inconsistent.
Find and fix animation jank -- the layout thrash, paint storms, and layer explosions that make motion stutter on real devices even when it is smooth on your laptop. Use when animations feel choppy, scroll stutters, or before shipping any animation-heavy page.
Define the app's motion language before animating anything -- a small set of durations, easings, and named moves that every animation draws from, so the app feels designed instead of decorated. Use before writing the first animation in a project, or when existing motion feels scattered.
Scaffold a new app from one sentence -- Next.js + TypeScript + Tailwind with a real design-token theme applied from the first commit, opinionated structure, and honest slots for auth and data. Use when starting any new project, prototype, or client build.
The de-AI pass -- audit a vibe-coded app for template smell in design and copy, then fix it with editorial layout, purposeful motion, and human-sounding words. Use after any build session, before anyone else sees it.
Build scroll-driven sections that feel authored rather than twitchy -- pinned scenes, scrubbed timelines, reveals, and parallax with the timing and cleanup that make them work on a phone. Use for landing pages, product tours, and any section where scrolling advances a narrative.
Pre-flight and deploy -- catch the classic day-one embarrassments (exposed keys, missing env vars, broken build, open endpoints), then ship to Vercel with domains and analytics wired. Use when the app is ready for other humans.