35 Claude Prompts for Google Docs

<context>[Paste the full doc.] It is [current] words and has to come in under [target] words. Every number, name, date, and commitment has to survive the cut.</context> <task>Trim it. Remove throat clearing, repeated context, and any sentence that only restates the heading above it.</task> <format>The trimmed doc first, then a list of what you removed grouped by reason, so I can restore anything you judged wrong.</format>

<context>[Paste the doc.] It was written for [original audience] and now has to be read by [new audience, for example the finance team or a customer].</context> <task>Rewrite it so the new audience gets it on one read, without stripping out the substance.</task> <format>Same headings. Replace jargon with plain wording, define any term that has to stay in a parenthesis at first use, and end with a list of every term you kept and why.</format>

<context>Here are two documents my team wrote that people responded well to: [paste both]. Here is my new draft: [paste].</context> <task>Rewrite my draft so it reads like it came from the same team.</task> <format>The rewritten draft, then a style note listing the specific patterns you matched: sentence length, how we open sections, how we deliver bad news, words we use, words we avoid.</format>

<context>[Paste the doc.] It is a [doc type] where somebody has to be accountable for each action described.</context> <task>Find every passive construction and every hedge such as 'we may want to consider', and rewrite them with a named actor and a direct verb.</task> <format>A table of original sentence, rewrite, and the actor you assigned. Where you cannot tell who the actor is, write UNKNOWN OWNER rather than guessing a name.</format>

<context>[Paste the full doc.] The reader is [role] and will read the first screen only before deciding whether to keep going.</context> <task>Write an executive summary that stands completely alone: the ask, the recommendation, the three reasons, the cost, and the main risk.</task> <format>Under 150 words, no bullet longer than two lines, the ask in the first sentence. Then a second version at half that length for a chat message.</format>

<context>[Paste the doc.] I think it argues [your intended argument], but I have read it too many times to judge.</context> <task>Ignore my stated intent and reverse outline it: for each section, write the one claim it actually makes and the evidence it actually provides.</task> <format>A numbered list in section order, then a verdict on where the real argument drifts from my intended one and which section is doing the least work.</format>

<context>[Paste the doc.] House style: product names are [list], we write [term] and never [variant], dates use [format], numbers over [threshold] use [convention].</context> <task>Find every inconsistency in terminology, capitalization, product naming, date format, and number format.</task> <format>A find and replace table with three columns: exact current text, exact replacement text, number of occurrences. Do not return a rewritten document.</format>

<context>[Paste the comment threads, including who wrote what and any replies.] The doc is [name] and I have to close the review by [date].</context> <task>Turn every thread into something I can act on: what is being asked, whether it is a fact fix, an opinion, or a scope change, and what I should do about it.</task> <format>A table of commenter, thread summary, type, recommended action, and whether it can be resolved without a reply. Sort it so the fact fixes come first.</format>

<context>[Paste the open comments together with the paragraphs they are attached to.] These reviewers are my [peers / manager / client], and I disagree with [which ones].</context> <task>Draft one reply per comment: accept, accept with a modification, or decline with a reason.</task> <format>Under 40 words per reply, no apologies, and for every decline put the reason before the decline so it does not read as a brush off.</format>

<context>Version A: [paste]. Version B: [paste]. They were edited in parallel by different people and both contain changes worth keeping.</context> <task>Produce one merged document, and separate genuine contradictions from places where the two versions merely word the same thing differently.</task> <format>The merged doc first. Then a conflicts list with the passage, what A says, what B says, and which one you kept, so the two authors can settle the real disagreements themselves.</format>

<context>[Paste the doc.] I am editing somebody else's document and I want to leave suggestions rather than silent rewrites.</context> <task>Propose your edits as exact replacements instead of returning a rewritten document.</task> <format>A table of exact original text, exact replacement text, and a one line rationale I can paste as the suggestion comment. Keep each original snippet short enough to select in one drag.</format>

<context>[Paste the doc or its outline.] The reviewers are [names and roles] and I need their input back by [date].</context> <task>Write the request that goes out with the review, telling each reviewer which sections to read and what kind of feedback I want from them specifically.</task> <format>A short message per reviewer naming their sections, the question they should answer, and what to ignore. Then one line I can paste at the top of the doc stating the review deadline.</format>

<context>Feedback received: [paste it, for example 'this feels too long' or 'not sure about the framing']. Here is the doc it refers to: [paste].</context> <task>Translate each vague comment into two or three concrete edits that would satisfy it, and name the passage that probably triggered it.</task> <format>Grouped by comment: your interpretation, the likely trigger passage, the specific edits, and one clarifying question to send back if your interpretation is a guess.</format>

<context>Previous version: [paste]. Current version: [paste]. Stakeholders have already read the previous one and will not read the whole thing again.</context> <task>Explain what changed in terms of meaning rather than wording: what was added, what was removed, which commitment moved, and what a reader of the old version would now get wrong.</task> <format>Four short lists with those labels, then a two sentence change note I can send to everyone who read the old version.</format>

