erne-feature

To isolate a single reusable component or hook, you can scaffold a focused feature unit that enforces clear boundaries, explicit typing, and dependency verification, enabling parallel work alongside other agents.

Building an API wrapper with strong typing requires explicit return types and parameter interfaces with no any, plus handling for loading, error, empty, and success states to ensure safe, predictable delivery.

A scoped feature unit is a single deliverable such as a screen, hook, or reusable component with clear boundaries and integration-point documentation, needed when isolating work within a larger project for parallel development.

Yes, the feature-builder approach requires explicit typing, enforcing explicit return types and parameter interfaces with no any, ensuring safe and predictable delivery of the focused feature unit.

Yes, you can parallelize work on multiple screens or components simultaneously, as the feature-builder agent is designed to work alongside other agents on larger features with clear boundaries.

The best way to document integration points for a focused feature unit is to deliver explicit integration-point documentation as part of the scoped output, ensuring clear boundaries for parallel work.