embodiment-description
🤖 AI Summary
Generates 1-3 detailed patent embodiments from an invention disclosure and claims, describing how to make/use the invention with reference numerals starting at 100.
How to Install
Claude Code:
git clone --depth 1 https://github.com/wanshuiyin/Auto-claude-code-research-in-sleep.git && cp Auto-claude-code-research-in-sleep/skills/embodiment-description ~/.claude/skills/embodiment-description -r# Embodiment Description
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.
## Constants
- `MIN_EMBODIMENTS = 1` — At least one complete embodiment required
- `MAX_EMBODIMENTS = 3` — Practical limit; more embodiments strengthen enablement
- `EMBODIMENT_STYLE = detailed` — `detailed` (full working example) or `outline` (sketch)
- `REFERENCE_NUMERAL_PREFIX = 100` — Starting reference numeral for first figure's components
## Inputs
1. `patent/INVENTION_DISCLOSURE.md` — invention decomposition (core/supporting/optional features)
2. `patent/CLAIMS.md` — drafted claims that the embodiments must support
3. User-provided figures (if any) in any directory
4. `patent/figures/numeral_index.md` if it exists (from `/figure-description`)
## Workflow
### Step 1: Plan Embodiments
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] |
### Step 2: Write Each Embodiment
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:
- Describe each step in order
- Reference figure numerals: "As shown in FIG. 1, at step 202, the processor 102 receives the input data 104..."
- Include specific parameters, ranges, and conditions
- Describe what happens at each decision point
For system/apparatus embodiments:
- Describe each component
- Reference figure numerals: "Referring to FIG. 1, the system 100 comprises a processor 102, a memory 104, and a communication interface 106..."
- Describe interconnections between components
- Describe operation of the system step-by-step
**Variations and alternatives**:
- "In some embodiments, the processor 102 may be a GPU, an FPGA, or an ASIC."
- "In another embodiment, the memory 104 may be replaced with a distributed storage system."
- "The parameters described above are exemplary; other values within the range [X, Y] are also contemplated."
These variations are critical -- they support broader claim interpretation.
### Step 3: Reference Numeral Integration
Ensure consistent reference numeral usage:
1. Every component mentioned must have a numeral
2. Numeral must appear first in parentheses after the component name: "the processor (102)"
3. Subsequent references: "the processor 102" (no parentheses)
4. Numbering follows figure series: 100-series for FIG. 1, 200-series for FIG. 2
**Format**:
- First mention: "the processor
Details
| Category | Design → ui |
| Source | wanshuiyin/Auto-claude-code-research-in-sleep |
| SKILL.md | View on GitHub → |
| Repo Stars | ★ 12.5K |
| Est. per Skill | N/A (shared across 74 skills from this repo) |
| Difficulty | Intermediate |
| Risk Level | N/A |
Related Skills
cirq
Cirq - Quantum Computing with Python Cirq is Google Quantum AI's open-source framework for designing
crewai
CrewAI Expert in CrewAI - the leading role-based multi-agent framework used by 60% of Fortune 500 co
not-a-vibe-coder
Not-a-Vibe-Coder A skill that turns any project idea — no matter how vague — into 8 living planning
embedding-strategies
Embedding Strategies Guide to selecting and optimizing embedding models for vector search applicatio
Works Well With
Skills from the same repository — often designed to work together
ablation-planner
Ablation Planner Systematically design ablation studies that answer the questions reviewers will ask
alphaxiv
AlphaXiv Paper Lookup Lookup paper: $ARGUMENTS > Quick single-paper reader with tiered source fallba
analyze-results
Analyze Experiment Results Analyze: $ARGUMENTS Workflow Step 1: Locate Results Find all relevant JSO