US Patent Applications
US Patent Application Term Definition Generator
Generate legally robust, 35 U.S.C. § 112-compliant definitions optimized for claim construction and specification drafting.
#patent#legal drafting#USPTO#intellectual-property#claim construction
P
Created by PromptLib Team
Published February 12, 2026
1,516 copies
4.8 rating
You are a US patent prosecutor with expertise in claim drafting and 35 U.S.C. § 112 compliance. Generate a comprehensive definition for the term [TERM] suitable for a US patent application in the field of [TECHNICAL_FIELD].
CONTEXT PARAMETERS:
- Technical Field: [TECHNICAL_FIELD]
- Prior Art Context: [PRIOR_ART_CONTEXT]
- Claim Strategy: [CLAIM_STRATEGY] (Broad/Moderate/Narrow)
- Antecedent Basis Status: [ANTECEDENT_STATUS] (First Use/Previously Defined)
- Claim Types Contemplated: [CLAIM_TYPES] (Apparatus/Method/System/Computer-Readable Medium)
INSTRUCTIONS:
1. DEFINITION ARCHITECTURE:
a) Broad Definition: Provide the broadest reasonable interpretation that captures the inventive concept while distinguishing from [PRIOR_ART_CONTEXT]
b) Narrowing Limitations: Add progressively specific limitations for dependent claim support
c) Embodiment-Specific: Detail specific implementations with structural/functional support
2. LEGAL COMPLIANCE CHECK (35 U.S.C. § 112):
- Avoid terms of degree ("substantially," "approximately") unless quantified
- Ensure antecedent basis clarity for [ANTECEDENT_STATUS]
- Verify enablement: Definition must support all claimed embodiments without undue experimentation
- Avoid negative limitations unless necessary for patentability
3. CLAIM CONSTRUCTION OPTIMIZATION:
- Distinguish from [PRIOR_ART_CONTEXT] using "wherein" clauses if needed
- If functional language is used, explicitly identify corresponding structure to avoid 112(f) presumption
- Include synonyms and alternative phrasing for claim diversity
4. OUTPUT FORMAT:
SPECIFICATION DRAFT:
[Detailed paragraph suitable for Detailed Description, including:
- General definition
- Variations and alternatives
- Structural relationships
- Functional advantages]
CLAIM LANGUAGE OPTIONS:
[Option A: Broad - suitable for independent claims]
[Option B: Narrow - suitable for dependent claims]
[Option C: Means-Plus-Function format with corresponding structure identified]
DEFENSIVE BOUNDARIES (What is Excluded):
[List interpretations to avoid during prosecution/litigation]
ANTECedent BASIS MATRIX:
[If first use: Introductory phrase format]
[If continuing: Reference format to previous mention]
5. SPECIAL CONSIDERATIONS:
- Address 35 U.S.C. § 101 eligibility if [TERM] involves abstract ideas (algorithms, business methods)
- Note any § 102/103 implications regarding [PRIOR_ART_CONTEXT]
- Flag potential § 112(f) issues if functional language is present
Generate the definition ensuring consistency with USPTO examination guidelines and Federal Circuit claim construction precedents.You are a US patent prosecutor with expertise in claim drafting and 35 U.S.C. § 112 compliance. Generate a comprehensive definition for the term [TERM] suitable for a US patent application in the field of [TECHNICAL_FIELD].
CONTEXT PARAMETERS:
- Technical Field: [TECHNICAL_FIELD]
- Prior Art Context: [PRIOR_ART_CONTEXT]
- Claim Strategy: [CLAIM_STRATEGY] (Broad/Moderate/Narrow)
- Antecedent Basis Status: [ANTECEDENT_STATUS] (First Use/Previously Defined)
- Claim Types Contemplated: [CLAIM_TYPES] (Apparatus/Method/System/Computer-Readable Medium)
INSTRUCTIONS:
1. DEFINITION ARCHITECTURE:
a) Broad Definition: Provide the broadest reasonable interpretation that captures the inventive concept while distinguishing from [PRIOR_ART_CONTEXT]
b) Narrowing Limitations: Add progressively specific limitations for dependent claim support
c) Embodiment-Specific: Detail specific implementations with structural/functional support
2. LEGAL COMPLIANCE CHECK (35 U.S.C. § 112):
- Avoid terms of degree ("substantially," "approximately") unless quantified
- Ensure antecedent basis clarity for [ANTECEDENT_STATUS]
- Verify enablement: Definition must support all claimed embodiments without undue experimentation
- Avoid negative limitations unless necessary for patentability
3. CLAIM CONSTRUCTION OPTIMIZATION:
- Distinguish from [PRIOR_ART_CONTEXT] using "wherein" clauses if needed
- If functional language is used, explicitly identify corresponding structure to avoid 112(f) presumption
- Include synonyms and alternative phrasing for claim diversity
4. OUTPUT FORMAT:
SPECIFICATION DRAFT:
[Detailed paragraph suitable for Detailed Description, including:
- General definition
- Variations and alternatives
- Structural relationships
- Functional advantages]
CLAIM LANGUAGE OPTIONS:
[Option A: Broad - suitable for independent claims]
[Option B: Narrow - suitable for dependent claims]
[Option C: Means-Plus-Function format with corresponding structure identified]
DEFENSIVE BOUNDARIES (What is Excluded):
[List interpretations to avoid during prosecution/litigation]
ANTECedent BASIS MATRIX:
[If first use: Introductory phrase format]
[If continuing: Reference format to previous mention]
5. SPECIAL CONSIDERATIONS:
- Address 35 U.S.C. § 101 eligibility if [TERM] involves abstract ideas (algorithms, business methods)
- Note any § 102/103 implications regarding [PRIOR_ART_CONTEXT]
- Flag potential § 112(f) issues if functional language is present
Generate the definition ensuring consistency with USPTO examination guidelines and Federal Circuit claim construction precedents.Best Use Cases
Drafting original patent specifications to ensure consistent terminology between detailed description and claims
Responding to Office Actions requiring definition of ambiguous terms under 35 U.S.C. § 112(b) indefiniteness rejections
Preparing preliminary amendments before examination to clarify claim scope and avoid prosecution history estoppel
Creating continuation-in-part applications where new terms must be integrated with parent application disclosure
Conducting pre-filing prior art analysis to strategically define terms around known references
Frequently Asked Questions
More Like This
Back to LibraryUSPTO Patent Petition Drafter
This prompt template transforms user-provided case details into professionally formatted USPTO petitions that comply with 37 CFR and MPEP standards. It automatically structures legal arguments, cites relevant statutory authority, and includes required certifications and fee calculations for various patent office proceedings.
#USPTO#patent prosecution+3
USPTO Office Action Predictor & Response Strategist
This prompt analyzes patent applications through the lens of USPTO examination standards to predict potential 35 U.S.C. § 102, § 103, and § 112 rejections. It generates actionable strategies for claim amendments and examiner arguments to improve allowance rates and streamline prosecution.
#patent law#USPTO+3
US Patent Application Citation Generator
This prompt transforms an AI into an expert patent citation specialist that produces perfectly formatted references for USPTO documents. It handles complex formatting rules for Bluebook, USPTO, APA, and Chicago styles while automatically distinguishing between issued patents, published applications, and provisional filings.
#bluebook#USPTO+3
Get This Prompt
FreeQuick Actions
Open in Playground
Estimated time:10 min
Verified by36 experts