Why Patterns Over Packages?

We analyzed 23 projects and 50+ candidate utilities — hooks, components, and helpers that appeared repeatedly across codebases.

The conclusion was unambiguous:

None of the identified code is suitable for publication as a standalone package.

Nearly every candidate fell into one of three buckets:

1. Already exists in the open-source ecosystem (often with better implementations)
2. Too trivial to justify a package (< 50 lines of actual logic)
3. Too project-specific (hardcoded routes, locale text, app-specific schemas)

What is worth sharing?

A 20-line dateFormatter wrapper is not worth a package. But a complete auth flow (store + API client + route guards + login form + token refresh) that is copy-paste identical across 6 projects?

That is a pattern worth documenting.

kigu focuses on category 3: repeatable wiring, not individual functions.

The full analysis

The detailed extraction audit (including the full verdict matrix and deep dives on every candidate) is maintained as internal documentation in the repository at /docs/extraction-analysis.md.