Code Patent Scanner

## Summary A well-designed, methodical skill for scanning local codebases and surfacing technically distinctive patterns, best suited as a pre-consultation triage and discovery tool rather than any form of IP or legal decision-maker. ### Strengths - **Strong safety posture:** Runs locally, explicitly avoids transmitting code or results, and emphasizes that outputs are technical, not legal, in nature. - **Clear methodology:** Detailed pipeline from file discovery and prioritization through pattern categorization, abstraction, scoring, and advisory signals. - **Good performance strategy:** Quick vs Deep modes and file heuristics (language filters, size bands, directory rules) make it practical for both small and moderately large repos. - **Actionable structure:** Multi-axis scoring and problem–solution–benefit framing help users understand *why* a pattern is distinctive and how it affects the system. ### Key Risks / Limitations - **Potential for misinterpretation as legal guidance:** Despite strong disclaimers and terminology rules, non-expert users may still over-trust scores or claim-like phrasing; it must be framed clearly as technical analysis only. - **Coverage vs depth trade-offs:** Quick Mode analyzes only a subset of files in large repositories, so some distinctive patterns may be missed without user-guided Deep Mode. - **Heuristic dependence:** Distinctiveness judgments rely on heuristic pattern recognition and developer-provided context; sophisticated but conventional code may be underrated, and clever-but-low-impact patterns may be overrated. ### Recommended Scenarios - Early-stage founders or tech leads wanting a structured view of what makes their implementation technically distinctive before talking to an IP professional. - Mature engineering teams periodically reviewing core services to document and track key architectural, algorithmic, or data-structure patterns. - Internal architecture or R&D reviews where stakeholders need concise, evidence-backed descriptions of unique technical approaches within a codebase. Use it as a discovery and prioritization tool, then hand off the most distinctive patterns and their technical context to qualified legal counsel for any IP-related decisions.