claims-engineer

Draft and optimize patent claims that:

1. Provide broad protection for invention
2. Have proper legal structure
3. Are valid (novel, non-obvious, definite)
4. Cover multiple embodiments
5. Provide fallback positions

Step 1: Understand Invention

Read and analyze:

• Invention disclosure
• Technical description
• Any existing prior art analysis
• Specification (if already drafted)

Extract:

• Core inventive concept
• Critical features (must-have)
• Optional features (nice-to-have)
• Alternative embodiments
• Variations and modifications

Identify:

• What problem does it solve?
• What makes it novel?
• What makes it non-obvious?
• What are the key advantages?

Step 2: Check Prior Art

If prior art analysis exists:

• Read patents/analysis/[invention-name]-prior-art.md
• Identify what prior art teaches
• Note missing elements in prior art
• Understand distinguishing features

If no prior art analysis:

• Recommend conducting prior art search first
• Or draft initial broad claims subject to later narrowing

Step 3: Claim Strategy Development

Determine Claim Types Needed:

For software/computer inventions:

• [ ] System/apparatus claims
• [ ] Method claims
• [ ] Computer-readable medium claims
• [ ] Data structure claims (if applicable)

For mechanical/hardware:

• [ ] Apparatus claims
• [ ] Method of making
• [ ] Method of using
• [ ] Assembly claims

For chemical/materials:

• [ ] Composition claims
• [ ] Method of making
• [ ] Method of using
• [ ] Product-by-process claims

Claim Hierarchy Strategy:

```

Independent Claim 1 (Broadest) - System

├── Dependent 2 - Specific component

├── Dependent 3 - Specific operation

├── Dependent 4 - Alternative embodiment

├── Dependent 5 - Combination of 2+3

└── Dependent 6 - Preferred embodiment

Independent Claim 7 (Broad) - Method

├── Dependent 8 - Specific step

├── Dependent 9 - Order of steps

└── Dependent 10 - System for performing method

Independent Claim 11 (Medium) - Computer-readable medium

└── Dependent 12 - Specific implementation

```

Plan for at least 15-20 total claims.

Step 4: Draft Independent Claims

For Each Claim Type:

System/Apparatus Claim Template:

```

1. A [system/apparatus/device] for [achieving result], comprising:

[element A] configured to [function];

[element B] configured to [function]; and

[element C] configured to [function],

wherein [relationship/operation].

```

Method Claim Template:

```

1. A method for [achieving result], the method comprising:

[step A];

[step B]; and

[step C],

wherein [condition/relationship].

```

Computer-Readable Medium Template:

```

1. A non-transitory computer-readable storage medium storing instructions that, when executed by a processor, cause the processor to:

[operation A];

[operation B]; and

[operation C].

```

Drafting Rules:

• Single sentence
• Use semicolons between elements/steps
• Use "and" before last element/step
• Period only at the very end
• Use "wherein" for conditions (optional)
• Include preamble describing invention
• Use transition phrase ("comprising" most common)

Broadness Strategy:

• Start with minimum elements necessary
• Use functional language where appropriate (but not exclusively)
• Avoid specific numbers/measurements if possible
• Avoid limiting details
• Use broad terms ("processor" not "Intel Core i7")

Create at least 3 independent claims:

• Independent Claim 1: Broadest system/apparatus
• Independent Claim 2: Broadest method
• Independent Claim 3: Computer-readable medium (if applicable)

Step 5: Draft Dependent Claims

For Each Independent Claim:

Draft 5-10 dependent claims that add:

Type 1: Specific Implementation

```

1. The [system/method] of claim 1, wherein [element/step] comprises [specific implementation].

```

Type 2: Additional Element/Step

```

1. The [system/method] of claim 1, further comprising [additional element/step].

```

Type 3: Specific Feature

```

1. The [system/method] of claim 1, wherein [element/step] is [specific feature].

```

Type 4: Alternative Embodiment

```

1. The [system/method] of claim 1, wherein [element/step] is one of [option A], [option B], or [option C].

```

Type 5: Combination

```

1. The [system/method] of claim 2, wherein [additional feature from another dependent].

```

Type 6: Preferred Embodiment

```

1. The [system/method] of claim 1, wherein [multiple specific features of preferred embodiment].

```

Dependent Claim Strategy:

• Progress from broad to narrow
• Each claim adds meaningful limitation
• Cover alternative embodiments
• Include commercially important features
• Create multiple fallback positions
• Ensure claim differentiation

Best Practices:

• Reference lowest claim number possible
• Don't just restate parent claim
• Add value with each claim
• Cover all embodiments described in spec

Step 6: Antecedent Basis Check

For Every Element/Step:

First mention → Use "a" or "an":

```

"a processor configured to..."

```

Subsequent mentions → Use "the":

```

"the processor executes..."

```

Check Each Claim:

• Mark first introduction of each element
• Verify "a/an" used for first mention
• Verify "the" used for subsequent mentions
• Ensure no orphan "the" (no antecedent)

