figure-description
/figure-description
Opisuje rysunki patentowe z numerami referencyjnymi i tworzy formalne opisy figur na podstawie dostarczonych plików.
- Repozytorium
- Athena ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 13.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 1
Brak sygnałów. Repozytorium zmienione 13.11.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Opisuje rysunki patentowe z numerami referencyjnymi i tworzy formalne opisy figur na podstawie dostarczonych plików.
Wyzwalacze z opisu
Argumenty
/figure-description [figure-directory-or-figure-list]
Oryginalny opis (EN)
Process user-provided patent figures and generate formal drawing descriptions. Use when user says \"Chart Processing\", \"figure description\", \"Annotations to the figure\", \"drawings description\", or wants to describe patent figures with reference numerals.
Jak działa
- Constants
- Inputs
- Workflow
- Key Rules
- Mirror description (additional to this open warehouse)
Podgląd SKILL.md
---
name: figure-description
description: "Process user-provided patent figures and generate formal drawing descriptions. Use when user says \"Chart Processing\", \"figure description\", \"Annotations to the figure\", \"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 (Annotations to the figure):
**For CN jurisdiction (Chinese)**:
```
Figure1Yes.[Invent Name]a map of the structure of the system;2Yes.[Invent Name]flow chart of methodologies;3Yes.[Specific components]A detailed chart of the structure;
```
**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.
## Mirror description (additional to this open warehouse)
- This document is considered upstream. ARIS mirrors in original;support files (scripts/、references/、../shared-references/)Not distributed with mirrors, full originals can be found at the upstream warehouse https://github.com/wanshuiyin/Auto-claude-code-research-in-sleep 。
- If supporting documents are cited for implementation skills, then the relative path should be parsed from the upstream warehouse.
Wersje
W bazie nie ma innych skilli o nazwie figure-description.
Migawka bazy z 13.11.2026 · wersja paczki 86edc45c5952 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100patentfig
Generuje przez API PatentFig rysunki patentowe z tekstu, wektoryzuje je do SVG, DXF lub PDF i konwertuje do TIFF, PDF lub PNG gotowych do zgłoszenia. - 100figure-bible
Tworzy i sprawdza plik motywu figures/theme.json z paletą i stylem, zanim skille figur zaczną generować obrazy. - 95figures
Składa rysunki i wykresy naukowe o rozmiarach w cm i eksportuje je jako SVG, PNG lub wektorowe PDF. - 100paper-figure
Generuje rysunki i tabele jakości publikacyjnej z wyników eksperymentów, także dla wpisów w CLAIMS_LEDGER.md tworzonych przez hook Ledger Figures. - 100paper-figure
Generuje rysunki i tabele jakości publikacyjnej z wyników eksperymentów, gdy potrzebne są wykresy do artykułu naukowego. - 100nature-paper-to-patent
Zamienia artykuły naukowe, prace dyplomowe, raporty, kod i rysunki na oparte na dowodach projekty chińskich zgłoszeń patentowych, mapując każdą zastrzeganą cechę do źródła.