frontend-master

To plan frontend architecture for Next.js and Tailwind, use a centralized decision matrix that maps component, animation, asset, and tooling selections to reusable frameworks rather than reinventing setup for each project.

A frontend decision matrix is a unified framework that guides architecture and component selection for UI development, providing a clear entry point and routing tasks to specialized skills for concrete implementation.

Yes, you can use this frontend framework to build a React component library by leveraging its scalable approach to map UI components, animations, and assets to a standardized selection framework.

You route frontend tasks to specialized implementation skills by reviewing the decision matrix, identifying the needed area like components or animations, and directing the task to corresponding skills such as frontend-iconify or frontend-playwright.

The best way to select frontend tooling and assets for a React stack is to consult a centralized decision matrix that documents tooling references and routes asset tasks to specialized sub-skills for execution.

No, you do not need specialized skills to scaffold a Next.js project initially, as this framework provides practical scaffolding guidance, but routing to specialized skills is required for detailed implementation tasks.