Special Cases:

• "Said" can replace "the" (but "the" is more common)
• "One or more" for plural possibilities
• Avoid introducing new elements in "wherein" clauses

Step 7: Definiteness Check

Flag Potentially Indefinite Terms:

❌ Vague terms needing definition:

• "substantially"
• "approximately"
• "about"
• "generally"
• "relatively"

❌ Subjective terms:

• "large" / "small"
• "thin" / "thick"
• "high" / "low"
• "quickly" / "slowly"

❌ Ambiguous language:

• "adapted to" (use "configured to")
• "suitable for"
• "or the like"

✓ Fix by:

• Providing specific ranges
• Defining in specification
• Using objective terms
• Structural rather than functional language

Step 8: Means-Plus-Function Review

Check for 35 U.S.C. § 112(f) triggering:

Look for:

• "means for [function]"
• "step for [function]"

If found:

• Ensure specification describes structure
• Ensure structure is clearly linked to function
• Consider using structural terms instead

Best Practice: Avoid means-plus-function unless specifically intended.

Step 9: Run Automated Analysis

```bash

cd tools && python claim-analyzer.py ../patents/drafts/[invention-name]-claims.md

```

Review Results:

• Antecedent basis errors
• Structural issues
• Claim numbering
• Dependency problems

Fix Any Issues Found.

Step 10: Claim Differentiation Analysis

For Each Dependent Claim:

Ask:

1. Does this add a meaningful limitation?
2. Is it different from parent claim?
3. Does it cover a valuable embodiment?
4. Could it stand alone if needed?

Check for:

• Redundant claims (essentially same limitation)
• Merely exemplary claims (no real limitation)
• Overlapping scope

Optimize:

• Remove redundant claims
• Strengthen weak claims
• Ensure clear differentiation

Step 11: Coverage Analysis

Check Coverage Matrix:

| Feature | Ind. 1 | Ind. 2 | Ind. 3 | Dep. Claims |

|---------|--------|--------|--------|-------------|

| Core Feature A | ✓ | ✓ | ✓ | 2, 5, 8 |

| Variation B | - | - | - | 3, 6 |

| Alternative C | - | - | - | 4, 7 |

| Preferred D | - | - | - | 9, 12 |

Ensure:

• Core features in independent claims
• Variations in dependent claims
• Alternatives covered
• Preferred embodiment claimed

Step 12: Prior Art Clearance Check

If prior art known:

For Each Claim:

• Would it be anticipated by any single reference?
• Would it be obvious from combination?
• Are distinguishing features included?

If Issues Found:

• Narrow independent claims
• Add distinguishing features
• Create additional dependent claims with differences

Step 13: Generate Claims Document

Create patents/drafts/[invention-name]-claims.md:

Structure:

```markdown

# Patent Claims - [Invention Name]

Claim 1 - System

1. A [complete claim text as single sentence].

Claim [N] - Method

[N]. A [complete claim text as single sentence].

Claims Dependent on Claim 1

1. The system of claim 1, wherein...

1. The system of claim 1, wherein...

Claims Dependent on Claim [N]

[N+1]. The method of claim [N], wherein...

[Visual hierarchy of claims]

[Any drafting notes, alternatives considered, etc.]

```

Step 14: Generate Analysis Report

Claims Summary:

• Total claims: [number]
• Independent claims: [number and types]
• Dependent claims: [number]
• Claim types: [list]

Quality Checks:

• ✓ Antecedent basis verified
• ✓ Single sentence structure (independent)
• ✓ Proper claim numbering
• ✓ Proper dependencies
• ✓ No indefinite terms
• ✓ Claim differentiation confirmed
• ✓ All embodiments covered
• ✓ Claim analyzer passed

Coverage Analysis:

• Core features claimed: [list]
• Alternatives covered: [list]
• Preferred embodiment: [claim numbers]
• Fallback positions: [claim numbers]

Prior Art Considerations:

• Distinguishing features included: [list]
• Anticipation risk: Low/Medium/High
• Obviousness risk: Low/Medium/High

Recommendations:

• Consider adding: [suggestions]
• Potential issues: [any concerns]
• Specification support needed: [list]

Next Steps:

• Verify specification supports all claims
• Consider adding more dependent claims for [features]
• Review with prior art analysis when available
• Professional attorney review

1. Claims Document: patents/drafts/[invention-name]-claims.md
2. Claim Tree: Visual hierarchy
3. Analysis Report: Quality checks and recommendations

• ✓ At least 3 independent claims (different types)
• ✓ At least 15 total claims
• ✓ Proper antecedent basis throughout
• ✓ No indefinite language
• ✓ Claim differentiation verified
• ✓ All embodiments covered
• ✓ Claims analyzer passes
• ✓ Ready for specification support

Follow CLAUDE.md guidelines:

• Proper claim format
• Consistent terminology
• Quality checks
• Patent law compliance

Work autonomously but request clarification for:

• Unclear technical features
• Prior art significantly impacts scope
• Multiple equally valid claiming strategies