jurisdiction-format

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Jurisdiction Format: Patent Filing Compilation

司法管辖区格式:专利提交文件编译

Compile the patent application into filing-ready format based on: $ARGUMENTS
Analogous to
/paper-compile
but for patent document formatting instead of LaTeX.
根据**$ARGUMENTS**将专利申请编译为可直接提交的格式
类似于
/paper-compile
工具,但针对专利文档格式而非LaTeX文档。

Constants

常量定义

  • JURISDICTION = "auto"
    — From pipeline or args:
    CN
    ,
    US
    ,
    EP
    ,
    ALL
  • PATENT_TYPE = "invention"
    invention
    (发明专利) or
    utility_model
    (实用新型, CN only)
  • OUTPUT_FORMAT = "markdown"
    markdown
    (for review) or
    docx
    (for filing, requires python-docx)
  • OUTPUT_DIR = "patent/output/"
    — Base output directory
  • JURISDICTION = "auto"
    — 来自流水线或参数:
    CN
    US
    EP
    ALL
  • PATENT_TYPE = "invention"
    invention
    (发明专利)或
    utility_model
    (实用新型,仅限CN)
  • OUTPUT_FORMAT = "markdown"
    markdown
    (用于审核)或
    docx
    (用于提交,需依赖python-docx)
  • OUTPUT_DIR = "patent/output/"
    — 基础输出目录

Inputs

输入文件

  1. patent/CLAIMS.md
    — drafted claims
  2. patent/specification/
    — all specification sections (title, technical_field, background, summary, drawings_description, detailed_description, abstract)
  3. patent/figures/
    — figure descriptions and numeral index
  4. patent/INVENTION_DISCLOSURE.md
    — for metadata
  1. patent/CLAIMS.md
    — 已撰写完成的权利要求书
  2. patent/specification/
    — 说明书所有章节(发明名称、技术领域、背景技术、发明内容、附图说明、具体实施方式、摘要)
  3. patent/figures/
    — 附图说明及编号索引
  4. patent/INVENTION_DISCLOSURE.md
    — 元数据文件

Shared References

参考文档

Load
../shared-references/patent-format-cn.md
for CNIPA document structure and formatting rules. Load
../shared-references/patent-format-us.md
for USPTO document structure. Load
../shared-references/patent-format-ep.md
for EPO document structure.
加载
../shared-references/patent-format-cn.md
获取CNIPA文档结构及格式规则。 加载
../shared-references/patent-format-us.md
获取USPTO文档结构。 加载
../shared-references/patent-format-ep.md
获取EPO文档结构。

Workflow

工作流程

Step 1: Determine Output Jurisdictions

步骤1:确定输出司法管辖区

From
$ARGUMENTS
or constant:
  • CN
    -> Generate CNIPA format only
  • US
    -> Generate USPTO format only
  • EP
    -> Generate EPO format only
  • ALL
    -> Generate all three formats
根据
$ARGUMENTS
或常量定义:
  • CN
    -> 仅生成CNIPA格式文件
  • US
    -> 仅生成USPTO格式文件
  • EP
    -> 仅生成EPO格式文件
  • ALL
    -> 生成上述三种格式文件

Step 2: Generate CN Format (if CN or ALL)

步骤2:生成中国格式(若选择CN或ALL)

Output to
patent/output/CN/
:
输出至
patent/output/CN/

权利要求书 (Claims)

权利要求书(Claims)

  • Extract claims from
    patent/CLAIMS.md
  • Format per CNIPA conventions:
    • Independent claims: "1. 一种[主题]的方法,...其特征在于..."
    • Dependent claims: "2. 根据权利要求1所述的方法,其特征在于..."
  • Ensure Chinese terminology is correct (所述, 其特征在于, 包括, 等)
  • patent/CLAIMS.md
    提取权利要求内容
  • 按照CNIPA规范格式化:
    • 独立权利要求:「1. 一种[主题]的方法,...其特征在于...」
    • 从属权利要求:「2. 根据权利要求1所述的方法,其特征在于...」
  • 确保中文术语准确(所述、其特征在于、包括等)

说明书 (Description)

说明书(Description)

Combine all specification sections in CNIPA order:
  1. 发明名称 (from title.md)
  2. 技术领域 (from technical_field.md)
  3. 背景技术 (from background.md)
  4. 发明内容 (from summary.md — split into 技术问题/技术方案/有益效果)
  5. 附图说明 (from drawings_description.md)
  6. 具体实施方式 (from detailed_description.md)
