Skip to content
Legal
Command

/create-epo-patent

Create a complete EPO-compliant patent application from invention disclosure through filing-ready package

BOOST
From plugin
claude-patent-creator-standalone
20316 skills13 agents16 commands1 hook
Install
> /plugin marketplace add RobThePCGuy/Claude-Patent-Creator
> /plugin install claude-patent-creator-standalone@claude-patent-creator

How it fires

How this command gets triggered: by you, by Claude, or both.

  • Fires itselfClaude auto-loads it when your prompt matches the work.
  • You can call itInvoke it directly when you want it.
  • Slash command/create-epo-patent

Context preview

What this command does when you run it.

Create a complete EPO-compliant patent application from invention disclosure through filing-ready package

Command definition

create-epo-patent.md
description: Create a complete EPO-compliant patent application from invention disclosure through filing-ready package
allowed-tools: Bash, Read, Write

Create EPO Patent Application

Guides you through creating a complete European patent application compliant with the EPC.

What This Command Does

Orchestrates the complete EPO patent application creation process:

1. **Prior Art Search** (15-30 min) 2. **Claims Drafting** (30-60 min) 3. **Specification Writing** (60-120 min) 4. **Diagrams Generation** (15-30 min) 5. **EPO Compliance Checking** (15-20 min) 6. **Final Assembly** (10-15 min)

**Total Time**: 2.5-4.5 hours for complete EP utility patent application

Process

Step 1: Gather Invention Information

I'll interview you about your invention:

  • What problem does it solve?
  • How does it work (high-level)?
  • What are the key components or steps?
  • What makes it novel/different from the closest prior art?
  • Are there any working prototypes or examples?
  • Is this a direct EP filing or Euro-PCT national phase entry?

Step 2: Prior Art Search

I'll search for relevant prior art using:

  • **BigQuery** (100M+ worldwide patents, filter country="EP" for EP patents)
  • **EPO OPS API** (European patent register, full-text EP documents)
  • **CPC classification** search focused on EPO-heavy technology areas

**Deliverable**: Prior art search report with novelty/inventive step assessment

Step 3: Draft Claims (EPO Format)

I'll draft claims following EPO requirements:

**Independent Claims** (Rule 43(1) EPC):

  • Two-part form: preamble + "characterised in that" + characterizing portion
  • Based on closest prior art identified in Step 2
  • Clear, concise, supported by description (Art. 84 EPC)

**Dependent Claims**:

  • Proper back-references
  • Further technical features
  • Fallback positions for prosecution

**Claim Categories**:

  • Product/apparatus claims
  • Method/process claims
  • Use claims (where appropriate)
  • No method-of-treatment claims (Art. 53(c) EPC)

**Deliverable**: Complete claims section (15-25 claims, EPO two-part form)

Step 4: Write Specification (Rule 42 EPC)

I'll write the description following EPO section order:

1. **Title** - Clear, concise, matches claims scope 2. **Technical Field** - Art to which the invention relates 3. **Background Art** - Prior art documents with citations (D1, D2...) 4. **Technical Problem** - Problem-solution approach (EPO standard) 5. **Disclosure of the Invention** - How the invention solves the problem 6. **Brief Description of Drawings** - Figure list 7. **Detailed Description** - At least one embodiment in detail 8. **Industrial Applicability** - If not obvious from description

**Key EPO Differences**:

  • Problem-solution approach is central
  • Prior art must be cited in description
  • Best mode not strictly required (unlike USPTO)
  • Industrial applicability section may be needed
  • Reference signs in claims correspond to description/drawings

**Deliverable**: Complete specification (20-50 pages, EPO format)

Step 5: Generate Diagrams

I'll create patent figures following Rule 46 EPC:

  • No text in drawings (except single words like "water", "steam")
  • Reference numbers matching description
  • A4 format with EPO margin requirements
  • Black lines, sufficiently dense

**Deliverable**: 3-10 patent figures (SVG/PNG)

Step 6: EPO Compliance Check

I'll validate the complete application:

  • Run EPO claims analysis (Art. 84 EPC - clarity, conciseness, support)
  • Check description format (Rule 42 EPC)
  • Verify formalities (Rules 42-49 EPC)
  • Check for excluded subject matter (Art. 52(2), Art. 53 EPC)
  • Fix any critical issues found

**Deliverable**: EPO compliance report + fixes

Step 7: Assemble Filing Package

I'll create the final EP filing package:

  • Description (Rule 42 format)
  • Claims (Rule 43 two-part form)
  • Abstract (Rule 47, max 150 words)
  • Drawings (Rule 46 compliant)
  • Request for Grant (Form 1001 guidance)
  • Priority document references
  • Fee calculation

**Deliverable**: EPO-ready filing package

Output Structure

All files will be organized as:

epo-patent-application-[date]/
├── 01-research/
│   ├── invention-disclosure.md
│   ├── prior-art-search-report.md
│   ├── top-10-patents.md
│   ├── novelty-assessment.md
│   └── inventive-step-assessment.md
├── 02-claims/
│   ├── claims-draft.md
│   ├── claims-final.md
│   ├── claims-two-part-form.md
│   └── claims-analysis.md
├── 03-specification/
│   ├── title-abstract.md
│   ├── specification-full.md
│   ├── problem-solution.md
│   └── specification-analysis.md
├── 04-figures/
│   ├── fig1-system-diagram.svg
│   ├── fig2-method-flowchart.svg
│   ├── fig3-component-detail.svg
│   └── figures-description.md
├── 05-compliance/
│   ├── art84-claims-compliance.md
│   ├── rule42-description-compliance.md
│   ├── formalities-check.md
│   └── excluded-subject-matter-check.md
└── 06-filing-package/
    ├── complete-application.md
    ├── form-1001-guidance.md
    ├── fee-calculation.md
    ├── priority-references.md
    └── filing-checklist.md

Requirements

Before running this command:

1. **MPEP/EPC Index Built**:

  • Run `/setup-patent-system` first (one-time)

2. **BigQuery Configured** (for patent search):

  • Google Cloud project created
  • BigQuery API enabled
  • Authenticated: `gcloud auth application-default login`
  • Environment variable: `GOOGLE_CLOUD_PROJECT=your-project-id`

3. **Graphviz Installed** (for diagrams):

  • Windows: `choco install graphviz`
  • Linux: `sudo apt install graphviz`
  • Mac: `brew install graphviz`

Options

You can customize the process:

**Filing Route**:

  • **Direct EP**: File directly at EPO
  • **Euro-PCT**: Enter European regional phase from PCT application

**Scope**:

  • **Quick**: Minimal claims + specification outline
  • **Standard** (default): Complete application
  • **Comprehensive**: Multiple embodiments + extensive examples

**Prior Art Depth**:

  • **Basic**: Keywords only (15 min)
  • **Standard** (
Read more
Ships withclaude-patent-creator-standalone

An AI-powered patent creation and analysis system for Claude Code. I built this because I needed to file a patent myself. I used AI to build the system, used the system to file the patent, and it worked. Now it's open source so anyone can use it.

Get the whole plugin