Yuan1z0825/nature-skills / skills/nature-paper-to-patent
nature-paper-to-patent
FlaggedTurn research papers or inventor materials into evidence-grounded Chinese invention patent drafts and technical disclosures. Use for 技术交底书、专利撰写、现有技术对比 and Chinese DOCX patent packages; not general manuscript writing.
references/patent-figure-guide.md
View on GitHub# Patent Figure Guide
## Method Flowcharts
Build the main method flowchart from the ordered operations in the independent method claim.
Use:
- black strokes and white fills;
- rectangular process nodes;
- solid directional arrows;
- figure numbers such as `图1`;
- step identifiers such as `S1`, `S2`, and `S3`;
- concise Chinese operation labels.
Write the final node as the concrete result of the method. Examples include:
- `输出缺陷检测结果`;
- `获得故障检测结果`;
- `输出目标探测结果`;
- `获得电池健康状态估计结果`;
- `输出目标类别和目标位置`.
Keep the result name identical to the independent claim. Do not use invented umbrella terms such as `技术结果`.
## Abstract Figure
Use the main overall method flowchart as the abstract figure unless another single figure better represents the principal technical solution.
The same figure may and normally should also appear in the specification as `图1`. Reuse the same drawing file, figure number, node labels, and arrows. Do not generate separate "abstract" and "specification" versions that differ in wording or flow.
The abstract figure must:
- represent the principal independent claim;
- show the main input, core operations, and specific output;
- remain readable without equations or experimental details;
- be generated as both SVG and PNG;
- be embedded in the abstract-figure DOCX, abstract DOCX, and specification DOCX.
Avoid:
- color as the only carrier of meaning;
- gradients, shadows, decorative icons, or photographic backgrounds;
- unsupported branches or modules;
- effect-only nodes such as "提高准确率";
- vague final nodes such as `输出技术结果`, `获得处理结果`, or `输出最终结果`;
- dense equations or experimental results inside nodes;
- inconsistent terminology between the figure and claims.
## Consistency Rules
Confirm:
1. every `claim_step` appears in a method claim;
2. an overall figure marked `complete_claim_flow` covers every numbered step of its referenced claim;
3. node order follows the claimed data flow;
4. every edge connects existing nodes;
5. every node is reachable in the intended flow;
6. the figure description uses the same figure number and title;
7. the embodiment explains each node's operation;
8. optional details remain outside the main flow unless they form a disclosed branch.
9. `abstract_figure_number` points to an existing complete main figure;
10. the abstract and specification reuse the same image file.
## Figure Set
For algorithm-related inventions, consider:
- overall method flowchart;
- system or model architecture;
- core module structure;
- training flow;
- inference flow;
- data preprocessing flow.
Generate only figures supported by the source. The bundled script currently renders deterministic method flowcharts. Describe unsupported figure types as `[TO CONFIRM: figure required]` rather than fabricating them.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| canvas-designanthropics/skillsCreate beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| docxanthropics/skillsUse this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', '.dotx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx or .dotx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| pdfanthropics/skillsUse this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| pptxanthropics/skillsUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates (.potx), layouts, speaker notes, or comments. Trigger whenever the user mentions "deck," "slides," "presentation," or references a .pptx or .potx filename, regardless of what they plan to do with the content afterward. If a .pptx or .potx file needs to be opened, created, or touched, use this skill. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |