frontend-implementation

To establish frontend conventions for a new React or Vue project, this implementation asks targeted questions about rendering needs and complexity, then recommends the top framework options with tradeoffs before applying conventions-first patterns for UI components and routing.

To detect the frontend stack and state management conventions, the implementation automatically inspects your package.json and common config files, confirming the detected frameworks and component libraries before writing any code.

TypeScript is preferred for frontend component implementation and routing changes unless your project is explicitly set up as JavaScript. The process enforces TypeScript usage as an implementation constraint while adhering to existing configurations.

Yes, you can implement UI components across Next.js, SvelteKit, and Nuxt. The process is applicable when working on components, pages, hooks, or routing changes across React, Vue, Svelte, and their respective meta-frameworks.

The best way to coordinate frontend data fetching with design tokens is to flag when ui-design should run, verify the design tokens, and extract data-fetching patterns from the codebase to ensure tooling coordination.

Frontend implementation breaks existing file structure and naming conventions when patterns are not extracted beforehand. This process prevents breaks by extracting export styles and TypeScript preferences from the codebase or falling back to convention defaults.