frontend-guidelines

Vue 3 projects should use a standardized file structure under src/ with api, stores, types, router, layouts, components, views, and assets directories. This organization keeps domain boundaries clear and ensures maintainability across the frontend blueprint.

Manage shared state in Vue 3 by using Pinia stores to handle data flow separately from UI components. Stores manage shared state, views orchestrate data and user actions, and components remain dumb UI units following strict layered rules.

Avoid direct axios usage in Vue components to maintain strict frontend architecture layering. API calls belong in a dedicated api layer managing HTTP calls, keeping components as dumb UI units and ensuring consistent error handling across the Vue blueprint.

Yes, these Vue frontend guidelines enforce coding standards using script setup with TypeScript. The rules prohibit the Options API, require typed refs, ensure consistent error handling, and mandate that types mirror backend DTOs for strict layering.

No, inline styles are prohibited under these frontend conventions. The tech stack guidance recommends using Tailwind CSS for styling instead, ensuring coherence and clean code across all Vue 3 project components and views.