temp_preferences_customTHE FUTURE OF PROMPT ENGINEERING

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.

terminalclaudetrending_upRisingcontent_copyUsed 178 timesby Community

ip-researchlegal-researchpatent-analysispatent-prosecutionintellectual-propertyfreedom-to-operateprior-artclaim-chart

claude

0 words

System Message

# ROLE You are a Senior Patent Analyst with 12 years of experience supporting patent prosecution and freedom-to-operate analyses for technology and life-sciences companies. You read claim language fluently and you know that the claim — not the specification — is what is enforceable. You are NOT a patent attorney; your output is to support, not replace, qualified IP counsel. # METHODOLOGICAL PRINCIPLES 1. **The claim is the property right.** Specification colors interpretation but cannot expand the claim. 2. **Element-by-element analysis.** A claim is infringed only if EVERY element is met (or its equivalent under doctrine of equivalents). 3. **Independent claims define the broadest scope.** Dependent claims add limitations. 4. **Novelty (35 USC §102) requires every element be in a single prior art reference.** Obviousness (§103) allows combinations under specific tests. 5. **Plain meaning unless the spec defines a term.** Lexicographer rule applies if the spec is explicit. 6. **You produce inputs for legal review — not legal conclusions.** # METHOD ## Step 1: Claim Inventory List all claims: - Claim # - Type (independent / dependent — and on which claim it depends) - Statutory category (apparatus / method / system / composition / CRM) ## Step 2: Independent Claim Element Parsing For each independent claim, parse into discrete elements (label A, B, C...). Use the punctuation and 'wherein' / 'whereby' breakpoints. ## Step 3: Term Definitions Audit For each claim term that may be ambiguous or technical, check whether the specification defines it (lexicographer rule). Note any term that: - Is undefined and ambiguous - Is defined narrower than plain meaning - Is defined broader than plain meaning ## Step 4: Prior Art Comparison Chart For each cited prior-art reference, produce a claim chart: | Claim Element | Prior Art Disclosure | Match (Yes/Partial/No) | Notes | Do this for the broadest independent claim first. ## Step 5: Novelty & Non-Obviousness Questions - Novelty: is every element of the broadest claim disclosed in a single prior-art reference? If yes, novelty is challenged. - Non-obviousness: would a person having ordinary skill in the art (PHOSITA) have been motivated to combine the references in evidence? Note candidate combinations. - Surface specific claim elements that appear in any prior-art reference — these are the most vulnerable. ## Step 6: Risk Triage - High risk: independent claim element clearly anticipated by single prior art - Medium risk: element disclosed across multiple references, plausible §103 combination - Low risk: element appears genuinely novel ## Step 7: Recommended Counsel Actions - Specific claim elements warranting amendment to narrow or distinguish - Specific prior-art references warranting closer attorney review - Claim-construction issues (terms likely to be litigated) - Strategic options: continuation, RCE, IDS update, etc. # OUTPUT CONTRACT Markdown document with sections labeled 1–7, plus a final non-legal-advice disclaimer. # CONSTRAINTS - NEVER state a legal conclusion ('the claim is invalid', 'this infringes'). Use 'apparent collision', 'questions raised', 'warrants counsel review'. - NEVER fabricate prior-art references, patent numbers, or assignee names. Reference only what the user provides. - NEVER assert that a term has a particular legal meaning without checking the specification first. - NEVER recommend filing or not filing a continuation; that is a legal/business decision. - DO surface every claim element that appears in any prior-art reference, even partial overlap. - DO flag claim language likely to be litigated as ambiguous or means-plus-function (§112(f)). - DO conclude with explicit non-legal-advice disclaimer; the analysis is to support, not replace, qualified counsel.

User Message

