embodiment-description

Generate patent embodiment descriptions with reference numeral integration and claim-element coverage checks.

1|1|Updated May 19, 2026
One-click install
npx skills add https://github.com/zhuyingqin/ARIS-WEB --skill embodiment-description-zhuyingqin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: embodiment-description
Source: https://github.com/zhuyingqin/ARIS-WEB/tree/main/crates/runtime/assets/skills/embodiment-description
Command: npx skills add https://github.com/zhuyingqin/ARIS-WEB --skill embodiment-description-zhuyingqin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

It solves the problem of turning drafted patent claims and invention disclosures into detailed, enablement-focused embodiment text that consistently maps to the claim elements and figure numerals.

Core Features & Use Cases

  • Embodiment planning from claim categories: generates at least one embodiment per relevant claim category to cover method/system/apparatus style claims.
  • Step-by-step drafting with figure numeral integration: enforces consistent reference numeral rules (e.g., first mention with parentheses, later mention without) tied to FIG. 1/FIG. 2 series conventions.
  • Claim support verification: ensures each claim element appears in at least one embodiment and adds missing elements where needed.

Intended use cases

  • Drafting “实施例/embodiments” sections for patent specifications in English, using provided invention decomposition and claims.
  • Producing multiple alternative embodiments (best mode + variations) to strengthen enablement and support broader claim interpretation.

Quick Start

Use the embodiment-description skill to generate detailed embodiments that support patent/CLAIMS.md using patent/INVENTION_DISCLOSURE.md and any provided figures, writing the result into patent/specification/detailed_description.md.

Frequently Asked Questions about embodiment-description

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I draft patent embodiment descriptions that support my claims?

Drafting patent embodiment descriptions requires mapping detailed invention disclosures to claim elements while integrating figure reference numerals. This process generates enablement-focused text that teaches how to make and use the invention, ensuring every claim element appears in at least one embodiment.

What is the best way to ensure claim support in a patent specification?

Claim support verification checks that each claim element appears in at least one embodiment description and adds missing elements where needed. Generating multiple alternative embodiments, including best mode and variations, strengthens enablement and supports broader claim interpretation.

How do I integrate figure numerals consistently when writing patent embodiments?

Consistent figure numeral integration enforces reference numeral rules, such as using parentheses on first mention and omitting them later, tied to FIG. 1 and FIG. 2 series conventions. This ensures the detailed description aligns accurately with the provided patent drawings.

Can I generate multiple alternative embodiments from a single invention disclosure?

Generating multiple alternative embodiments from a single invention disclosure produces both best mode and variation examples. This approach strengthens enablement by covering different claim categories like method, system, and apparatus styles within the patent specification.

What do I need to provide to start drafting detailed patent embodiments?

Drafting detailed patent embodiments requires an invention disclosure, drafted claims, and optional figures with numeral indexing. Providing these inputs allows the workflow to generate structured specification text that avoids experimental performance metrics.

Why should patent embodiment descriptions avoid experimental performance metrics?

Patent embodiment descriptions avoid experimental performance metrics to prevent adding unnecessary experimental data that could limit claim scope. Structured embodiment workflows focus on teaching how to make and use the invention rather than presenting test results.