subagent-pattern-collect

To collect architecture patterns before refactoring frontend routes, systematically identify the current project structure and extract pattern contracts with explicit file references and ownership boundaries.

The best way to extract data-contract patterns for backend modules is to apply a repeatable collection workflow that surfaces existing conventions and validation points before feature implementation.

To prevent code duplication when adding new domain modules, run a pattern collection workflow to govern changes and ensure new modules align with existing architecture.

Yes, the pattern collection workflow works across the full stack, applying to frontend routes, backend modules, and data-contract evolution to reduce misalignment between teams.

You need to run an architecture pattern collection workflow before adding a new route or domain module, ensuring planned changes align with existing validation points and ownership boundaries.

Manually identifying project structure for code review lacks a repeatable exploration flow, increasing the risk of misalignment and missing explicit file references across evolving data contracts.