Infinite-Labs-AI

Use when writing or rewriting website copy: homepages, landing pages, pricing pages, product pages, feature pages, hero sections, headlines, subheads, CTAs, value propositions, taglines, and above-the-fold messaging. Do not use for email sequences, blog posts, longform X articles, or platform-specific ad copy.

Use when planning a product launch, feature release, waitlist, beta, public announcement, relaunch, Product Hunt-style push, repeated feature launch system, launch-week checklist, or multi-channel GTM rollout.

Use when writing or rewriting longform X/Twitter articles, X Articles, founder essays, launch essays, growth teardowns, product breakdowns, build-in-public stories, or sharp startup takes that need X-native hooks, tone, pacing, and structure. Use for X Articles and long posts, not blog SEO posts, lifecycle emails, or landing page copy.

Use when turning a marketing, growth, CRO, pricing, onboarding, email, ad, or acquisition idea into a useful experiment or test plan.

Use when optimizing a site or brand to show up in AI answers, LLM citations, AI search, product recommendations, and category answers.

Use when auditing, planning, or debugging marketing measurement, conversion tracking, GA4, GTM, UTMs, pixels, CRM attribution, funnel reporting, or dashboard trust.

Use when creating or improving B2B outbound, prospecting, cold email, LinkedIn outreach, account research, sales sequences, or founder-led direct outreach.

Use when researching competitors, alternatives, market gaps, win-loss themes, comparison pages, battlecards, pricing, or messaging.

Route and execute unknown-discovery workflows before, during, or after implementation. Use when a user asks for a blindspot pass, unknown unknowns, "what am I missing", domain vocabulary bootstrapping, design directions, mock-before-wire artifacts, codebase-grounded brainstorms, one-question-at-a-time interviews, reference semantics maps, tweakable plans, implementation notes, buy-in docs, merge quizzes, or interactive review artifacts/HTML artifacts that expose assumptions and capture human decisions.

Surface unknown unknowns before touching unfamiliar code or systems. Use when the user asks for a blindspot pass, "what am I missing", hidden traps, implementation risks, prompt hardening, or wants Codex to inspect a module/repo area before writing code.

Package completed work into a stakeholder buy-in/sign-off artifact. Use when the user asks for a pitch doc, sign-off doc, Slack-ready summary, rollout package, objection handling, or a review artifact that leads with demo/evidence and names who must approve what.

Generate multiple incompatible product/UI/design directions so the user can discover taste by reaction. Use when the user says they have no visual taste, will know it when they see it, wants 3-4 directions, wants alternatives before committing, or needs an interactive review artifact for design choices.

Teach the user enough domain vocabulary and mental models to prompt accurately. Use when the user says they do not understand a domain, lacks the right words, asks to learn their unknown unknowns, or needs practitioner vocabulary before asking Codex to do unfamiliar work.

Keep a durable implementation-notes/deviation log while building. Use when the user asks to log surprises, preserve deviations from a plan, keep implementation notes, pick conservative options and continue, or capture unknowns discovered during execution for a later attempt.

Expand a known problem into a codebase-grounded intervention space. Use when the user knows the outcome problem but not the best fix, asks to brainstorm interventions, wants options from cheapest to most ambitious, or wants Codex to search the repo for leverage points before choosing a plan.

Verify understanding of a diff or completed change before merge. Use when the user asks to be quizzed before merging, wants to ensure they understand what changed, needs a merge-readiness report, or wants an artifact that tests comprehension and points wrong answers back to the relevant explanation.

Use when the user asks for terminal, CLI, ASCII, ANSI, dashboard, leaderboard, chart, visualization, visual idea, or new visual output for local health, wearable, calendar, email, food, workout, sleep, stress, recovery, or readiness data. Select an existing CLI visual by semantic intent, or design a new privacy-safe first-pass CLI visual spec and mockup in the same answer.

Use for health questions about sleep, stress, exercise, activity, workouts, steps, food, meals, eating, calories, energy, fatigue, readiness, recovery, HRV, resting heart rate, SpO2, or forward planning with health context.

Use for health questions about sleep, stress, exercise, activity, workouts, steps, food, meals, eating, calories, energy, fatigue, readiness, recovery, HRV, resting heart rate, SpO2, or forward planning with health context.