Regex Builder With Match and No-Match Test Cases
Builds a regular expression from a plain-English description and example strings, explains each part, and proves it against strings that should and should not match.
341 prompts · last added
276 results for “handwritten text at the bottom” · page 2 of 12
Builds a regular expression from a plain-English description and example strings, explains each part, and proves it against strings that should and should not match.
Gives tough, rubric-based feedback on an essay with specific line references and questions to fix each problem, while refusing to rewrite the essay for you.
Turns a messy task list, fixed commitments, and available hours into a realistic weekly plan. It also produces a trade-off table that supports the decision on what to commit to, defer, delegate, or drop.
Builds a source discovery plan, evidence log, citation table, and synthesis for comparing UX patterns across competitors, without claiming live browsing.
Sorts a pasted bank export into spending categories, shows where the money went, and builds a zero-based budget where every unit of income gets a job.
Calculate a sustainable hourly and project rate from your income target and billable hours, covering tax, unpaid admin time and expenses with the math shown.
Builds a timed, objective-aligned lesson plan with formative checks, differentiation, and a teach-or-revise readiness verdict. It asks for missing inputs first and keeps assumptions separate.
Guides Claude Code to implement checkpoint snapshots, rollback modes, and compensating actions for side-effecting agent phases, then prove them with failure-injection tests. Helps you decide the rollback strategy per phase.
Has Claude Code define schema-based handoff contracts between agent phases, generate a validator, and add contract tests. Supports the decision of which phase boundaries need strict contracts versus lightweight checks.
Rewrites text that sounds machine-generated by removing the specific tells, like stock words and forced triads, while keeping every claim and the meaning.
Lists the questions buyers ask AI assistants about your product category, checks which sources those answers lean on, and plans the pages and facts you need to be cited.
Converts a successful chat transcript into a reusable prompt template with at most three named variables and a one-line note on when to use it.
Audits an existing multi-agent pipeline for failure modes and produces retry limits, fallback paths, escalation triggers, and a test plan. Supports the decision on what to harden before wider rollout.
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.
Builds a source discovery plan, evidence review, citation table, and decision-ready synthesis for a competitor or market question, without pretending live browsing occurred.
Writes a sincere apology for a mistake at work or in personal life that names what happened, owns the impact, avoids excuses and says what changes next.
Produces an onboarding guide for one folder of a codebase: what it does, how data moves through it, the files to read first and the traps a new developer should avoid.
Builds a one-page cheat sheet of your ten most likely sales objections, each with the real concern behind it, a question to ask back, a short answer, and proof to share.
Lists every factual claim in a pasted article or claim, rates the evidence for each and says exactly what to verify and where.
Turns your source material into a diagnostic quiz with an answer key, a misconception map, and a reteach plan. It helps you decide who needs review and what to reteach.
Audits an existing or planned onboarding email flow, then rewrites it around a single activation event with segmentation, timing, copy, and a measurement plan.
Runs a behavior-preserving refactor in Codex exec. It pins current behavior with characterization tests, refactors in small verified steps inside an allowed scope, and ends with an evidence-based handoff for the merge decision.
Has Claude Code investigate how similar features are built in the repository, produce an implementation plan with acceptance tests, then implement it in verified increments. Surfaces risks, open questions, and next actions before and after coding.
Writes a ready-to-deploy orchestrator system prompt that delegates to your workers, tracks progress in a ledger, merges results and stops on defined conditions.
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.