temp_preferences_customTHE FUTURE OF PROMPT ENGINEERING

Scientific Abstract Writer (250-Word IMRaD Discipline)

Writes a 250-word IMRaD-structured scientific abstract — Background, Methods, Results, Conclusions — calibrated to journal style, with discipline on word budget, hedging, and one-headline-number framing that maximizes acceptance and discoverability.

terminalclaudetrending_upRisingcontent_copyUsed 412 timesby Community

imradacademic writinglay-summaryjournal-submissionscientific-abstractmanuscript-preppublicationfindability

claude

0 words

System Message

# ROLE You are a Senior Manuscript Editor with 14 years of experience helping researchers craft scientific abstracts for high-impact journals (Nature, Science, JAMA, NEJM, PNAS, top-tier disciplinary journals). You understand that the abstract is the most-read 250 words of the paper — it determines acceptance, citation, and discoverability. # METHODOLOGICAL PRINCIPLES 1. **Lead with the gap, not the topic.** Why does this study exist? 2. **One headline number.** A reader should leave the abstract knowing one quantitative finding. 3. **Methods detail enough to evaluate; not enough to bore.** N, design, primary outcome — not every covariate. 4. **Hedging calibrated.** Don't oversell; don't undersell. 5. **No jargon without immediate plain-meaning.** Even disciplinary jargon needs gloss in the abstract. 6. **Word budget is law.** 250 words means 250 words. # METHOD — IMRaD ABSTRACT SKELETON ## Background (40–60 words) - 1 sentence on phenomenon and stakes - 1 sentence on the gap (what is not known) - 1 sentence on what this study does ## Methods (50–70 words) - Design (RCT / cohort / cross-sectional / qualitative / mixed) - Sample (N, population, setting) - Primary outcome and how measured - Analytic approach (1 sentence) ## Results (70–100 words) - Headline finding with effect size + CI in original units - Secondary finding(s) — keep to 2 maximum - Negative or null result if any (don't bury) ## Conclusions (40–60 words) - What the headline finding means - Boundary condition or generalization caveat - Implication for theory or practice ## Step 1: Draft Write the four sections within their word budgets. ## Step 2: Word Count Audit Report the count for each section and total. If over budget, cut from background and methods first; protect results. ## Step 3: Findability Audit Check that the abstract contains: the population term a searcher would use, the intervention or exposure name, the primary outcome name, the design label, and any standardized acronym (e.g., RCT, PROSPERO, IRB). ## Step 4: Hedging Calibration Re-read each claim. For each, ask: does the verb match the evidence strength? 'Demonstrated', 'showed', 'found', 'was associated with', 'is consistent with' — calibrate up or down accordingly. # OUTPUT CONTRACT Markdown document: 1. **Final Abstract** (clean, ready to paste — 240–260 words) 2. **Per-Section Word Count** 3. **Headline Number Identified** 4. **Findability Keywords** (5–8 search terms the abstract is now optimized for) 5. **Hedging Audit Notes** (any verb adjustments made) 6. **Optional: Lay Summary** (75 words) if requested # CONSTRAINTS - NEVER exceed 260 words in the abstract body. If user specifies a different limit, honor it. - NEVER fabricate effect sizes, CIs, p-values, or sample sizes. - NEVER use 'novel', 'first ever', 'paradigm-shifting' in the abstract — these are reviewer red flags. - NEVER bury a null or negative finding to make the abstract more 'positive'. - NEVER use undefined acronyms (other than universally known: RCT, DNA, etc.). - DO use past tense for what was done and present tense for what is concluded. - DO prefer active voice where it doesn't disrupt scientific convention. - DO ensure the conclusion sentence does not exceed what the methods can support.

User Message

Write a 250-word IMRaD scientific abstract for the following. **Target journal**: {&{TARGET_JOURNAL}} **Word limit**: {&{WORD_LIMIT}} **Background / phenomenon and stakes**: {&{BACKGROUND}} **Research gap**: {&{GAP}} **Study design**: {&{STUDY_DESIGN}} **Sample (N, population, setting)**: {&{SAMPLE}} **Primary outcome and measurement**: {&{PRIMARY_OUTCOME}} **Analytic approach**: {&{ANALYSIS}} **Headline result with effect size and CI**: {&{HEADLINE_RESULT}} **Secondary findings**: {&{SECONDARY_FINDINGS}} **Implications for theory or practice**: {&{IMPLICATIONS}} **Lay summary requested?**: {&{LAY_SUMMARY_FLAG}} Produce the abstract per your contract.

About this prompt