<context>[Paste the doc with its current headings marked by level.] People navigate it from the Docs outline pane and keep getting lost in the middle.</context> <task>Rebuild the heading hierarchy: correct the levels, make the phrasing parallel, and rewrite each heading so it states what the section concludes rather than what topic it covers.</task> <format>A before and after list of every heading with its level, plus a note on any section that has no heading and needs one, or has one and should be merged upward.</format>

<context>[Paste the section that reads as one dense block.] It contains [comparisons / sequential steps / criteria / options].</context> <task>Decide what belongs in a table, what belongs in a numbered list, what belongs in bullets, and what has to stay as prose. Then rewrite the section that way.</task> <format>Give tables as tab separated rows I can paste directly, and add one line per element explaining why that format suits that content.</format>

<context>[Paste the heading list of a doc that runs to [N] pages.] It is shared as a link and readers jump straight into the middle of it.</context> <task>Plan the navigation: which headings belong in the table of contents, which sections need a direct link people can share, and what each link should be called.</task> <format>A table of heading, include in the table of contents yes or no, suggested link text, and where else in the doc that link should appear inline.</format>

<context>[Paste the outline of the doc.] It has grown to [N] words and different readers only ever need different parts of it.</context> <task>Propose a split into separate documents with one parent hub doc, based on who reads what and how often each part changes.</task> <format>Per proposed doc: name, owner, contents, audience, update frequency, and which other docs it links to. Then the structure of the hub doc that ties them together.</format>

<context>[Paste the process section, currently written as prose.] It is followed by [role], usually under time pressure.</context> <task>Convert it into a checklist someone can tick through while doing the work, with every decision point made explicit.</task> <format>Numbered steps in checklist form, branch points written as If [condition], go to step [n], and a Verify block at the end listing how to confirm the work was done correctly.</format>

<context>[Paste the doc, and describe every image in it: what it shows and why it is there.] It will be shared outside my team.</context> <task>Audit it for accessibility: heading order, descriptive link text instead of 'click here', alt text for each image, table header rows, and any meaning carried by color alone.</task> <format>A findings table of issue, location, and the exact replacement text. Write the alt text for me rather than telling me to write it.</format>

<context>[Paste the doc and the list of sources with their URLs.] House reference style is [style, or state that there is none].</context> <task>Place each reference properly: what becomes an inline link, what becomes a footnote, what moves to an appendix, and what is not credible enough to cite at all.</task> <format>A table of claim, source, placement decision, and the exact text to insert. Separately, flag every claim in the doc that currently has nothing behind it.</format>

<context>I have [N] Google Docs sitting in one Drive folder and need the same replacements applied to all of them: [list the old text and new text pairs]. I have never written Apps Script.</context> <task>Write a Google Apps Script that opens every Doc in a folder and applies the replacements, then tell me exactly where to paste it and how to run it.</task> <format>The full script with comments, the folder ID as a variable at the top, a DRY_RUN flag that only logs what it would change, and numbered run instructions including which permissions it will request.</format>

<context>Docs come back to me from different people with mixed fonts, sizes, and spacing. House style is [font, size, line spacing, heading sizes, margins].</context> <task>Write an Apps Script bound to a document that applies the house style to body text and to each heading level, without touching tables or images.</task> <format>The full script with one function per style rule so I can comment out the ones I do not want, plus a short list of what it cannot fix and I will have to do by hand.</format>

<context>I have a Google Sheet with the columns [list them] and a Google Doc template containing placeholders like {{name}} and {{amount}}. I need one document per row, saved into [folder].</context> <task>Write an Apps Script that copies the template for each row, replaces the placeholders, and names each file from [which columns].</task> <format>Full script with template ID and folder ID as variables, a status written back to the sheet so processed rows are skipped on a re-run, and instructions for launching it from the Sheet.</format>

<context>I run document reviews in Google Docs and need the comments tracked outside the doc. The documents involved are [IDs, or say all docs in one folder].</context> <task>Write an Apps Script that uses the Drive API to pull comments and their replies out of those documents and write them into a Google Sheet.</task> <format>Full script, the exact advanced service I must enable and how to enable it, columns for doc name, author, comment, quoted text, resolved status and date, plus what the API cannot retrieve.</format>

<context>My team repeats the same actions in every document: [list them, for example insert the standard header, stamp today's date, apply the review checklist, delete empty paragraphs].</context> <task>Write an Apps Script with an onOpen custom menu that exposes each of those actions as its own menu item.</task> <format>Full script with one clearly named function per action, the onOpen menu builder, and an explanation of why the menu only appears after a reload the first time.</format>

<context>Our documents need a consistent block at the top containing [what it should hold, for example doc owner, status, last reviewed date, confidentiality label].</context> <task>Write an Apps Script that inserts that block, or updates it if it is already there, and stamps the last modified date pulled from the file metadata.</task> <format>Full script that locates and updates the existing block instead of duplicating it, the exact block text with placeholders, and a warning about what breaks if somebody edits the block by hand.</format>

<context>Here is my script: [paste the code]. Here is the error and the execution log: [paste both]. It fails [every time / only on large docs / only for other users on the team].</context> <task>Explain what the error actually means, fix the script, and tell me which part was the real cause rather than a symptom.</task> <format>The corrected script, a short root cause explanation, and a list of the quota, timeout, or permission limits that could make this same script fail again later.</format>