patent-write

Chinese invention patent drafting

When to use

The user wants to write a Chinese invention patent
The user wants to supplement a certain section, such as the abstract, claims, or specific embodiments
The user has provided a reference patent and hopes to distill the writing method, structure, and expression patterns
The user wants to consolidate, converge, or check terminology consistency in an existing patent draft

User expression / keywords	Execution file
Complete patent, full text, complete specification, help me write the entire patent	reference/full-patent.md
Title, name, title optimization, title convergence	reference/title.md
Abstract	reference/abstract.md
Background technology, defects of existing technology	reference/background.md
Summary of the invention, technical solution, beneficial effects	reference/invention-content.md
Claims, independent claims, dependent claims	reference/claims.md
Description of drawings, figure numbers	reference/figures-desc.md
Drawing creation (Draw.io black-and-white Chinese)	reference/figures-drawio.md
Specific embodiments, examples	reference/implementation.md
Consolidation, checking, terminology consistency, self-check	reference/review.md
Reference patent distillation, imitation writing patterns, structure extraction	reference/distill.md

Prioritize collecting the following materials, and supplement whatever is missing:

Technical solution description: what problem is solved, what the core means are
Existing draft: any existing part of the title, abstract, claims, or specification
Reference patent: used to distill structure, language, and granularity, not to be directly copied
Drawings or flowcharts: module diagrams, flowcharts, architecture diagrams, sequence diagrams
Innovation points: specific differences and effects relative to existing technology

If the user wants to write the full text, proceed by default in the following order:

Read the writing rules, structure templates, and taboos of the corresponding reference
Write strictly around the materials provided by the user, and do not add nonexistent experimental data, implementation results, or hardware parameters
In the same round of output, provide finished products as much as possible, not just principles
If the information is insufficient to support formal patent text, first list the missing items, then provide an actionable draft

Do not fabricate: do not write modules, steps, experimental data, or performance indicators that are not in the materials
Structure first: first define the protection skeleton, then write the expanded text
Unified terminology: use only one main designation for the same object throughout the text
Technical correspondence: background defects, invention objectives, technical solution, and beneficial effects must correspond one to one
Write less empty talk: avoid having only functional results without an implementation path
Broad first, then narrow: the independent claim summarizes the core solution, and the dependent claims then refine the steps, conditions, modules, and formulas

Titles should preferably follow the common naming structure of "method, system, device, and medium"
Write the abstract as "disclosed content + core steps + technical effects", and do not copy the long sentence patterns of the claims
The background art should describe the specific defects of existing methods, not just industry trends
In the summary of the invention, first write the purpose, then the technical solution, then the beneficial effects
Claim 1 is responsible for the overall process or core modules; dependent claims are responsible for detailing sub-steps, parameters, constraints, and dependency relationships
The specific embodiments should form a closed loop with the drawings, step numbers, and module names