nerdev-abstraction

Define a Plugin interface with metadata, tools, services, hooks, and a configure method, then register implementations in a central registry. Feature packages export this standard shape and are instantiated through a factory with runtime configuration.

The registry pattern keeps a single Map of all implementations keyed by id, acting as the source of truth for composition. Use it when features must be added or removed without editing existing code, replacing switch statements with polymorphism.

Define domain service interfaces with pure TypeScript signatures and inject Repository and UnitOfWork abstractions instead of using Prisma or framework code directly. Transport layers like HTTP, WebSocket, or CLI only call these services.

Yes, it composes with the nerdev-monorepo skill: packages/core holds interfaces, registry, and factory, while apps consume them via barrel exports. Feature packages depend only on core and shared to avoid circular dependencies.

Extract interfaces from concrete implementations, create a registry and register existing code, then replace direct imports with factory calls. Finally move shared utilities to packages/shared, add a Zod config schema, and introduce an event bus for cross-feature communication.

Avoid it for small single-purpose scripts where indirection adds overhead without benefit. The pattern pays off when multiple pluggable implementations exist or when features must be toggled through configuration rather than code changes.