framework-adapter

To generate a Next.js App Router folder structure using FSD architecture, this skill maps FSD blueprint layers like pages, layouts, and shared segments under the src/ directory while enforcing framework-specific routing conventions. It outputs a ready-to-apply directory tree with re-export-only routing wrappers.

Adapting FSD layers to SvelteKit or Nuxt routing rules involves integrating the final FSD blueprint with the project's specific routing patterns to produce a concrete directory structure. This skill maps shared layers and pages to the chosen framework, placing FSD layers under src/ and marking optional segments as placeholders.

You need to complete structure planning before generating a framework-specific directory tree because this skill operates after the fsd-workshop structure-planner step. It requires the final fsd-blueprint.md as input to map pages, layouts, and shared layers to the chosen framework's routing conventions.

You can use FSD architecture with Angular or React and Vite folder structures. This skill supports mapping the final FSD blueprint to these frameworks, placing FSD layers under src/ and generating a ready-to-apply directory structure that respects their specific routing rules.

Routing wrapper enforcement when mapping FSD blueprints to web frameworks requires re-export-only routing wrappers to maintain clean separation between FSD layers and framework routing. This ensures the generated directory structure respects both FSD architecture principles and the chosen framework's routing conventions.