30 Claude Prompts for a Methods Section You Can Defend
XML prompts that turn pasted protocol notes into study design, participants, collection, analysis, ethics, and a full draft. Claude invents no procedures, stats, software versions, or citations.
In short: This page contains 30 copy-paste ready prompts, organized into 6 categories with a description and pro tip for each. The first 5 prompts are free instantly, no signup needed. Hand-curated and tested by the AI Academy team.
Study Design
5 promptsName the Design You Ran
1/30✨ What it does
Claude names a study design for [RESEARCH QUESTION] from [PROTOCOL NOTES] without inventing a design family you did not run. You verify every sentence against your protocol notes before you keep it.
<context> I need the study-design sentence for a methods section. Work only from protocol notes I paste. Do not invent a design family, a methods paper, or a published example I did not name. </context> <inputs> - Research question: [RESEARCH QUESTION] - Field: [FIELD] - Protocol notes: [PROTOCOL NOTES] - What I actually did, if it differs: [WHAT I ACTUALLY DID OR SAME] - Designs I am considering: [CANDIDATE DESIGNS OR LOCKED] - Citation style: [CITATION STYLE] </inputs> <task> Name the design I can defend. Produce: (1) one design label that fits the paste, (2) a 4 to 6 sentence methods paragraph, (3) why nearby labels do not fit, (4) what later results can and cannot support, (5) UNVERIFIED rows for any claim that needs a source or a step I did not paste. </task> <constraints> - Do not invent procedures, stats, software versions, or citations. - Do not invent a precedent study or a methods textbook page. - If [CANDIDATE DESIGNS OR LOCKED] is LOCKED, do not swap the design. Audit whether the paste matches it. - If planned and as-run differ, name both and do not hide the change. - If a claim needs a source or step I did not give, mark it UNVERIFIED. </constraints> <format> Design label, then the paragraph, then a cannot-support list, then UNVERIFIED rows. </format>
Pro tip: Paste the protocol you filed, not the design you wish you had run. A mixed-methods label on a single survey is how methods sections fail review.
Justify the Design From Constraints
2/30✨ What it does
Claude justifies [STUDY DESIGN] for [RESEARCH QUESTION] from [PROTOCOL NOTES] and names what that design cannot support. You verify the justification against your protocol notes before you keep it.
<context> I need a design justification a reviewer can live with. Argue from the question and the constraints I name. Do not invent a methods citation I did not paste. </context> <inputs> - Research question: [RESEARCH QUESTION] - Design: [STUDY DESIGN] - Alternatives I considered: [ALTERNATIVES] - Constraints: [DATA ACCESS], [MONTHS] - Protocol notes: [PROTOCOL NOTES] - Methods source I already have (optional): [PASTE METHODS SOURCE OR NONE] </inputs> <task> Justify [STUDY DESIGN] for [RESEARCH QUESTION]: why it fits, what it can support, what it cannot, alternatives I rejected and why, and threats I already accept. If I pasted a methods source, cite only that label in [CITATION STYLE] if I supplied one in the notes. </task> <constraints> - Do not invent procedures, stats, software versions, or citations. - Do not pretend a qualitative design can produce a causal estimate I did not measure. - If the design cannot answer the question, say so and propose a smaller question, not a fake method. - If a claim needs a source I did not give, mark it UNVERIFIED. </constraints> <format> Justification memo, then a cannot-support list, then a one-paragraph I chose this because draft, then UNVERIFIED rows. </format>
Pro tip: If you only remember a methods lecture, paste a page first. Claude will otherwise write a tidy fiction of that method.
State What the Design Cannot Support
3/30✨ What it does
Claude lists what [STUDY DESIGN] cannot support for [RESEARCH QUESTION] from [PROTOCOL NOTES], without adding a method you did not name. You verify each limit against your protocol notes before you keep it.
<context> I need an honest cannot-support list in the methods section, not a booster paragraph. Work only from the design and notes I paste. </context> <inputs> - Research question: [RESEARCH QUESTION] - Design: [STUDY DESIGN] - Protocol notes: [PROTOCOL NOTES] - Claims I am tempted to make later: [TEMPTING CLAIMS] - Sample n if known: [SAMPLE N OR UNKNOWN] </inputs> <task> List what [STUDY DESIGN] cannot support for [RESEARCH QUESTION]: causal claims, generalisation, mechanism, prevalence, and any item in [TEMPTING CLAIMS]. For each: why the design blocks it, a weaker sentence I can keep, and whether methods should say so in one line. </task> <constraints> - Do not invent procedures, stats, software versions, or citations. - Do not invent n or a power claim. If [SAMPLE N OR UNKNOWN] is UNKNOWN, refuse representativeness language. - Do not invent a follow-up design that would rescue a tempting claim. - If a limit needs a source I did not give, mark it UNVERIFIED. </constraints> <format> Table: tempting claim | blocked because | weaker sentence | say in methods? | UNVERIFIED. </format>
Pro tip: Paste the claims you hope the discussion will make. Methods should kill the ones the design cannot carry.
Report Setting and Timeframe
4/30✨ What it does
Claude reports the setting and timeframe for [RESEARCH QUESTION] from [PROTOCOL NOTES] and leaves dates UNKNOWN unless you pasted them. You verify every date against your protocol notes before you keep it.
<context> I need setting and timeframe sentences for a methods section. Describe only places and dates I pasted. Do not complete a missing window from a typical paper in my field. </context> <inputs> - Research question: [RESEARCH QUESTION] - Setting: [SETTING] - Start and end if I have them: [DATES OR UNKNOWN] - Protocol notes: [PROTOCOL NOTES] - Waves or visits if any: [WAVES OR NONE] </inputs> <task> Write a setting and timeframe subsection: where the work sat, when it ran, which waves I named, and who or what the setting excludes. If [DATES OR UNKNOWN] is UNKNOWN, keep every sentence date-free and list the cells I must open in the protocol or log. </task> <constraints> - Do not invent procedures, stats, software versions, or citations. - Do not invent a city, clinic, archive, or season I did not name. - Do not invent n days, n sites, or a recruitment window. - If a date or site is missing, write UNKNOWN or NOT IN PASTE and mark UNVERIFIED. </constraints> <format> Setting and timeframe prose, then a known versus NOT IN PASTE table, then UNVERIFIED rows. </format>
Pro tip: Copy dates from the ethics form or field log, not from memory. A season Claude guesses is a methods error.
Flag Planned Versus As-Run Design
5/30✨ What it does
Claude lists design deviations between [PROTOCOL] and [WHAT I ACTUALLY DID] without inventing a deviation to look honest. You verify each deviation against your protocol notes before you keep it.
<context> The methods section must say what I planned and what I did if they differ. Do not invent a deviation to look careful, and do not hide one I pasted. </context> <inputs> - Research question: [RESEARCH QUESTION] - Planned protocol: [PROTOCOL] - What I actually did: [WHAT I ACTUALLY DID] - Why it changed, if I know: [REASON OR UNKNOWN] - Advisor or ethics note: [REVIEWER NOTES OR NONE] </inputs> <task> Build a planned versus as-run map for design choices: sampling, timing, instruments, analysis, and staffing. For each difference: planned line, as-run line, reason if I gave one, and a methods sentence I can keep. If they match, say SAME and stop inventing drama. </task> <constraints> - Do not invent procedures, stats, software versions, or citations. - Do not invent a missed wave, a dropped arm, or a second coder. - If [REASON OR UNKNOWN] is UNKNOWN, write REASON NOT IN PASTE, not a guessed IRB story. - If a change needs a source or approval I did not paste, mark it UNVERIFIED. </constraints> <format> Table: domain | planned | as-run | reason | methods sentence | UNVERIFIED. Then a short deviations subsection. </format>
Pro tip: If you coded alone after planning two coders, write that. Dual coding is a method, not a tone you can claim later.
Participants
5 promptsDescribe the Sample From Notes
6/30✨ What it does
Claude describes the sample for [RESEARCH QUESTION] from [PASTE SAMPLE NOTES] and refuses a made-up headcount. You verify every sample cell against your protocol notes before you keep it.
<context> I will paste access notes and, if I have it, a planned or known headcount. Describe only that sample. Do not complete a missing n from a typical paper in my field. </context> <inputs> - Research question: [RESEARCH QUESTION] - Planned or known n: [SAMPLE N OR UNKNOWN] - Sample or access notes: [PASTE SAMPLE NOTES] - Inclusion rule: [INCLUSION RULE] - Setting: [SETTING] - Who I could not reach: [MISSING POPULATION] </inputs> <task> Write a participants subsection: who is in the set, how they entered, who is missing, and the n I supplied. If [SAMPLE N OR UNKNOWN] is UNKNOWN, keep every sentence n-free and list the cells I must open in the file. </task> <constraints> - Do not invent procedures, stats, software versions, or citations. - Do not invent n, a response rate, or a demographic split I did not paste. - If a cell is missing, write NOT IN PASTE and mark UNVERIFIED. - Do not upgrade a convenience sample into a representative one. </constraints> <format> Participants prose, then a table of known versus NOT IN PASTE fields, then UNVERIFIED rows. </format>
Pro tip: Paste the cleaned-file count, not the number you remember from recruitment week. Memory is how 184 becomes 148.
Write Inclusion and Exclusion Rules
7/30✨ What it does
Claude writes inclusion and exclusion rules for [RESEARCH QUESTION] from [PROTOCOL NOTES] without adding a criterion you did not name. You verify inclusion rules against your protocol notes before you keep it.
<context> I need inclusion and exclusion criteria as I actually applied them. Do not add a criterion that would make the sample look cleaner. </context> <inputs> - Research question: [RESEARCH QUESTION] - Inclusion rule: [INCLUSION RULE] - Exclusion rule: [EXCLUSION RULE OR NONE] - Protocol notes: [PROTOCOL NOTES] - Borderline cases I already decided: [BORDERLINE CASES OR NONE] </inputs> <task> Write inclusion and exclusion as numbered rules a second reader could apply. For each rule: the test, where it sits in the protocol, and one borderline I already decided if I pasted one. Flag any rule that appears only in my memory and not in the paste as UNVERIFIED. </task> <constraints> - Do not invent procedures, stats, software versions, or citations. - Do not invent an exclusion that would tidy a messy sample. - Do not invent n excluded or a flow-diagram count. - If [EXCLUSION RULE OR NONE] is NONE, do not invent exclusions. - If a rule needs a source or form I did not paste, mark it UNVERIFIED. </constraints> <format> Numbered inclusion rules, numbered exclusion rules, borderline notes, UNVERIFIED rows. </format>
Pro tip: Paste the screening form, not a summary. Silent extra exclusions are how samples quietly become someone else.
Report Recruitment As It Happened
8/30✨ What it does
Claude reports recruitment for [RESEARCH QUESTION] from [PASTE RECRUITMENT NOTES] as it happened, with no invented yield. You verify recruitment steps against your protocol notes before you keep it.
<context> I need a recruitment subsection that matches how people or records entered. Do not invent a channel, an incentive, or a yield I did not paste. </context> <inputs> - Research question: [RESEARCH QUESTION] - Recruitment notes: [PASTE RECRUITMENT NOTES] - Channels I actually used: [CHANNELS] - Incentive if any: [INCENTIVE OR NONE] - Yield if I counted it: [YIELD OR UNKNOWN] </inputs> <task> Write recruitment as run: channels, who invited, what they were told, incentive only if I named one, and yield only if I pasted it. If [YIELD OR UNKNOWN] is UNKNOWN, keep every sentence count-free and list the logs I must open. </task> <constraints> - Do not invent procedures, stats, software versions, or citations. - Do not invent a flyer, a clinic, a panel, or a payment I did not name. - Do not invent a response rate or a refused-n. - If a step is missing, write NOT IN PASTE and mark UNVERIFIED. </constraints> <format> Recruitment prose, then a channel checklist with NOT IN PASTE tags, then UNVERIFIED rows. </format>
Pro tip: If you used one email list, say so. A multi-site recruitment story you did not run will not survive a reviewer who asks for the invite.
Describe a Corpus or Record Set
9/30✨ What it does
Claude describes the corpus or record set for [RESEARCH QUESTION] from [PASTE ACCESS NOTES] without inventing an archive. You verify the corpus description against your protocol notes before you keep it.
<context> This study uses a corpus, archive, or record set rather than (or as well as) living participants. Describe only access I pasted. Do not invent a collection I cannot open. </context> <inputs> - Research question: [RESEARCH QUESTION] - Access notes: [PASTE ACCESS NOTES] - What is in the set: [CORPUS DESCRIPTION] - Dates of records if known: [RECORD DATES OR UNKNOWN] - Who I cannot reach: [MISSING POPULATION] </inputs> <task> Write a corpus or records subsection: what the set is, how I gained access, what is excluded, and date bounds I supplied. If [RECORD DATES OR UNKNOWN] is UNKNOWN, keep sentences date-free and list finding-aid cells I must open. </task> <constraints> - Do not invent procedures, stats, software versions, or citations. - Do not invent an archive, a database, a license, or n records. - Do not upgrade a convenience scrape into a complete census. - If a claim needs a source I did not give, mark it UNVERIFIED. </constraints> <format> Corpus prose, then known versus NOT IN PASTE fields, then UNVERIFIED rows. </format>
Pro tip: Paste the access email or finding-aid rule. A named archive Claude recalls from training is still a fake source.
Report Missing Cells Without Inventing n
10/30✨ What it does
Claude reports missing sample cells for [RESEARCH QUESTION] from [PASTE SAMPLE NOTES] and leaves n as UNKNOWN unless you pasted it. You verify missing cells against your protocol notes and leave UNKNOWN blank.
<context> My sample table is incomplete. I need methods sentences that stay honest about missing cells. Do not fill n, percents, or demographics from a typical paper. </context> <inputs> - Research question: [RESEARCH QUESTION] - Sample notes or table: [PASTE SAMPLE NOTES] - Planned or known n: [SAMPLE N OR UNKNOWN] - Cells I know are empty: [EMPTY CELLS] - Who I could not reach: [MISSING POPULATION] </inputs> <task> Write a missing-cells memo: which fields are known, which are NOT IN PASTE, which sentences must stay n-free, and a participants paragraph that uses only known cells. Leave every count as UNKNOWN unless I pasted it. </task> <constraints> - Do not invent procedures, stats, software versions, or citations. - Do not invent n, a percent, an age mean, or a gender split. - Do not round a missing cell into a tidy table. - If [SAMPLE N OR UNKNOWN] is UNKNOWN, refuse a completed flow sentence and mark UNVERIFIED. </constraints> <format> Known versus UNKNOWN table, then an n-free paragraph, then UNVERIFIED rows. </format>
Pro tip: Open the data file before you ask for prose. A methods paragraph with a guessed n is a results invention wearing a lab coat.
Data Collection
5 promptsDescribe Instruments You Named
11/30✨ What it does
Claude describes instruments for [RESEARCH QUESTION] from [PROTOCOL NOTES] without inventing a scale, item, or version. You verify each instrument against your protocol notes before you keep it.
<context> I need an instruments subsection from tools I actually named. Do not invent a scale, an item, a Cronbach alpha, or a version I did not paste. </context> <inputs> - Research question: [RESEARCH QUESTION] - Instruments I used: [INSTRUMENTS] - Protocol notes: [PROTOCOL NOTES] - Versions or editions if I have them: [VERSIONS OR UNKNOWN] - Citation style: [CITATION STYLE] - Instrument source I already have (optional): [PASTE INSTRUMENT SOURCE OR NONE] </inputs> <task> Describe each item in [INSTRUMENTS]: what it captured, how I administered it, and version only if I pasted one. Cite only labels that appear in [PASTE INSTRUMENT SOURCE OR NONE]. If a version, alpha, or item count is missing, write UNKNOWN and mark UNVERIFIED. </task> <constraints> - Do not invent procedures, stats, software versions, or citations. - Do not invent a validated scale, a cutoff, or a reliability coefficient. - Do not invent author-year for an instrument I did not paste. - If I wrote my own items, say so. Do not dress them as a published measure. </constraints> <format> One block per instrument, then UNKNOWN fields, then UNVERIFIED rows. </format>
Pro tip: Paste the exact instrument name and edition from the form you used. A version Claude fills from memory is a citation error.
Write the Procedure As Run
12/30✨ What it does
Claude writes the collection procedure for [RESEARCH QUESTION] from [WHAT I ACTUALLY DID] without adding a step you did not run. You verify the procedure against your protocol notes before you keep it.
<context> I will paste what I actually did in the field or at the desk. The procedure must match that paste, including awkward steps. Do not add a visit, a recorder, or a pilot I did not name. </context> <inputs> - Research question: [RESEARCH QUESTION] - What I actually did: [WHAT I ACTUALLY DID] - Planned protocol if it differs: [PROTOCOL OR SAME] - Word limit: [WORD COUNT] - Citation style: [CITATION STYLE] </inputs> <task> Rewrite [WHAT I ACTUALLY DID] as a procedures subsection a second reader could follow: order of tasks, who was present, what was collected, and how long a session lasted only if I pasted a duration. Stay under [WORD COUNT]. List deviations from [PROTOCOL OR SAME] separately. </task> <constraints> - Do not invent procedures, stats, software versions, or citations. - Do not invent a consent script, a recorder, or a second interviewer. - If duration, n sessions, or site count is missing, write UNKNOWN and mark UNVERIFIED. - If the paste is a plan and not a log, label the draft AS PLANNED. </constraints> <format> Numbered procedures under [WORD COUNT], then AS PLANNED versus AS RUN, then UNVERIFIED rows. </format>
Pro tip: If collection already happened, paste the log, not the approved plan. Reviewers catch procedures that exist only on the ethics form.
Report Timing, Sites, and Waves
13/30✨ What it does
Claude reports timing, sites, and waves for [RESEARCH QUESTION] from [PROTOCOL NOTES] and leaves counts UNKNOWN unless you pasted them. You verify timing and sites against your protocol notes before you keep it.
<context> I need timing, sites, and waves reported as I ran them. Do not invent a second site or a follow-up wave that would make the design look stronger. </context> <inputs> - Research question: [RESEARCH QUESTION] - Protocol notes: [PROTOCOL NOTES] - Sites I actually used: [SITES] - Dates or waves: [DATES OR WAVES OR UNKNOWN] - What I skipped: [SKIPPED WAVES OR NONE] </inputs> <task> Write a timing and sites subsection: which sites, which waves, which dates I supplied, and what I skipped. If [DATES OR WAVES OR UNKNOWN] is UNKNOWN, keep sentences count-free and list the calendar cells I must open. </task> <constraints> - Do not invent procedures, stats, software versions, or citations. - Do not invent a site, a wave, or n visits. - Do not invent that a skipped wave was optional if the protocol required it. Name the skip. - If a date is missing, write UNKNOWN and mark UNVERIFIED. </constraints> <format> Timing and sites prose, then a wave table with UNKNOWN cells, then UNVERIFIED rows. </format>
Pro tip: If wave two never happened, say so in methods. Hiding a dropped wave until limitations looks like you noticed it late.
Log Collection Deviations
14/30✨ What it does
Claude logs collection deviations between [PROTOCOL] and [WHAT I ACTUALLY DID] without inventing a missed visit. You verify collection deviations against your protocol notes before you keep it.
<context> Collection did not match the protocol in places I will name. Log those deviations. Do not invent extra ones to look transparent, and do not tidy away ones I pasted. </context> <inputs> - Research question: [RESEARCH QUESTION] - Planned protocol: [PROTOCOL] - What I actually did: [WHAT I ACTUALLY DID] - Deviations I already logged: [DEVIATIONS] - Ethics note if any: [ETHICS NOTE OR NONE] </inputs> <task> Write a collection-deviations subsection from [DEVIATIONS] plus any clash you can see between [PROTOCOL] and [WHAT I ACTUALLY DID]. For each: what changed, when if I said so, whether ethics already knew, and a methods sentence. Do not add a deviation that is not in the paste. </task> <constraints> - Do not invent procedures, stats, software versions, or citations. - Do not invent a missed visit, a broken recorder, or a protocol amendment. - If [ETHICS NOTE OR NONE] is NONE, do not invent that a board approved the change. - If a change needs a source I did not give, mark it UNVERIFIED. </constraints> <format> Numbered deviations with methods sentences, then a not-in-paste clash list, then UNVERIFIED rows. </format>
Pro tip: Paste the deviation log you already keep. A clean methods section that never slipped is often the one reviewers distrust.
Describe Storage and Handling
15/30✨ What it does
Claude describes storage and handling for [RESEARCH QUESTION] from [PROTOCOL NOTES] without inventing a platform or retention rule. You verify storage claims against your protocol notes before you keep it.
<context> I need data storage and handling sentences that match what I actually used. Do not invent a platform, an encryption claim, or a retention year I did not paste. </context> <inputs> - Research question: [RESEARCH QUESTION] - Protocol notes: [PROTOCOL NOTES] - Where files live: [STORAGE] - Who can open them: [ACCESS RULE] - Retention if I know it: [RETENTION OR UNKNOWN] - Identifiers I kept or stripped: [IDENTIFIERS] </inputs> <task> Write a storage and handling subsection: where data sat, who could open it, whether identifiers stayed, and retention only if I pasted it. If [RETENTION OR UNKNOWN] is UNKNOWN, keep that sentence out and list the policy I must open. </task> <constraints> - Do not invent procedures, stats, software versions, or citations. - Do not invent a vendor, a lock, or n years of retention. - Do not invent that data were anonymised if I only said de-identified, or the reverse. - If a claim needs a source I did not give, mark it UNVERIFIED. </constraints> <format> Storage prose, then a known versus UNKNOWN checklist, then UNVERIFIED rows. </format>
Pro tip: Copy the storage line from the ethics form. Encrypted at rest is a claim you must be able to show, not a phrase Claude should gift you.
These prompts give you the what. Tutorials give you the why.
Learn when to use extended thinking, how to build Claude Projects, and workflows that compound. 300+ tutorials and growing.
Analysis Plan
5 promptsWrite Analysis Steps From the Plan
16/30✨ What it does
Claude writes analysis steps for [RESEARCH QUESTION] from [PASTE ANALYSIS NOTES] and leaves counts as UNKNOWN unless you pasted them. You verify analysis steps against your protocol notes before you keep it.
<context> I need an analysis subsection from steps I already named, not results. Do not invent a test, a model, or an n I did not name. </context> <inputs> - Research question: [RESEARCH QUESTION] - Design: [STUDY DESIGN] - Analysis notes: [PASTE ANALYSIS NOTES] - Software I can use: [SOFTWARE] - Sample n if known: [SAMPLE N OR UNKNOWN] - Word limit: [WORD COUNT] </inputs> <task> Write an analysis plan: units, preparation, primary analysis, secondary or exploratory work, and what I will not claim. Leave every count as UNKNOWN unless I pasted it. Stay under [WORD COUNT]. If the work already ran, label steps AS RUN only when the paste is a log. </task> <constraints> - Do not invent procedures, stats, software versions, or citations. - Do not invent n, p-values, effect sizes, or a finding. - Do not add a test I cannot run in [SOFTWARE] unless you label it OPTIONAL, NEEDS NEW TOOL. - If [SAMPLE N OR UNKNOWN] is UNKNOWN, refuse a power claim and mark UNVERIFIED. </constraints> <format> Numbered analysis steps, then a will-not-claim list, then UNKNOWN cells, then UNVERIFIED rows. </format>
Pro tip: If you have not chosen software, say so. A tidy mixed-effects plan you cannot run is a reviewer gift.
Name Variables or Codes You Used
17/30✨ What it does
Claude names variables or codes for [RESEARCH QUESTION] from [PASTE ANALYSIS NOTES] without inventing a measure you did not use. You verify named variables against your protocol notes before you keep it.
<context> I need the variables, codes, or materials I actually used listed so a reader can follow the analysis. Do not invent a measure, a code, or a codebook I did not paste. </context> <inputs> - Research question: [RESEARCH QUESTION] - Analysis notes or codebook excerpts: [PASTE ANALYSIS NOTES] - Outcomes I named: [OUTCOMES] - Predictors or themes I named: [PREDICTORS OR THEMES] - Citation style: [CITATION STYLE] </inputs> <task> List variables or codes from the paste only: name, role (outcome, predictor, covariate, theme, other), how I measured or applied it, and any missing definition. Quote codebook lines only if they appear in the paste. </task> <constraints> - Do not invent procedures, stats, software versions, or citations. - Do not invent a variable, a code, or a cutoff. - Do not invent n levels or n themes. - If a name is in [OUTCOMES] but not defined in the notes, mark UNVERIFIED, NEED DEFINITION. </constraints> <format> Table: name | role | definition in paste | UNVERIFIED. Then a NEED DEFINITION list. </format>
Pro tip: Paste the codebook or the data dictionary, not the paper you wish you had written. Extra variables are how analyses quietly grow.
Plan Missingness Without Fake Counts
18/30✨ What it does
Claude plans missingness handling for [RESEARCH QUESTION] from [PASTE ANALYSIS NOTES] without inventing n missing or a test. You verify missingness plans against your protocol notes before you keep it.
<context> I need a missingness plan that does not invent how much is missing. Use only rules I pasted. Do not invent n missing or a test I did not name. </context> <inputs> - Research question: [RESEARCH QUESTION] - Analysis notes: [PASTE ANALYSIS NOTES] - Missingness rule I already chose: [MISSINGNESS RULE OR UNKNOWN] - Sample n if known: [SAMPLE N OR UNKNOWN] - Software: [SOFTWARE] </inputs> <task> Write a missingness subsection: the rule I named, what I will not impute, and what I will report as unknown. If [MISSINGNESS RULE OR UNKNOWN] is UNKNOWN, list the decisions I still owe and refuse a completed plan. Leave every count as UNKNOWN unless I pasted it. </task> <constraints> - Do not invent procedures, stats, software versions, or citations. - Do not invent n missing, a percent complete, or Little's test unless I named that test. - Do not invent multiple imputation if I did not name it. - If [SAMPLE N OR UNKNOWN] is UNKNOWN, refuse a missingness percent and mark UNVERIFIED. </constraints> <format> Missingness prose, then UNKNOWN cells, then UNVERIFIED rows. </format>
Pro tip: If you have not opened the missingness report, keep n out. A 12 percent complete case line you cannot show is a stats invention.
Separate Primary From Exploratory Work
19/30✨ What it does
Claude separates primary from exploratory analysis for [RESEARCH QUESTION] from [PASTE ANALYSIS NOTES] without inventing a test. You verify the primary versus exploratory split against your protocol notes before you keep it.
<context> I need the methods section to split primary analysis from exploratory work. Do not invent a pre-registered primary test I did not name. </context> <inputs> - Research question: [RESEARCH QUESTION] - Analysis notes: [PASTE ANALYSIS NOTES] - Primary analysis I named: [PRIMARY ANALYSIS] - Extra looks I already did or want: [EXPLORATORY LIST] - Registration status: [REGISTERED / NOT REGISTERED / UNKNOWN] </inputs> <task> Split the analysis: primary (only what I named), secondary if I named it, exploratory (the rest). For each extra look: keep as exploratory, drop, or UNVERIFIED if I never ran it. If registration is NOT REGISTERED or UNKNOWN, do not write that the primary test was pre-registered. </task> <constraints> - Do not invent procedures, stats, software versions, or citations. - Do not invent a registry ID or a locked primary outcome. - Do not move an exploratory look into primary to make the paper tidier. - If a split needs a source I did not give, mark it UNVERIFIED. </constraints> <format> Three headed lists (primary / secondary / exploratory), then a do-not-claim line, then UNVERIFIED rows. </format>
Pro tip: If it was not named as primary before you saw the data, it is exploratory. Methods should say that before results do not.
Refuse Software Versions You Did Not Paste
20/30✨ What it does
Claude lists software you named for [RESEARCH QUESTION] from [SOFTWARE] and marks any version UNVERIFIED unless you pasted it. You verify software names and versions against your protocol notes before you keep it.
<context> I need a software sentence that names only tools I used. Do not invent a version, a package, or a license I did not paste. </context> <inputs> - Research question: [RESEARCH QUESTION] - Software I can name: [SOFTWARE] - Versions if I have them: [VERSIONS OR UNKNOWN] - Packages or libraries if I have them: [PACKAGES OR UNKNOWN] - Analysis notes: [PASTE ANALYSIS NOTES] </inputs> <task> Write a software and environment sentence block: tools in [SOFTWARE], versions only from [VERSIONS OR UNKNOWN], packages only from [PACKAGES OR UNKNOWN]. If a version is UNKNOWN, write SOFTWARE NAMED, VERSION UNVERIFIED and list the About or sessionInfo step I must run. </task> <constraints> - Do not invent procedures, stats, software versions, or citations. - Do not invent R, Python, SPSS, NVivo, or a package I did not name. - Do not invent a version number, a build, or a citation for the tool. - If you are unsure a package exists in my paste, mark UNVERIFIED, do not add it. </constraints> <format> Software sentences, then a VERSION UNVERIFIED checklist, then the lookup steps I must run. </format>
Pro tip: Open the program and copy the version string. A version Claude remembers from training is still a fabricated number.
Ethics
5 promptsDraft Ethics Facts From Status
21/30✨ What it does
Claude drafts ethics facts for [RESEARCH QUESTION] from [ETHICS ID OR NONE] without inventing an approval number. You verify ethics status against your protocol notes and approval letter.
<context> I need ethics sentences that match what I am allowed to say. Do not invent an approval number, a waived review, or a board I did not name. </context> <inputs> - Research question: [RESEARCH QUESTION] - Ethics status: [ETHICS ID OR NONE / PENDING / NOT REQUIRED] - Board or office if I have it: [BOARD NAME OR NONE] - Data type: [HUMAN / ARCHIVAL / PUBLIC / OTHER] - Protocol notes: [PROTOCOL NOTES] </inputs> <task> Draft ethics facts only as I stated them: approval status, board name only if I gave it, and what the study must not claim. If status is NONE or PENDING, write that the methods section must not claim approval. If NOT REQUIRED, restate my reason from the paste, do not invent a category. </task> <constraints> - Do not invent procedures, stats, software versions, or citations. - Do not invent an IRB, REB, or ethics ID. - Do not invent a waiver, an exemption letter, or a date of approval. - If a fact needs a letter I did not paste, mark it UNVERIFIED. </constraints> <format> Ethics prose, then a must-not-claim list, then UNVERIFIED rows. </format>
Pro tip: Put the real approval number in yourself. Claude completing an ethics ID from memory is a misconduct risk.
Write Consent or Data-Use Notes
22/30✨ What it does
Claude writes consent or data-use notes for [RESEARCH QUESTION] from [PROTOCOL NOTES] without inventing a form you did not use. You verify consent wording against your protocol notes before you keep it.
<context> I need consent or data-use sentences from the process I actually used. Do not invent a form, a signature, or a public-data licence I did not paste. </context> <inputs> - Research question: [RESEARCH QUESTION] - Consent or data-use notes: [PROTOCOL NOTES] - Process I used: [CONSENT / WAIVER / LICENCE / PUBLIC / OTHER] - What participants or sources were told: [WHAT THEY WERE TOLD OR UNKNOWN] - Withdrawal rule if any: [WITHDRAWAL OR NONE] </inputs> <task> Write consent or data-use notes: the process I named, what people were told only if I pasted it, withdrawal only if I named it, and what I must not claim. If [WHAT THEY WERE TOLD OR UNKNOWN] is UNKNOWN, keep that paragraph out and list the form I must open. </task> <constraints> - Do not invent procedures, stats, software versions, or citations. - Do not invent a consent script, a checkbox, or a GDPR clause. - Do not invent that consent was written if I only said verbal, or the reverse. - If a line needs a form I did not paste, mark it UNVERIFIED. </constraints> <format> Consent or data-use prose, then a form-to-open list, then UNVERIFIED rows. </format>
Pro tip: Paste the consent paragraph you actually used. A reconstructed script is how methods and the form in the appendix stop matching.
Report Risks You Already Named
23/30✨ What it does
Claude reports risks and mitigations for [RESEARCH QUESTION] from [KNOWN RISKS] without inventing a procedure that closed a risk. You verify named risks against your protocol notes before you keep it.
<context> I need risk and mitigation sentences that match risks I already named. Do not invent a harm, a hotline, or a closing procedure I did not paste. </context> <inputs> - Research question: [RESEARCH QUESTION] - Known risks: [KNOWN RISKS] - Mitigations I already run: [MITIGATIONS] - Population I could not reach: [MISSING POPULATION] - Protocol notes: [PROTOCOL NOTES] </inputs> <task> Draft a short risks subsection: each risk in [KNOWN RISKS], the mitigation I named, and risks I did not mitigate. Separate residual risk from ethics approval. Do not add a risk that is not in the paste just to look thorough. </task> <constraints> - Do not invent procedures, stats, software versions, or citations. - Do not invent a distress protocol, a counsellor, or a data-breach drill. - Do not invent that a risk was closed if I only named it. - If a mitigation needs a source I did not give, mark it UNVERIFIED. </constraints> <format> Risk table: risk | mitigation in paste | residual | UNVERIFIED. Then 6 reusable sentences. </format>
Pro tip: If you promised a referral sheet, confirm it went out. A mitigation that lived only in the protocol is a methods overclaim.
Separate Ethics Facts From Study Limits
24/30✨ What it does
Claude separates ethics facts from study limits for [RESEARCH QUESTION] using [ETHICS ID OR NONE] and [KNOWN LIMITS]. You verify ethics versus limits against your protocol notes before you keep it.
<context> Ethics approval and study limits get mixed in my draft. Split them. Do not invent a limit-closing study or an approval I do not have. </context> <inputs> - Research question: [RESEARCH QUESTION] - Ethics status: [ETHICS ID OR NONE / PENDING / NOT REQUIRED] - Known limits: [KNOWN LIMITS] - Known risks: [KNOWN RISKS] - Protocol notes: [PROTOCOL NOTES] </inputs> <task> Write two short subsections: (1) ethics facts only as I stated them, (2) study limits I already accept. Move any sentence that is a design or sample limit out of ethics. Include the limit of using Claude on this methods draft. </task> <constraints> - Do not invent procedures, stats, software versions, or citations. - Do not invent an ethics ID or a waived review. - Do not invent a limit-closing follow-up. - If a sentence needs a source I did not give, mark it UNVERIFIED. </constraints> <format> Ethics subsection, limits subsection, then a moved-sentence list, then UNVERIFIED rows. </format>
Pro tip: Approval is not a validity claim. A small n belongs in limits, not in the sentence that names the board.
Flag Claude Use in the Methods
25/30✨ What it does
Claude drafts a Claude-use disclosure for [RESEARCH QUESTION] from [VENUE AI POLICY] without inventing a journal rule. You verify the Claude-use line against your protocol notes and the venue policy you pasted.
<context> I used Claude to draft methods prose. I need a disclosure line that matches the venue policy I paste, not a hidden ghostwrite. </context> <inputs> - Research question: [RESEARCH QUESTION] - Venue AI policy I actually have: [VENUE AI POLICY] - What Claude did: [WHAT CLAUDE DID] - What I checked: [WHAT I CHECKED] - Protocol notes: [PROTOCOL NOTES] </inputs> <task> Draft 3 disclosure options: short (one sentence), methods-paragraph (3 to 5 sentences), and acknowledgements-style. Each must state that Claude drafted from my notes, that I verified procedures against the protocol, and that Claude invented no n or citations. Honor [VENUE AI POLICY]. If the policy is silent, say ASK VENUE rather than inventing a rule. </task> <constraints> - Do not invent procedures, stats, software versions, or citations. - Do not invent a journal rule, a COPE clause, or a required phrase I did not paste. - Do not claim I checked a step I did not list in [WHAT I CHECKED]. - If a policy line is unclear, mark UNVERIFIED and ASK VENUE. </constraints> <format> Three disclosure drafts, then ASK VENUE blanks, then UNVERIFIED rows. </format>
Pro tip: Paste the journal or program AI note. A disclosure Claude invents from a generic integrity blog is still the wrong rule.
Most people use 10% of Claude. Tutorials unlock the rest.
AI Academy: 300+ hands-on tutorials on Claude, ChatGPT, Midjourney, and 50+ AI tools. New tutorials added every week.
Full Draft
5 promptsAssemble a Methods Outline
26/30✨ What it does
Claude builds a methods outline for [RESEARCH QUESTION] from [PROTOCOL NOTES] with NEED NOTES blanks and no invented procedures. You verify the outline against your protocol notes before you draft prose.
<context> I need a methods-section outline a paper or chapter can follow, not a finished draft. Do not stock the outline with procedures, n, or citations I have not pasted. </context> <inputs> - Research question: [RESEARCH QUESTION] - Venue headings if I have them: [VENUE HEADINGS OR NONE] - Protocol notes: [PROTOCOL NOTES] - Word count target: [WORD COUNT] - Citation style: [CITATION STYLE] </inputs> <task> Build an outline: design, setting, participants or corpus, collection, analysis, ethics, deviations, limits. Each heading needs a job, a word budget that sums to [WORD COUNT], and a blank where a count, version, or citation is missing. If I pasted [VENUE HEADINGS OR NONE], use those headings. </task> <constraints> - Do not invent procedures, stats, software versions, or citations. - If a heading has no pasted support, leave it as a heading plus NEED NOTES. - Do not invent a journal heading I did not paste. - If a claim needs a source I did not give, mark it UNVERIFIED. </constraints> <format> Nested outline with word counts and NEED NOTES tags. UNVERIFIED list at the end. </format>
Pro tip: Ask for an artifact so the outline stays beside the draft. Writing methods without the outline is how procedures sprawl and n appears from nowhere.
Draft the Complete Methods Section
27/30✨ What it does
Claude drafts a complete methods section for [RESEARCH QUESTION] from [PROTOCOL NOTES] at [WORD COUNT], tagging UNVERIFIED any missing procedure. You verify the full draft against your protocol notes before you keep it.
<context> I will paste the protocol notes I actually have. Draft a complete methods section from that paste only. Do not invent procedures, stats, software versions, or a literature I have not supplied. </context> <inputs> - Research question: [RESEARCH QUESTION] - Protocol notes and what I actually did: [PROTOCOL NOTES] - Word count: [WORD COUNT] - Citation style: [CITATION STYLE] - Required headings: [VENUE HEADINGS OR NONE] - Sample n if known: [SAMPLE N OR UNKNOWN] </inputs> <task> Draft the full methods section under [WORD COUNT]: design, setting, participants or corpus, collection, analysis, ethics, deviations, limits. Cite only sources present in the paste. Tag any sentence that still needs a procedure, count, version, or source as UNVERIFIED. Leave counts as UNKNOWN unless I pasted them. </task> <constraints> - Do not invent procedures, stats, software versions, or citations. - Do not write completed results for a study that has not run. - If a heading has no pasted support, write NEED NOTES under it instead of filling it. - Prefer a thinner honest draft over a complete-looking section I cannot evidence. </constraints> <format> Full methods draft under the headings I gave (or a standard set if I said NONE), then a master UNVERIFIED and UNKNOWN list. </format>
Pro tip: Paste the protocol, the as-run log, and the ethics status in one go. A complete draft from a title alone is how invented procedures get invited.
Cut to a Word or Page Limit
28/30✨ What it does
Claude cuts [PASTE DRAFT] to [WORD COUNT] while protecting [MUST KEEP] and deleting padding, not procedures. You verify the cut draft against your protocol notes so no procedure vanished.
<context> I must cut [PASTE DRAFT] to [WORD COUNT] or [PAGE LIMIT OR NONE] without losing a procedure I actually ran or inventing a tighter statistic. </context> <inputs> - Draft: [PASTE DRAFT] - Target word count: [WORD COUNT] - Page limit if any: [PAGE LIMIT OR NONE] - Must keep: [MUST KEEP] - Protocol notes: [PROTOCOL NOTES] - Citation style: [CITATION STYLE] </inputs> <task> Cut to [WORD COUNT] (and [PAGE LIMIT OR NONE] if I set one). Protect [MUST KEEP]. Prefer deleting repetition and throat-clearing. Do not delete a procedure and keep the claim as if it were still specified. Do not invent a tighter n to save space. Show a cut log. </task> <constraints> - Do not invent procedures, stats, software versions, or citations. - Do not add new citations while cutting. - Do not merge two instruments into one name. - If a required procedure cannot survive the cut, say so and stop before you gut the protocol. - Report old and new word counts. </constraints> <format> Cut draft, word counts, cut log (what left and why), UNVERIFIED rows. </format>
Pro tip: Tell Claude what must stay (the sample rule, the as-run deviation, the software). Unguided cuts delete the sentence a reviewer will ask for.
Audit Overclaims Against the Protocol
29/30✨ What it does
Claude audits [PASTE METHODS] against [PROTOCOL] for overclaims such as dual coding or a representative sample you did not have. You verify each overclaim rewrite against your protocol notes before you keep it.
<context> I need a hostile methods audit: does the draft claim more than the protocol and access can support? Do not repair an overclaim with extra data or a second coder I did not have. </context> <inputs> - Research question: [RESEARCH QUESTION] - Methods draft: [PASTE METHODS] - Protocol: [PROTOCOL] - Data I can reach: [DATA ACCESS] - Sample n if known: [SAMPLE N OR UNKNOWN] </inputs> <task> Audit [PASTE METHODS] against [PROTOCOL] for overclaims: causal language, dual coding I did not name, a representative sample I did not have, a test I cannot run, a software version I did not paste, or a completed result in past tense. For each: quote the line, name the overclaim, and rewrite a weaker line I can keep. </task> <constraints> - Do not invent procedures, stats, software versions, or citations. - Do not invent n, a second coder, an instrument, or a finding. - If [SAMPLE N OR UNKNOWN] is UNKNOWN, refuse a power or representativeness claim. - If a rewrite needs a source I did not give, mark it UNVERIFIED. </constraints> <format> Table: quoted line | overclaim | weaker rewrite | UNVERIFIED? </format>
Pro tip: Search the draft for will show, prove, and representative. Those three words are where reviewers start.
Build a Pre-Submission Methods Checklist
30/30✨ What it does
Claude builds a pre-submission methods checklist for [VENUE RULES] from [PROTOCOL NOTES], inventing no extra journal rule. You verify every checklist item against your protocol notes before you submit.
<context> I need a checklist before I submit a methods section under [VENUE RULES]. This is a QA list, not a new draft of the section. </context> <inputs> - Research question: [RESEARCH QUESTION] - Venue rules: [VENUE RULES] - Protocol notes: [PROTOCOL NOTES] - Word or page limit: [WORD COUNT] - Citation style: [CITATION STYLE] - Optional draft: [PASTE DRAFT OR NONE] </inputs> <task> Build a checklist: design match, sample honesty, collection as run, analysis without fake counts, software versions verified, ethics wording, deviations named, word count versus [WORD COUNT], citation completeness against sources I pasted, and any rule in [VENUE RULES]. Mark items I must verify by hand against the protocol. </task> <constraints> - Do not invent procedures, stats, software versions, or citations. - Do not invent a journal rule I did not paste. - Do not invent that my citations or versions are complete. - If I pasted a draft, flag only problems you can see. If I did not, keep items as blank checks. - No suggested extra papers. </constraints> <format> Checkbox list grouped by design, sample, collection, analysis, ethics, venue. Hand-verify items in italics. UNVERIFIED rows last. </format>
Pro tip: Paste the venue's methods checklist if it has one. Journal-ish lists miss the one item that actually sends the file back.
Free tool
Prompt Optimizer
Turn a rough idea into a structured, professional AI prompt.
Frequently Asked Questions
Prompts are the starting line. Tutorials are the finish.
A growing library of 300+ hands-on tutorials on ChatGPT, Claude, Midjourney, and 50+ AI tools. New tutorials added every week.
7-day free trial. Cancel anytime.
Related guides