按照CNIPA规定的顺序合并所有章节:
  1. 发明名称(来自title.md)
  2. 技术领域(来自technical_field.md)
  3. 背景技术(来自background.md)
  4. 发明内容(来自summary.md — 拆分为技术问题/技术方案/有益效果)
  5. 附图说明(来自drawings_description.md)
  6. 具体实施方式(来自detailed_description.md)

说明书摘要 (Abstract)

说明书摘要(Abstract)

  • Extract from abstract.md
  • Verify word count <= 300 Chinese characters
  • Include most representative claim
  • 从abstract.md提取内容
  • 验证字数≤300个汉字
  • 包含最具代表性的权利要求

Format as markdown or docx

格式化为markdown或docx

If
OUTPUT_FORMAT = "markdown"
:
  • Write as separate .md files with clear section headers
If
OUTPUT_FORMAT = "docx"
:
  • Use python-docx to create Word documents matching CNIPA templates
  • Set font to 宋体 (SimSun) for body, 黑体 (SimHei) for headers
  • Standard margins (上下 2.54cm, 左右 3.17cm)
OUTPUT_FORMAT = "markdown"
  • 写入独立的.md文件,使用清晰的章节标题
OUTPUT_FORMAT = "docx"
  • 使用python-docx创建匹配CNIPA模板的Word文档
  • 正文字体设置为宋体(SimSun),标题字体设置为黑体(SimHei)
  • 标准页边距(上下2.54cm,左右3.17cm)

Step 3: Generate US Format (if US or ALL)

步骤3:生成美国格式(若选择US或ALL)

Output to
patent/output/US/
:
输出至
patent/output/US/

Claims Section

权利要求章节

  • Number all claims sequentially (1, 2, 3, ...)
  • Format per US conventions:
    • "1. A method for [purpose], comprising:"
    • "2. The method of claim 1, wherein..."
  • Ensure antecedent basis is correct ("a" -> "the")
  • 所有权利要求按顺序编号(1、2、3...)
  • 按照美国规范格式化:
    • 「1. A method for [purpose], comprising:」
    • 「2. The method of claim 1, wherein...」
  • 确保先行基础表述准确("a" -> "the")

Specification

说明书

Combine all sections in USPTO order:
  1. Title
  2. Cross-Reference to Related Applications (if any)
  3. Field of the Invention
  4. Background of the Invention
  5. Brief Summary of the Invention
  6. Brief Description of the Drawings
  7. Detailed Description of Preferred Embodiments
  8. Abstract
Format drawings references as "FIG. 1" (not "Figure 1").
按照USPTO规定的顺序合并所有章节:
  1. 发明名称
  2. 相关申请交叉引用(如有)
  3. 发明领域
  4. 发明背景
  5. 发明简要概述
  6. 附图简要说明
  7. 优选实施例详细说明
  8. 摘要
附图引用格式为「FIG. 1」(而非「Figure 1」)

Abstract

摘要

  • Extract from abstract.md
  • Verify word count <= 150 words / 2500 characters
  • 从abstract.md提取内容
  • 验证字数≤150词/2500字符

Application Data Sheet (ADS) Template

申请数据表(ADS)模板

Generate a skeleton ADS with:
  • Title
  • Inventor information (placeholder)
  • Application type
  • Entity status (small/micro/large)
生成ADS框架,包含:
  • 发明名称
  • 发明人信息(占位符)
  • 申请类型
  • 实体状态(小型/微型/大型)

Step 4: Generate EP Format (if EP or ALL)

步骤4:生成欧洲格式(若选择EP或ALL)

Output to
patent/output/EP/
:
输出至
patent/output/EP/

Claims Section

权利要求章节

  • Format in two-part form per Rule 43(1) EPC:
    • "1. A method for [purpose], comprising [known features], characterised in that [inventive features]."
  • Ensure the "characterised in that" phrase is present in all independent claims
  • 按照EPC第43(1)条规定采用两部分格式:
    • 「1. A method for [purpose], comprising [known features], characterised in that [inventive features].」
  • 确保所有独立权利要求均包含「characterised in that」表述

Description

说明书

