Design System Component Spec Writer for Figma Handoff
Produces a developer-ready component specification covering anatomy, variants, states, tokens, accessibility, and open questions from a short component brief.
341 prompts · last added
272 results for “do not invent claims” · page 2 of 12
Produces a developer-ready component specification covering anatomy, variants, states, tokens, accessibility, and open questions from a short component brief.
Matches your existing resume to one job description: keyword gap table, rewritten bullets that use only your real experience, and a list of requirements you cannot honestly claim.
Turns a client's rough notes into a structured design brief with goals, audience, deliverables, constraints, references to gather and measurable success criteria.
Summarizes an uploaded long video or PDF with timestamp or page citations, then lists key claims with evidence and action items.
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.
A five-minute end-of-day check that records what got done, captures loose ends, and picks three priorities for tomorrow so you can stop thinking about work.
Combines your Docs, Sheets, meeting notes, and outside sources into one decision memo. Separates internal evidence from external research and logs conflicts, gaps, and next actions.
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.
Writes a first-person LinkedIn About section from your background: what you do, for whom, proof, and how to reach you, in under 1,500 characters with three opening options.
Extracts decisions, owned and dated action items and open questions from meeting notes, then drafts a follow-up email.
Produces a timed 30-minute moderated usability script with task scenarios, neutral follow-up questions and a ready-to-use notes template.
Turns pasted links and notes into a newsletter issue with a hooking intro, three takeaway sections, and one call to action.
Organizes rough symptom notes into a dated timeline and a prioritized question list for your appointment, without any diagnosis.
Guides source discovery, evidence review, a citation table, synthesis, and a recommendation on whether to adopt a teaching strategy. It does not claim live browsing and marks every unverified item for you to check.
Produces a least-privilege tool inventory, function definitions, and approval rules for an agent that calls APIs or internal systems.
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.
Breaks a pasted paper abstract or text into claim, method, key evidence and limitations, then adds three seminar discussion questions.
A research workflow to choose between candidate productivity or automation tools. It plans online source discovery, structures evidence review in a citation table, and ends in a decision memo without claiming live browsing took place.
Turns a list of links and your quick takes into a readable newsletter issue with a subject line, an opening, short summaries and your own angle on each item.
Builds a day-by-day revision timetable counted back from your exam date, with practice tests, review days and buffer days sized to the hours you really have.
Converts discovery notes into a one-page proposal executive summary and a dated mutual action plan. It helps a rep decide whether the deal is ready to propose and what is still missing.
Converts raw meeting notes or a transcript into a decision log, an action tracker with owners and dates, and a list of open questions. It separates what was stated from what was inferred, so follow-up is unambiguous.
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 Claude Code to build or refactor a dependency-aware DAG scheduler for agent phases, with cycle validation, bounded parallelism, join policies, retries, and an append-only run ledger so interrupted runs resume without redoing finished nodes.
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.