What problem does it solve? Drafting patent applications requires navigating complex USPTO rules like 35 USC 101, 102, 103, and 112, where small mistakes such as missing antecedent basis or means-plus-function language can fatally narrow or invalidate claims. ## Core Features & Use Cases - Claim Drafting Guidance: Provides patterns for method, system, apparatus, CRM, and product-by-process claims with correct transitional phrases like 'comprising' versus 'consisting of'. - Rejection Risk Diagnosis: Identifies critical failure modes including 112(f) means-plus-function traps, 112(b) indefiniteness, 101 abstract idea rejections under Alice/Mayo, and new matter violations under 35 USC 132. - Automated Validation Rules: Applies regex-based checks to claim files to detect means-plus-function language, missing antecedents, closed claim language, and generic computer implementations. - Use Case: When drafting a software patent, use this Skill to write claims with structural language, multiple embodiments in the specification, and fallback dependent claims that survive examiner rejections. ## Quick Start Draft an independent method claim and three dependent claims for my data processing invention, checking for antecedent basis and means-plus-function issues.