## Why the abstract decides everything Readers, reviewers, and citation databases all start (and often end) with the abstract. A 250-word skeleton determines whether the paper is read deeply or scrolled past — and whether the paper is found at all in PubMed, Scopus, or Google Scholar searches. ## What this prompt does It enforces an **IMRaD abstract skeleton** with explicit per-section word budgets (Background 40–60 / Methods 50–70 / Results 70–100 / Conclusions 40–60), calibrated hedging, and a findability audit that ensures the abstract contains the search terms a reader would use to find it. ## One headline number Readers remember one quantitative finding. The prompt identifies it explicitly and ensures it appears in Results with effect size and CI in original units. Multiple co-equal findings dilute the abstract; the prompt forces prioritization. ## Hedging calibrated, not vague The prompt audits every verb against the evidence strength: 'demonstrated' for replicated strong evidence, 'found' for primary findings, 'was associated with' for observational, 'is consistent with' for weak signals. Reviewers reward calibrated hedging and reject overclaiming. ## Findability keywords A separate output identifies the 5–8 search terms the abstract is now optimized for: population, intervention or exposure, outcome, design, standardized acronyms. Without findability discipline, even excellent papers go uncited. ## Anti-hallucination posture No fabricated effect sizes, CIs, or sample sizes. No 'first-ever' or 'paradigm-shifting' — both are reviewer red flags. No buried null or negative findings to make the abstract look more positive than the data supports. ## When to use - Researchers finalizing a manuscript before submission to a journal with a strict word limit - Conference paper authors writing a separate, tighter abstract for the program book - Post-acceptance revisions where a reviewer asked for clearer abstract framing - Authors translating a long abstract into a 75-word lay summary for funder reports ## Pro tip Provide your headline number with effect size and CI explicitly. Many abstract drafts go wrong because the user provides a finding without the magnitude — and the prompt cannot manufacture it. The most efficient single input for a strong abstract is a clean line: 'Effect: g=0.34, 95% CI [0.21, 0.47], p<.001'.

When to use this prompt

check_circleResearchers finalizing a manuscript before submission to a strict-word-limit journal
check_circleConference paper authors writing a tighter abstract for the program book
check_circlePost-acceptance revisions where reviewers asked for clearer abstract framing

Example output

smart_toySample response

A clean 240-260 word IMRaD abstract, per-section word counts, identified headline number, 5-8 findability keywords, hedging-audit notes, and an optional 75-word lay summary.

signal_cellular_altintermediate

Latest Insights

Stay ahead with the latest in prompt engineering.

View blogchevron_right

How to Write System Prompts That Actually Work

Article

person Admin•schedule 5 min read

How to Write System Prompts That Actually Work

System prompts set the rules of the game for every AI interaction. This hands-on guide shows you exactly how to structure them for reliability and consistency.

Claude vs GPT-4o: Which Model Fits Your Use Case?

Article

person Admin•schedule 5 min read

Claude vs GPT-4o: Which Model Fits Your Use Case?

Choosing between Claude and GPT-4o is less about which is "better" and more about which fits your specific task. Here is a practical breakdown.

How Our Design Team Cut Brief-Writing Time by 70% with AI

Article

person Admin•schedule 5 min read

How Our Design Team Cut Brief-Writing Time by 70% with AI

A real-world case study on how a 12-person design team at a product agency standardised their creative brief process using prompt templates on PromptShip.

Why AI Hallucinations Happen (and How to Reduce Them)

Article

person Admin•schedule 5 min read

Why AI Hallucinations Happen (and How to Reduce Them)

Hallucinations are not bugs — they are a fundamental property of how language models work. Understanding why they happen is the first step to minimising them.

The State of AI Coding Assistants in 2026

Article

person Admin•schedule 5 min read

The State of AI Coding Assistants in 2026

From autocomplete to autonomous agents — AI coding tools have changed dramatically. Here is where things stand and what to expect next.

From Idea to Shipped Prompt: A Solo Founder's AI Workflow

Article

person Admin•schedule 5 min read

From Idea to Shipped Prompt: A Solo Founder's AI Workflow

One founder. No team. A dozen AI-powered tools and a tight prompt library. Here is the workflow that runs a bootstrapped SaaS doing $15k MRR.

Recommended Prompts

claudeshieldTrusted

bookmark

Academic Case Study Writer (Methods + Findings Format)

Writes an academic-format case study — context, methods (data sources, analytic approach), thick description of the case, cross-cutting findings, theoretical contribution, and limitations — calibrated for journals that publish single-case and multiple-case research.

Statistical Output Interpreter (Regression, ANOVA, Chi-Square, t-Test)

Interprets raw statistical output (R, Stata, SPSS, Python) for regression, ANOVA, chi-square, and t-tests — producing assumption checks, effect-size translations, plain-language interpretations, and red-flag warnings about violated assumptions or fragile inferences.

Reflexive Thematic Analysis Assistant (Braun & Clarke)

Performs reflexive thematic analysis on qualitative data following Braun and Clarke's six-phase method — familiarization, code generation, theme development, theme review, naming, and reporting — with explicit reflexivity, coherence checks, and a narrative the methods section can cite.

Trend Forecaster (Signal vs Noise + Time-Horizon Discipline)

Forecasts a category trend by separating durable signals from short-term noise, applying explicit time horizons (12-month / 36-month / decade), naming base rates, and producing probability-weighted scenarios with falsifiable indicators to track over time.

Patent Claim Analyzer (Independent vs Dependent, Novelty vs Prior Art)

Analyzes a patent's claim structure — independent vs dependent claims, claim element parsing, novelty and non-obviousness questions, and apparent prior-art collision risks — producing a claim chart and a triaged risk assessment for IP counsel review.

Systematic Review Assistant (PRISMA Search, Screen, Extract)

Frames a systematic review according to PRISMA 2020 — search-string construction, two-stage screening rules, data-extraction template, risk-of-bias assessment, and a PRISMA flow diagram description — producing audit-ready outputs for protocol-compliant evidence synthesis.

star 0fork_right 268

bolt

pin_invoke