Combine all sections in EPO Rule 42 order:
  1. Title of the Invention
  2. Technical Field
  3. Background Art
  4. Disclosure of the Invention (problem-solution-advantage)
  5. Description of Embodiments
  6. Brief Description of Drawings
  7. Reference Signs List (mandatory at EPO)
Format drawings references as "FIG. 1" or "Figure 1".
按照EPO第42条规定的顺序合并所有章节:
  1. 发明名称
  2. 技术领域
  3. 背景技术
  4. 发明公开(问题-解决方案-优势)
  5. 实施例说明
  6. 附图简要说明
  7. 参考符号列表(EPO强制要求)
附图引用格式可为「FIG. 1」或「Figure 1」

Abstract

摘要

  • Extract from abstract.md
  • ~150 words limit
  • 从abstract.md提取内容
  • 字数限制约150词

Step 5: Consistency Check

步骤5:一致性检查

Verify across all generated formats:
  • All claims are present in every format
  • Claim numbering is consistent
  • Reference numerals match specification across all formats
  • No format-specific requirements are violated
  • Language is correct for each jurisdiction (Chinese for CN, English for US/EP)
验证所有生成格式的一致性:
  • 所有权利要求在各格式中均完整存在
  • 权利要求编号一致
  • 参考编号在所有格式的说明书中匹配
  • 未违反任何格式特定要求
  • 语言符合对应司法管辖区要求(CN为中文,US/EP为英文)

Step 6: Output Summary

步骤6:输出汇总

Write
patent/output/OUTPUT_SUMMARY.md
:
markdown
undefined
写入
patent/output/OUTPUT_SUMMARY.md
markdown
undefined

Patent Filing Documents

Patent Filing Documents

Generated Files

Generated Files

CN (CNIPA)

CN (CNIPA)

FileDescriptionStatus
权利要求书.mdClaims in CN formatComplete
说明书.mdDescription in CN formatComplete
说明书摘要.mdAbstract (CN)Complete
FileDescriptionStatus
权利要求书.mdClaims in CN formatComplete
说明书.mdDescription in CN formatComplete
说明书摘要.mdAbstract (CN)Complete

US (USPTO)

US (USPTO)

FileDescriptionStatus
claims.mdClaims in US formatComplete
specification.mdDescription in US formatComplete
abstract.mdAbstract (US)Complete
ads_template.mdApplication Data Sheet skeletonComplete
FileDescriptionStatus
claims.mdClaims in US formatComplete
specification.mdDescription in US formatComplete
abstract.mdAbstract (US)Complete
ads_template.mdApplication Data Sheet skeletonComplete

EP (EPO)

EP (EPO)

FileDescriptionStatus
claims.mdClaims in EP formatComplete
description.mdDescription in EP formatComplete
abstract.mdAbstract (EP)Complete
FileDescriptionStatus
claims.mdClaims in EP formatComplete
description.mdDescription in EP formatComplete
abstract.mdAbstract (EP)Complete

Consistency Check

Consistency Check

  • All claims present in all formats
  • Reference numerals consistent
  • Language correct per jurisdiction
undefined
  • All claims present in all formats
  • Reference numerals consistent
  • Language correct per jurisdiction
undefined

Key Rules

核心规则

  • Never mix jurisdiction formats (e.g., do not include "其特征在于" in US claims).
  • Claims must be identical in technical content across jurisdictions, only the format differs.
  • For CN output, verify Chinese patent terminology is correct and consistent.
  • For EP output, the two-part claim form is mandatory -- every independent claim must have "characterised in that."
  • Abstract word limits are jurisdiction-specific and must be verified.
  • The jurisdiction-format skill does NOT modify claim content -- it reformats existing content only.
  • If
    OUTPUT_FORMAT = "docx"
    , check that python-docx is available; if not, fall back to markdown.
  • 切勿混合不同司法管辖区的格式(例如,不要在美国权利要求中加入「其特征在于」)。
  • 各司法管辖区的权利要求技术内容必须完全一致,仅格式可不同。
  • 针对CN输出,需验证中文专利术语的准确性和一致性。
  • 针对EP输出,两部分权利要求格式为强制要求——所有独立权利要求必须包含「characterised in that」。
  • 摘要字数限制因司法管辖区而异,必须严格验证。
  • 本司法管辖区格式工具不会修改权利要求内容——仅对现有内容进行格式转换。
  • OUTPUT_FORMAT = "docx"
    ,需检查python-docx是否可用;若不可用,自动 fallback 至markdown格式。