| name | patent-builder |
| title | Patent Builder |
| description | Discovers patentable ideas, refines early concepts, analyzes implementations for patent potential, drafts patent disclosure materials, or reverse-lookups existing disclosures against new requirements to identify coverage gaps. Use when the user asks about patent idea mining, invention brainstorming, patentability-oriented technical analysis, invention disclosure drafting, prior-solution comparison, claim-feature extraction, or checking whether existing disclosures already cover a new feature or requirement. / 发现可专利技术想法，打磨早期发明概念，分析已有实现的专利潜力，起草专利交底材料，或根据新需求对已有交底书做覆盖度反查，识别保护空白。适用于专利点挖掘、发明构思启发、现有方案对比、专利性初步分析、专利交底书撰写与优化、或检查已有交底是否覆盖新功能或新需求。 |
| author | VinceZcrikl |
| author_url | https://github.com/VinceZcrikl/vinceZcrikl-skills/tree/main/skills/patent-builder |
| license | MIT |
| version | 0.1.0 |
| execution_mode | open |
| jurisdiction | general |
| practice | ip |
| language | en |
Patent Builder
Language
If the user is writing in Chinese, load reference/zh.md and follow its instructions instead of the English body below.
Use this skill to help users discover, refine, evaluate, and document potential patent ideas.
Do not provide legal conclusions. Treat novelty, inventiveness, and patentability comments as preliminary technical analysis. Recommend professional patent counsel for filing, claim drafting, clearance, or legal opinions.
Core principles
- Focus on technical problems, technical means, and technical effects.
- Separate confirmed implementation from optional embodiments.
- Distinguish common techniques from potentially inventive combinations.
- Prefer concrete mechanisms over broad statements such as "uses AI" or "improves experience".
- Do not use real examples unless the user provides them or explicitly asks for examples.
- Use neutral placeholders: "the system", "the module", "the data object", "the candidate item", "step N", "item A".
- Avoid unsupported claims such as "novel", "unique", or "patentable" unless clearly framed as preliminary.
Entry mode selection
Determine the user's starting point.
Mode A: Existing implementation
Use when the user provides a system, feature, prototype, architecture, code description, product workflow, or technical document.
Mode B: Initial idea
Use when the user has a preliminary concept, pain point, or possible solution but no implementation.
Mode C: Open exploration
Use when the user has no clear direction and wants guided brainstorming.
Mode D: Reverse disclosure lookup
Use when the user has one or more existing patent disclosures and wants to check whether a new requirement, feature, or implementation is already covered, identify protection gaps, or decide whether to file a new disclosure or extend an existing one.
If unclear, ask one concise question:
"Are we starting from an existing implementation, an initial idea, or open exploration?"
Universal workflow
Use this checklist and adapt the depth to the user's material.
Patent Builder Progress:
- [ ] 1. Identify the technical field and target scenario
- [ ] 2. Clarify the technical problem
- [ ] 3. Identify known or likely conventional approaches
- [ ] 4. Extract distinguishing technical features
- [ ] 5. Build candidate invention concepts
- [ ] 6. Evaluate novelty risk, inventiveness potential, feasibility, and value
- [ ] 7. Select the strongest invention direction
- [ ] 8. Draft or refine the patent disclosure
- [ ] 9. List open questions and confirmation points
