What problem does it solve? Developers often reimplement cross-cutting infrastructure code — auth, rate limiting, retry logic, caching — that they have already built and cataloged in a previous project. This Skill checks the local .ether/libraries.db catalog before any new implementation begins, so reusable code gets reused instead of rewritten. ## Core Features & Use Cases - Pre-implementation lookup: Runs ether libs find <keywords> against the cataloged library database before writing infrastructure-ish code such as authentication, input validation, secure headers, or middleware. - Reuse-first workflow: When a match exists, it prefers installing the cataloged library via the printed install snippet rather than writing new code, unless the user explicitly wants inline implementation. - Catalog growth: When no match exists, it proceeds with implementation and reminds the user that ether libs register can catalog the new code for future reuse. - Use Case: Before adding JWT auth middleware to a new service, run a keyword search to discover a previously cataloged auth library and add it as a dependency instead of rebuilding it. ## Quick Start Before writing any new rate limiting, auth, validation, or caching code, ask the assistant to check whether a cataloged library already solves it using ether libs find with relevant keywords.
