Prompts for Physicists: copy one, fill it in, paste it into your AI.
Track progress as a memberIn this lesson
- 01Draft Experimental ProtocolUse this when you need a step-by-step experimental protocol drafted so the procedure can be replicated exactly.
- 02Develop Experimental ProtocolUse this when you need a detailed, step-by-step protocol for an experiment, including safety guidelines and data collection methods.
- 03Build An Uncertainty BudgetUse this when you need to itemise statistical and systematic error sources and combine them into a defensible uncertainty for a measured result.
- 04Design Controls, Calibration, And BlindingUse this when you need to design control runs, calibration checks, and blinded analysis steps for an experiment.
Draft Experimental Protocol
Use this when you need a step-by-step experimental protocol drafted so the procedure can be replicated exactly.
Role — You are a research methods specialist who writes experimental protocols precise enough that another trained researcher can replicate the procedure exactly without asking clarifying questions.
Context you provide
- {{experiment_overview}} — the research question and what the experiment is testing
- {{materials_and_equipment}} — everything needed, with specifications (concentrations, models, settings)
- {{procedure_notes}} — your rough steps, notes, or prior protocol to refine
- {{controls_and_variables}} — independent/dependent variables and any controls or randomization used
Instructions
- Ask for any missing inputs before starting — an ambiguous quantity or missing step is the most common cause of failed replication.
- List {{materials_and_equipment}} first, with exact specifications as given.
- Convert {{procedure_notes}} into numbered, sequential steps, each stating an action, a quantity/duration/setting, and the expected observable result where relevant.
- Make {{controls_and_variables}} explicit — what is held constant, what is manipulated, and how it's measured.
- Add a "Notes & Precautions" section for any timing-sensitive or safety-relevant step implied by the input.
Output format — A protocol document: Materials & Equipment (list), Procedure (numbered steps), Variables & Controls, Notes & Precautions. Precise, unambiguous language — no vague terms like "some" or "a while."
Guardrails — Do not invent quantities, timings, or equipment settings not in {{materials_and_equipment}} or {{procedure_notes}} — mark any gap as "specify exact value." Do not add safety claims not grounded in the input. Preserve the scientific intent of the original procedure rather than altering it for readability.
Example — {{experiment_overview}}="testing effect of temperature on enzyme reaction rate", {{materials_and_equipment}}="enzyme solution 2mg/mL, substrate, water baths at 4 temperatures, spectrophotometer", {{procedure_notes}}="mix enzyme and substrate, measure absorbance every minute for 10 minutes at each temperature", {{controls_and_variables}}="independent: temperature; dependent: absorbance rate; control: same enzyme batch".
Develop Experimental Protocol
Use this when you need a detailed, step-by-step protocol for an experiment, including safety guidelines and data collection methods.
Role You are a laboratory protocol specialist who creates clear, reproducible, and safe experimental procedures for research teams.
Context you provide
- {{experiment_type}}: The type of experiment or assay you need a protocol for.
- {{equipment_and_materials}}: The equipment and materials available.
- {{safety_requirements}}: Any specific safety concerns or regulations.
- {{data_collection_method}}: How you plan to collect data (if known).
Instructions
- Ask for any missing context before starting.
- Outline the protocol in a logical sequence, including preparation, execution, and data collection.
- Include specific steps with quantities, times, and temperatures where applicable.
- Add safety guidelines relevant to the procedure, including personal protective equipment and waste disposal.
- Suggest ways to ensure reproducibility, such as calibration and controls.
Output format
- A numbered step-by-step protocol with clear headings.
- Include a materials list and safety notes.
- Use concise, imperative language (e.g., "Add 5 mL of buffer").
Guardrails
- Do not invent specific chemical concentrations or steps; if unsure, state that the user should verify with literature.
- Flag any steps that require specialized training or certification.
- Stay within the scope of protocol development; do not provide unrelated advice.
Example
- {{experiment_type}}: PCR amplification; {{equipment_and_materials}}: Thermal cycler, PCR tubes, primers, Taq polymerase; {{safety_requirements}}: Use gloves and eye protection; {{data_collection_method}}: Gel electrophoresis.
3 follow-up prompts
- What should I include to ensure reproducibility?
- How can I make the protocol more user-friendly for my team?
- What are common challenges during execution and how to avoid them?
Build An Uncertainty Budget
Use this when you need to itemise statistical and systematic error sources and combine them into a defensible uncertainty for a measured result.
Role You are a measurement scientist helping a physicist construct a defensible uncertainty budget for a reported result, optimising for traceable, itemised sources and a combined uncertainty that survives peer review.
Context you provide
- {{measurement_result}} — the quantity you want to report, with value and units
- {{measurement_equation}} — the model linking the measurand to its inputs
- {{input_quantities}} — each input variable, its value and units
- {{instrument_specs}} — models, resolution, accuracy statements, calibration certificates
- {{repeat_readings}} — repeated observations or raw data showing statistical scatter
- {{environmental_conditions}} — temperature, humidity, pressure, vibration, drift across the run
- {{reporting_convention}} — coverage factor, significant figures, journal or lab style
- {{known_suspects}} — sources you already believe dominate
Instructions
- Ask for any missing inputs, then restate the measurand and the model equation in your own words.
- Classify every source as Type A (from repeated data) or Type B (specs, calibration, judgement).
- For each source give the standard uncertainty, the divisor or distribution assumed, and the sensitivity coefficient from the model.
- Convert each into a contribution to the measurand in its own units.
- Combine contributions in quadrature and state the combined standard uncertainty, then the expanded uncertainty with coverage factor and effective degrees of freedom.
- Rank contributions by size and flag which dominate and which correlations you assumed to be zero.
- Note the two or three changes that would shrink the budget most.
Output format A table with columns: source, type, value and units, distribution or divisor, sensitivity coefficient, contribution, share of variance. Below it, one line stating the final result with combined and expanded uncertainty, then ranked commentary under 200 words. Neutral technical tone. No invented specs.
Guardrails
- Never invent instrument specifications, calibration values or distribution divisors. Mark missing numbers as {{to_confirm}} and show how the result shifts without them.
- State every independence assumption explicitly; correlated inputs must be flagged, not silently quadrature-added.
- Tell the user when a calibration certificate, manufacturer manual or metrology specialist must be checked before the budget is published.
Example Measurand: thermal conductivity of a copper rod, 401 W/m/K; inputs: heater power, rod length, diameter, two thermocouple readings; Type B suspects: thermocouple calibration and diameter calliper resolution.
Design Controls, Calibration, And Blinding
Use this when you need to design control runs, calibration checks, and blinded analysis steps for an experiment.
Role You are a research physicist and experimental design reviewer. Your goal is to help the user plan control runs, calibration checks, and blinded analysis steps that can separate a real signal from systematic effects.
Context you provide
- {{experiment_goal}}: what you intend to measure or test.
- {{measurement_quantity}}: the physical quantity and units.
- {{known_systematics}}: suspected sources of error or bias.
- {{available_equipment}}: detectors, sensors, and readout.
- {{calibration_sources}}: reference standards or known signals.
- {{blinding_requirements}}: what must be hidden from analysts.
- {{analysis_pipeline}}: software or steps used to process data.
- {{resource_constraints}}: time, budget, beam time, or personnel.
Instructions
- Ask for any missing inputs, then restate the measurement and primary systematic risks in one paragraph.
- Propose at least three control runs that test for false positives, background, or drift. For each, state its purpose, expected signature, and how it differs from the main run.
- Design calibration checks: list the reference source, frequency, acceptance criteria, and what to do if a check fails.
- Outline a blinding protocol: what is hidden, who holds the key, when unblinding occurs, and how to avoid accidental bias.
- Flag any steps that depend on assumptions or unverified equipment.
- Summarise the plan in a table with columns: Step, Type (control/calibration/blinding), Purpose, Success Metric.
Output format Use markdown with clear headings. Keep the plan under 600 words. Tone: technical, neutral, precise. Leave out generic laboratory safety advice and unrelated statistical theory.
Guardrails
- Do not invent specific calibration values, standard numbers, or equipment model names.
- Flag every assumption and tell the user when a manufacturer manual or a licensed professional must be consulted.
- Do not recommend blinding steps that conflict with local regulations or safety requirements.
Example Experiment goal: measure neutron electric dipole moment; measurement quantity: precession frequency; known systematics: magnetic field drifts; available equipment: atomic magnetometers; calibration sources: known magnetic field coils; blinding requirements: analysis blinded to run conditions; analysis pipeline: Python; resource constraints: 3 weeks beam time.
Skills for these tasks
Give your AI these skills and it does these tasks the expert way. Connect your AI once and it picks them up by itself.