Skip to content
Automation
Skill

/figure-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.

From plugin
aris
19k87 skills1 agent1 command

Claude Code

$ npx -y skills add wanshuiyin/Auto-claude-code-research-in-sleep --skill figure-description --agent claude-code

SKILL.md

figure-description.SKILL.md
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:

## 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`:

## 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`:

## 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.
Read more
@wanshuiyin
Ships witharis

· · · · · · · · 💬 Join Community · 🌱 ARIS is a methodology, not a platform. What matters is the research workflow — take it wherever you go.

19k87 skills1 agent
Get the whole plugin

Stars on GitHub

Momentum

stars in total
19.1k
Star history of wanshuiyin/Auto-claude-code-research-in-sleep on GitHub, a chart by star-history.com

Other skills on aris.

ablation-planner

ablation-planner

Use when main results pass result-to-claim (claim_supported=yes or partial) and ablation studies are needed for paper submission.

@wanshuiyin@wanshuiyinInstall Skill
alphaxiv

alphaxiv

Quick single-paper lookup via AlphaXiv LLM-optimized summaries with tiered source fallback. Use when user says "explain this…

@wanshuiyin@wanshuiyinInstall Skill
analyze-results

analyze-results

Analyze ML experiment results, compute statistics, generate comparison tables and insights. Use when user says "analyze results",…

@wanshuiyin@wanshuiyinInstall Skill
arxiv

arxiv

Search, download, and summarize academic papers from arXiv. Use when user says "search arxiv", "download paper", "fetch arxiv",…

@wanshuiyin@wanshuiyinInstall Skill
auto-paper-improvement-loop

auto-paper-improvement…

Autonomously improve a generated paper via GPT-6-Astra xhigh review → implement fixes → recompile, for 2 rounds. Use when user…

@wanshuiyin@wanshuiyinInstall Skill
auto-review-loop-llm

auto-review-loop-llm

Autonomous research review loop using any OpenAI-compatible LLM API. Configure via llm-chat MCP server or environment variables.…

@wanshuiyin@wanshuiyinInstall Skill

More skills from other plugins.

agent-builder

agent-builder

Load immediately after an Agent intent, before the first agent_builder_* call. Governs how you create, configure, test, and…

n8n12d209k
@n8n-io@n8n-ioInstall Skill
browser-use

browser-use

Direct browser control via CDP for web interaction: automation, scraping, testing, screenshots, and site/app work. Also covers…

@browser-use@browser-useInstall Skill
agent-browser

agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling…

@vercel-labs-2@vercel-labs-2Install Skill
add-anydoc

add-anydoc

Add local office-document-to-Markdown conversion to NanoClaw agent containers with the pinned Firecrawl AnyDoc CLI. Use when…

@nanocoai@nanocoaiInstall Skill

Questions about figure-description.

Which coding agents can use figure-description?
figure-description installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.