메뉴
Write detailed embodiment descriptions for patent specifications. Use when user says "撰写实施例", "write embodiment", "实施例描述", "detailed description", or wants to describe how to practice an invention.
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/ThomasMoreAI/legal-skills-open --skill embodiment-description명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
Use when retrieving arbitration institutional rules (ICC, LCIA, SCC, SIAC, HKIAC, VIAC, МКАС/МАК при ТПП України, UNCITRAL) — fetching current version, verifying redaction applicable to the date of arbitration agreement, constructing URLs for official rule texts
Use when choosing the Polish legal regime for letters, requests, applications, complaints, petitions, public-information requests, KPA filings, PPSA complaints, RODO access requests, registry extracts, court-file access, tax/ZUS/cudzoziemcy/USC procedures, or professional lawyer letters. Prevents mixing UDIP, KPA, PPSA, RODO, registry, special-procedure, and advocate/radca letter regimes.
Use when preparing applications for recognition and enforcement of foreign arbitral awards in Poland, applications for setting aside arbitral awards under KPC art. 1205–1211, or opposing such applications — mapping Article V of the 1958 New York Convention to art. 1214–1215 of the Polish KPC, identifying grounds for refusal, structuring public policy arguments
SOC 직업 분류 기준
SKILL.md 표시 중
| name | embodiment-description |
| title | Embodiment Description |
| description | Write detailed embodiment descriptions for patent specifications. Use when user says "撰写实施例", "write embodiment", "实施例描述", "detailed description", or wants to describe how to practice an invention. |
| author | wanshuiyin |
| author_url | https://github.com/wanshuiyin/Auto-claude-code-research-in-sleep/tree/main/skills/embodiment-description |
| license | MIT |
| version | 0.1.0 |
| execution_mode | open |
| jurisdiction | general |
| practice | ip |
| language | en |
Write detailed embodiments for: $ARGUMENTS
Embodiments describe HOW to make and use the invention -- they are the patent equivalent of experiment sections, but describe the invention rather than evaluating it empirically.
MIN_EMBODIMENTS = 1 — At least one complete embodiment requiredMAX_EMBODIMENTS = 3 — Practical limit; more embodiments strengthen enablementEMBODIMENT_STYLE = detailed — detailed (full working example) or outline (sketch)REFERENCE_NUMERAL_PREFIX = 100 — Starting reference numeral for first figure's componentspatent/INVENTION_DISCLOSURE.md — invention decomposition (core/supporting/optional features)patent/CLAIMS.md — drafted claims that the embodiments must supportpatent/figures/numeral_index.md if it exists (from /figure-description)For each claim category (method, system, etc.), plan at least one embodiment:
| Embodiment | Covers Claims | Type | Key Variations |
|---|---|---|---|
| 1 | Claims 1, X | Best mode / preferred | [primary implementation] |
| 2 | Claims 2, 3 | Alternative | [different parameters/materials] |
| 3 | Claims 4, 5 | Additional alternative | [different configuration] |
For each embodiment, write a detailed description following this structure:
Opening paragraph: "In one embodiment, [invention summary with reference to what is being described]."
Component/step-by-step description:
For method embodiments:
For system/apparatus embodiments:
Variations and alternatives:
These variations are critical -- they support broader claim interpretation.
Ensure consistent reference numeral usage:
Format:
For each claim element, verify it appears in at least one embodiment:
| Claim Element | Embodiment | Reference Numeral | Description Paragraph |
|---|---|---|---|
| [element] | [which] | [numeral] | [paragraph reference] |
If any claim element lacks embodiment support, add the necessary description.
For method/software inventions, include:
Example:
In one embodiment, the method comprises the following steps:
At step 202, the processor 102 receives input data from the input device 108.
At step 204, the processor 102 extracts feature vectors from the input data using a convolutional neural network.
At step 206, the processor 102 applies the attention mechanism 110 to the feature vectors...
Embodiment sections are written to patent/specification/detailed_description.md (or appended to the specification structure).
Each embodiment section should be self-contained but cross-reference other embodiments when describing alternatives.