Positioning Statement and Messaging Hierarchy for a Product Launch
Turns product facts, audience insight, and competitor context into a positioning statement, messaging hierarchy, and proof map so a team can approve one launch angle.
341 prompts · last added
83 results for “custom-commands” · page 2 of 4
Turns product facts, audience insight, and competitor context into a positioning statement, messaging hierarchy, and proof map so a team can approve one launch angle.
Runs a read-only Codex investigation that maps the relevant code paths, test commands, and likely root causes for a bug report. It ends with a ranked hypothesis table and a go/no-go recommendation before any edits.
Plans and executes a library or framework version migration in Cursor in small, verifiable batches, with an impact inventory, rollback points, and per-batch test gates instead of one risky bulk edit.
Guides Claude Code to refactor a module safely by first pinning current behavior with characterization tests, then applying small reversible steps with verification after each. Delivers a diff, risk register, and rollback plan.
Turns a side-business idea into a one-page plan: customer, offer, price, channel, costs, and the cheapest 30-day test that would prove people will pay.
Compares competitor homepage copy with your positioning to map overlap, find unclaimed angles, and propose one sharper differentiating line.
Converts your pasted Cursor .mdc rules into a single AGENTS.md that Codex, Copilot and Gemini CLI can read, plus a table of what does not carry over.
Turns a raw feature or bug request into a paste-ready Codex task with a goal, constraints, files in scope, definition of done and exact verification commands.
Analyzes a recurring manual task and produces an automation blueprint with trigger, steps, data mapping, error handling, and a test plan. It also helps you decide whether the task is worth automating at all.
A ready-to-save SKILL.md that makes your coding agent write Conventional Commits messages and pull request descriptions from the staged diff, never from guesses.
Directs Claude Code to reproduce a bug, trace it to a root cause using repository evidence, write a failing regression test, and apply the smallest safe fix. Ends with a verified diff, risks, and next actions.
Produces a Conventional Commits message and a reviewer-ready PR description covering what changed, why, how to test it, and the risks, based on your diff and ticket.
Turns the changes in a branch into a clear pull request description: what changed and why, how to test it, risks and screenshots to add, in your repo's template if it has one.
Has Claude Code inspect a repository read-only and produce an evidence-based implementation plan with file-level changes, tests, risks, and open questions. Use it to decide whether to start, split, or clarify a feature before any code is written.
Builds a transparent market size estimate from discoverable sources, compares top-down and bottom-up methods, and flags weak assumptions before a go or no-go call.
Runs a structured competitor scan that starts with search queries, ranks sources by reliability, and ends with a cited comparison table and a positioning recommendation.
Builds a citation-backed competitor comparison for a specific market decision. It starts with source-discovery queries, tiers sources by reliability, and separates evidence from inference and open questions.
Guides Cursor Agent through reproducing a bug, isolating the root cause with evidence, applying a minimal diff, and adding a regression test, ending with a verification checklist and risks.
Diagnoses where a workflow slows down using your process steps and metrics, then ranks causes and produces a 30-day improvement plan with owners, measures, and risks.
Build a research plan that shows where to find competitor evidence, how to judge sources, and how to log citations. It never claims live browsing happened, so you can verify each source yourself.
Guides Codex through reproducing a failing CI job locally, classifying the cause as code, test, environment, or flaky, applying a minimal fix when safe, and producing an evidence-based handoff for anything it cannot resolve.
Plans 30 days of posts that lead to one offer: content pillars, a mix of value, proof and ask posts, hooks for each day, and the platform and format to use.
Finds the most likely cause of an error from the message and the relevant code, ranks other possible causes, and gives the smallest fix plus a way to prove it worked.
Analyzes your brand copy samples and builds a reusable one-page voice brief with tone rules, banned words, example rewrites and a paste-ready instruction block.
Guide
Nothing that fits? Write a prompt with AI.
341 copy-ready prompts for productivity, writing, business and coding and more. Each one sets the role, the steps and the output format, and marks the parts you fill in with curly brackets.
Most are written for ChatGPT (285), Gemini (260), Claude (217) and Claude Code (42); the number is how many prompts list that tool. Each prompt page lists its tools, and most text prompts also work in any capable chat model.
Words in curly brackets, such as {audience}, are the parts you replace with your own details. Choose “Ready to use (no blanks)” in the filters to see prompts you can paste as they are.
By how often they are copied, unless you choose another order. Newest shows the latest additions first. Trending ranks prompts by copies, opens and saves over the last two weeks.
No. Every prompt is free to copy or open in your AI tool. A free account lets you save prompts to your vault.
Yes. Write with AI asks what you need, builds a short form for it, and writes the prompt as you fill it in.