学术写作
未发现用户侧风险
专利附图说明生成
处理用户提供的专利附图并生成正式的附图说明。当用户说“附图处理”、“figure description”、“附图说明”、“drawings description”或想要描述带有参考标号的专利附图时使用。
文件预览
1 个文件
SKILL.md
4.9 KB · 可预览
---
name: figure-description
description: "Process user-provided patent figures and generate formal drawing descriptions. Use when user says \"附图处理\", \"figure description\", \"附图说明\", \"drawings description\", or wants to describe patent figures with reference numerals."
argument-hint: [figure-directory-or-figure-list]
allowed-tools: Bash(*), Read, Write, Edit, Grep, Glob, WebSearch, WebFetch
---
# Figure Description for Patents
Process patent figures and generate drawing descriptions based on: **$ARGUMENTS**
Unlike `/paper-figure` which generates data plots, this skill processes user-provided technical diagrams and assigns reference numerals.
## Constants
- `FIGURE_DIR = "patent/figures/"` — Output directory for figure descriptions
- `REFERENCE_NUMERAL_PREFIX = 100` — Starting numeral for first figure's components
- `NUMERAL_SERIES = 100` — Each figure uses a separate 100-series (Fig 1: 100-199, Fig 2: 200-299, etc.)
## Inputs
1. User-provided figures (PNG, JPG, SVG, PDF) — search for them in the project directory
2. `patent/INVENTION_DISCLOSURE.md` — for understanding what components to identify
3. `patent/CLAIMS.md` — for mapping numerals to claim elements
## Workflow
### Step 1: Discover Figures
1. Search the project directory for figure files:
- Check `patent/figures/`, `figures/`, root directory
- Look for PNG, JPG, SVG, PDF files
- Check INVENTION_BRIEF.md or INVENTION_DISCLOSURE.md for figure references
2. List all discovered figures with their paths
3. If figures are missing that claims require, note them as `[MISSING: description needed]`
### Step 2: Analyze Each Figure
For each figure found:
1. **Read the image** using the Read tool (supports image files)
2. **Identify components**: What labeled or visually distinct components are shown?
3. **Identify connections**: How do components relate to each other?
4. **Identify flow**: If it's a flowchart or sequence, what is the step order?
### Step 3: Assign Reference Numerals
For each figure, assign numerals using the series convention:
| Figure | Numeral Range |
|--------|-------------|
| FIG. 1 | 100-199 |
| FIG. 2 | 200-299 |
| FIG. 3 | 300-399 |
For each identified component:
- Assign the next available numeral in the series
- Cross-reference to the claim elements it supports
- Note if a component appears in multiple figures (use same numeral across figures)
### Step 4: Generate Drawing Descriptions
Write formal drawing descriptions (附图说明):
**For CN jurisdiction (Chinese)**:
```
图1是[发明名称]的系统结构示意图;
图2是[发明名称]的方法流程图;
图3是[具体组件]的详细结构示意图;
```
**For US/EP jurisdiction (English)**:
```
FIG. 1 is a block diagram illustrating the system architecture according to one embodiment;
FIG. 2 is a flowchart illustrating the method steps according to one embodiment;
FIG. 3 is a detailed view of the processing module of FIG. 1;
```
### Step 5: Generate Reference Numeral Index
Create a complete mapping:
```markdown
## Reference Numeral Index
| Numeral | Component Name | Figure(s) | Claim Element |
|---------|---------------|-----------|---------------|
| 100 | System | FIG. 1 | Claim X preamble |
| 102 | Processor | FIG. 1 | Claim X, element 1 |
| 104 | Memory | FIG. 1 | Claim X, element 2 |
| 106 | Communication bus | FIG. 1 | Claim X, element 3 |
| 200 | Method | FIG. 2 | Claim 1 preamble |
| 202 | Receiving step | FIG. 2 | Claim 1, step 1 |
| 204 | Processing step | FIG. 2 | Claim 1, step 2 |
```
### Step 6: Cross-Reference to Claims
Verify that every claim element has at least one reference numeral:
| Claim Element | Figure | Numeral | Status |
|---------------|--------|---------|--------|
| [element] | [which fig] | [numeral] | Covered / [MISSING] |
If any claim element has no corresponding figure or numeral, flag it:
- `[MISSING FIGURE: Need a diagram showing {element description}]`
- `[MISSING NUMERAL: Component {name} in figure {X} needs a numeral]`
### Step 7: Output
Write `patent/figures/figure_descriptions.md`:
```markdown
## Figure Descriptions
### FIG. 1 — [Description]
[Formal one-paragraph description with all reference numerals]
### FIG. 2 — [Description]
[Formal one-paragraph description with all reference numerals]
...
```
Write `patent/figures/numeral_index.md`:
```markdown
## Reference Numeral Index
[Complete table of all numerals, components, figures, and claim mappings]
```
## Key Rules
- Every component in every figure must have a reference numeral.
- Every reference numeral must be explained in the specification.
- Numeral series must be consistent: 100-series for FIG. 1, 200-series for FIG. 2.
- If the same component appears in multiple figures, use the SAME numeral.
- Do NOT modify user-provided figures -- only describe them.
- Flag missing figures that the claims require but the user has not provided.
- Drawing descriptions are one sentence each, in a consistent format.
SKILL.md
元数据
| name | figure-description |
|---|---|
| description | 处理用户提供的专利附图并生成正式的附图说明。当用户说“附图处理”、“figure description”、“附图说明”、“drawings description”或想要描述带有参考标号的专利附图时使用。 |
| argument-hint | ["figure-directory-or-figure-list"] |
| allowed-tools | Bash(*), Read, Write, Edit, Grep, Glob, WebSearch, WebFetch |
专利附图说明
基于以下参数处理专利附图并生成附图说明:$ARGUMENTS
与生成数据图的 /paper-figure 不同,此技能处理用户提供的技术图表并分配参考标号。
常量
FIGURE_DIR = "patent/figures/"— 附图说明的输出目录REFERENCE_NUMERAL_PREFIX = 100— 第一幅图组件的起始标号NUMERAL_SERIES = 100— 每幅图使用一个独立的100系列(图1:100-199,图2:200-299,等等)
输入
- 用户提供的附图(PNG、JPG、SVG、PDF)——在项目目录中搜索它们
patent/INVENTION_DISCLOSURE.md— 用于理解需要识别哪些组件patent/CLAIMS.md— 用于将标号映射到权利要求要素
工作流
步骤1:发现附图
- 搜索项目目录中的附图文件:
- 检查
patent/figures/、figures/、根目录 - 查找 PNG、JPG、SVG、PDF 文件
- 检查 INVENTION_BRIEF.md 或 INVENTION_DISCLOSURE.md 中的附图引用
- 检查
- 列出所有发现的附图及其路径
- 如果权利要求需要但缺少某些附图,请标记为
[MISSING: 需要描述]
步骤2:分析每幅附图
对每幅找到的附图:
- 读取图像,使用支持图像文件的 Read 工具
- 识别组件:显示了哪些标注或视觉上不同的组件?
- 识别连接:组件之间如何关联?
- 识别流程:如果是流程图或序列图,步骤顺序是什么?
步骤3:分配参考标号
对每幅图,使用系列惯例分配标号:
| 附图 | 标号范围 |
|---|---|
| 图1 | 100-199 |
| 图2 | 200-299 |
| 图3 | 300-399 |
对每个识别的组件:
- 分配系列中的下一个可用标号
- 交叉引用其支持的权利要求要素
- 注意组件是否出现在多幅图中(在多幅图中使用相同的标号)
步骤4:生成附图说明
撰写正式的附图说明(附图说明):
中国辖区(中文):
text
图1是[发明名称]的系统结构示意图;
图2是[发明名称]的方法流程图;
图3是[具体组件]的详细结构示意图;美国/欧洲辖区(英文):
text
FIG. 1 is a block diagram illustrating the system architecture according to one embodiment;
FIG. 2 is a flowchart illustrating the method steps according to one embodiment;
FIG. 3 is a detailed view of the processing module of FIG. 1;步骤5:生成参考标号索引
创建完整映射:
markdown
## 参考标号索引
| 标号 | 组件名称 | 附图 | 权利要求要素 |
|---------|---------------|-----------|---------------|
| 100 | 系统 | 图1 | 权利要求 X 前序 |
| 102 | 处理器 | 图1 | 权利要求 X,要素1 |
| 104 | 存储器 | 图1 | 权利要求 X,要素2 |
| 106 | 通信总线 | 图1 | 权利要求 X,要素3 |
| 200 | 方法 | 图2 | 权利要求1前序 |
| 202 | 接收步骤 | 图2 | 权利要求1,步骤1 |
| 204 | 处理步骤 | 图2 | 权利要求1,步骤2 |步骤6:与权利要求交叉引用
验证每个权利要求要素至少有一个参考标号:
| 权利要求要素 | 附图 | 标号 | 状态 |
|---|---|---|---|
| [要素] | [哪幅图] | [标号] | 已覆盖 / [缺失] |
如果任何权利要求要素没有对应的图或标号,请标记:
[缺失附图:需要显示{要素描述}的图表][缺失标号:图{X}中的组件{名称}需要一个标号]
步骤7:输出
写入 patent/figures/figure_descriptions.md:
markdown
## 附图说明
### 图1 — [描述]
[带有所有参考标号的正式一段描述]
### 图2 — [描述]
[带有所有参考标号的正式一段描述]
...写入 patent/figures/numeral_index.md:
markdown
## 参考标号索引
[所有标号、组件、附图和权利要求映射的完整表格]关键规则
- 每幅图中的每个组件都必须有参考标号。
- 每个参考标号都必须在说明书中解释。
- 标号系列必须一致:图1使用100系列,图2使用200系列。
- 如果相同组件出现在多幅图中,请使用相同的标号。
- 不要修改用户提供的附图——只对其进行描述。
- 标记权利要求需要但用户未提供的缺失附图。
- 附图说明每幅图一句话,格式一致。