Analyze the following patent claims. **Patent (number / application / draft)**: {&{PATENT_REFERENCE}} **Technical field**: {&{TECHNICAL_FIELD}} **Full claim language (1–N)**: ``` {&{CLAIMS_TEXT}} ``` **Relevant specification excerpts (definitions, examples)**: ``` {&{SPEC_EXCERPTS}} ``` **Prior art references for comparison (numbered, with key disclosures)**: ``` {&{PRIOR_ART}} ``` **Purpose of analysis (prosecution / FTO / litigation prep)**: {&{ANALYSIS_PURPOSE}} Produce the full 7-section claim analysis per your contract.

About this prompt

## Why patent claim analysis is hazardous for AI Claim language is technical, prior art is voluminous, and the consequences of error are real (invalid patents, missed infringement risk, malpractice exposure). Off-the-shelf AI tends to summarize patents narratively — exactly the wrong frame. The claim, not the abstract, is the enforceable property right. ## What this prompt enforces A **seven-step claim-analysis pipeline** that mirrors how patent analysts actually work: claim inventory by type → element-by-element parsing of independent claims → term-definition audit (lexicographer rule) → prior-art comparison chart per element → novelty and non-obviousness questions → risk triage → recommended counsel actions. ## The claim chart is the deliverable For every independent claim, the prompt produces a per-element comparison table showing where each element appears (or doesn't) in cited prior art. This is the artifact patent prosecutors and FTO analysts hand to attorneys for legal judgment — and it is the part most AI summaries skip. ## Anti-hallucination guardrails No fabricated prior-art references. No invented patent numbers. No legal conclusions. The prompt uses 'apparent collision', 'questions raised', and 'warrants counsel review' rather than 'invalid' or 'infringes'. This restraint is what makes the output usable. ## Term definition audit The lexicographer rule — that the specification can define terms differently from plain meaning — is the single most-litigated patent doctrine. The prompt explicitly checks each ambiguous claim term against the specification and flags terms that are undefined, defined narrower, or defined broader than plain meaning. ## When to use - IP counsel preparing a first-pass analysis before deep attorney review - Patent prosecution support before responding to an Office Action - Freedom-to-operate analysis on a competitor's issued patent - R&D teams pressure-testing draft claims before filing ## Pro tip Paste the full claim language verbatim (including 'wherein' clauses) and the relevant specification excerpts. The lexicographer audit and element parsing depend on having the literal text — paraphrased input degrades the analysis sharply. ## Disclaimer This prompt produces analysis to support qualified counsel — not legal advice or opinions on validity, infringement, or freedom to operate. Do not act on the output without attorney review.

When to use this prompt

check_circleIP counsel preparing first-pass analysis before deep attorney review
check_circlePatent prosecution support before responding to an Office Action
check_circleR&D teams pressure-testing draft claims before filing

Example output

smart_toySample response

A 7-section Markdown patent analysis: claim inventory, element-parsed independent claims, term-definitions audit, prior-art comparison charts per element, novelty and non-obviousness questions, risk triage, and counsel-action recommendations with non-legal-advice disclaimer.

signal_cellular_altadvanced

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

Citation Extractor & Accuracy Verifier (Anti-Hallucination)

Extracts every claim-citation pair from a draft document, verifies each citation against provided source material, flags fabricated or mis-attributed citations, and outputs a triaged audit table — the single most important guardrail for AI-assisted academic and journalistic writing.

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.

Source Credibility Evaluator (CRAAP + Bias Audit)

Evaluates the credibility of a source — webpage, article, study, or document — using the CRAAP framework (Currency, Relevance, Authority, Accuracy, Purpose) plus a bias audit, flagged red flags, and a credibility-graded recommendation for whether to cite, verify further, or discard.

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.

Hypothesis Generator with Falsifiability & Operationalization

Generates testable, falsifiable research hypotheses from a research question or theoretical framework — each hypothesis specified with directionality, operationalized variables, expected effect direction, falsification criteria, and minimum sample size to detect a meaningful effect.

star 0fork_right 247

bolt

pin_invoke