library-deep-dive
Library Deep Dive
Determines whether a project uses a single specific library to its full potential. The output is a deep, evidence-backed research report — not a surface scan — delivered as a self-contained, beautifully designed HTML file.
Why This Matters
Most projects adopt a library for one or two features and never explore the rest. A team pulls in zod for simple validation and misses schema composition, discriminated unions, and branded types. They add gorm for basic CRUD and miss hooks, custom datatypes, batch operations, and the session API. Every library ships a far larger feature surface than anyone discovers by accident.
Underutilization has real costs: hand-rolled code that duplicates built-in functionality, worse performance because the library's optimized path was never used, and a stale version because nobody knows what newer features would unlock. This skill closes that gap by systematically comparing what the project does with everything the library offers.
The deliverable is a point-in-time research report — a snapshot read by humans, never edited again — so it gets the full HTML treatment, not Markdown.
Inputs
The user names a library (e.g. "deep dive into Zod", "are we using GORM to the max"). From that:
- Identify the library in the project's dependency files (
package.json,go.mod,requirements.txt,Cargo.toml,Gemfile,pom.xml,build.gradle, etc.). - Capture the exact version installed — version currency is part of the assessment.
- If the library is not found in any dependency file, stop and report that to the user with the files checked.