---
name: patent-application-drafting
description: Use when drafting Chinese patent technical disclosures or patent application documents from inventor interviews, especially for software, AI, system, device, method, model-training, data-processing, visual monitoring, or engineering inventions. Use when the user wants to collect an invention idea, confirm technical completeness, prepare a patent disclosure, draft claims/specification/abstract/drawings, convert to Word, or review novelty, inventiveness, and practical applicability.
---

# Patent Application Drafting

## Purpose

Use this skill to turn an inventor's rough technical idea into a complete Chinese patent drafting package. The process must first confirm the technical solution is complete and effective, then produce the disclosure, claims, specification, abstract, drawings, Word documents, and a three-requirements review as requested.

This skill is for drafting support, not a substitute for a licensed attorney's final filing review.

## Core Rule: Confirm Before Drafting

Do not rush into final drafting from an incomplete invention idea. First gather and confirm:

1. applicant and inventor information;
2. product/system/application scenario;
3. existing technical problem;
4. complete technical solution and data/control flow;
5. essential technical features;
6. optional/alternative embodiments;
7. technical effects and measurable indicators;
8. implementation examples;
9. public disclosure status;
10. filing strategy: one core application or divisional/portfolio split.

If the inventor says they are still explaining, listen and only summarize briefly. Start structured drafting only after they clearly say the technical framework is complete or ask to begin sorting.

For the detailed interview checklist, read `references/inventor-interview.md` when gathering facts.

## Workflow

### 1. Intake and Listening

Identify whether the user is:

- still describing the invention;
- asking for technical-solution sorting;
- asking for a disclosure draft;
- asking for formal patent application documents;
- asking for drawings, Word files, or three-requirements review.

When the inventor is still describing, respond with short confirmations and record key points. Do not over-structure until asked.

### 2. Technical Completeness Check

Before drafting a disclosure or application, check whether the invention includes:

- the starting condition or input;
- the processing modules/steps;
- how each step is triggered;
- what data is generated, selected, labeled, trained, transmitted, or stored;
- how the system knows success/failure or confidence;
- what is executed locally vs cloud/server/platform;
- how the result is deployed or used;
- what is new compared with conventional practice;
- why the solution produces a technical effect.

If any key part is missing, ask focused questions. Prefer 3-6 concrete questions rather than a long questionnaire.

### 3. Technical Disclosure Draft

After confirmation, create a disclosure document with:

- invention name candidates;
- technical field;
- background technology;
- technical problems;
- technical solution overview;
- complete implementation process;
- system/module composition;
- core innovation points;
- technical effects;
- alternative embodiments;
- recommended claim layout;
- drawing suggestions;
- business/engineering examples;
- open issues for confirmation.

Use the structure in `references/drafting-outputs.md`.

### 4. Formal Application Draft

When the user asks for formal application files, draft:

- claims;
- specification;
- abstract;
- drawing descriptions;
- optional separate drawing source/figure notes.

Use one application with multiple statutory categories unless the user requests a portfolio split. For software/AI/system inventions, normally include method claims, system claims, electronic device claims, and computer-readable storage medium claims.

Keep the independent claim focused on the minimum necessary closed loop. Put implementation details, thresholds, versioning, manual review, privacy, rollback, and scenarios in dependent claims.

### 5. Drawings

Prepare drawings as simple black-and-white patent flowcharts/block diagrams:

- no color, shading, icons, or decorative elements;
- boxes, diamonds, arrows, and reference numerals where appropriate;
- figure captions outside the drawing image unless the user asks otherwise;
- each figure can be a separate PNG for Word insertion.

If the user asks to generate images, use the image generation tool. If the user asks for Word, insert the figures into a separate DOCX and add captions.

### 6. Word Deliverables

When asked for Word files, use the Documents skill if available. Produce at least:

- `01-正式申请文件-文本.docx`: claims, specification, and abstract;
- `02-正式申请文件-附图.docx`: description drawings with captions.

Attempt render/visual QA. If rendering fails because LibreOffice/soffice is unavailable, still deliver the DOCX and state that visual render QA could not be completed.

### 7. Final Submission Folder

When preparing final application materials, organize them in the simple submission folder template. The first-level folder name must be the patent application name:

```text
专利申请名称/
├── 00-提交清单.md
├── 01-正式申请文件-文本.docx
├── 02-正式申请文件-附图.docx
├── 03-附图JPG/
├── 04-请求书信息.md
└── 99-原始文件/
```

Use this structure as the default final handoff package. Keep it simple; do not add extra process folders unless the user asks.

- `00-提交清单.md`: checklist for completed claims, specification, abstract, drawings, JPG drawings, request-form information, abstract length, abstract figure inclusion in the description drawings, no comments/tracked changes, and handler account signature readiness.
- `03-附图JPG/`: JPG versions of figures when needed for filing; if an abstract figure is specified, that figure must also appear in the description drawings.
- `04-请求书信息.md`: request-form fields, including applicant, inventors, contact, address, phone, email, postcode, abstract figure, priority, genetic resources, biological material deposit, sequence listing, early publication, substantive examination, and handler/signature account.
- `99-原始文件/`: original source materials supplied by the user.

### 8. Three-Requirements Review

When asked to review patentability, analyze:

- novelty: whether the full combination is likely not identically disclosed;
- inventiveness: closest prior-art combinations and why the solution is not a simple aggregation;
- practical applicability: whether the solution can be manufactured/used and produces technical effects.

For high-stakes filing decisions or actual novelty search, browse or use official patent databases if the user asks for a search. Without a search, clearly state the review is preliminary and not a formal search conclusion.

Use `references/quality-review.md` for the review checklist.

## Drafting Principles

- Protect the technical mechanism, not only the business scenario.
- Convert business needs into objective technical problems.
- Avoid claim language that depends only on "improving user experience" or management rules.
- For AI inventions, identify training data generation, labeling, model training, model deployment, inference, feedback, and technical constraints.
- For edge/cloud systems, clearly separate端侧、云端、平台、设备、用户反馈、OTA and data-security roles.
- Add alternatives so claims are not tied to one model, one vendor, one threshold, or one business scenario.
- Keep file names clear and Chinese-friendly when working in a Chinese patent workspace.

## Output Naming

Use descriptive filenames. For final application packages, use:

- `00-提交清单.md`
- `01-正式申请文件-文本.docx`
- `02-正式申请文件-附图.docx`
- `03-附图JPG/图1.jpg`
- `04-请求书信息.md`
- `99-原始文件/`

For drafting-stage materials before final packaging, use names such as:

- `技术交底书.md`
- `正式申请文件-权利要求书.md`
- `正式申请文件-说明书.md`
- `正式申请文件-说明书摘要.md`
- `正式申请文件-附图草图.md`

When multiple inventions are present, prefix filenames with a short invention title.
