What problem does it solve? Frontend projects repeatedly rebuild the same HTTP plumbing: configuring base URLs, attaching Authorization Bearer tokens, and converting Axios or $fetch errors into a predictable app error shape. This Skill scaffolds that shared API transport layer once, correctly placed for the project's architecture, so feature code only writes thin business wrappers. ## Core Features & Use Cases - Framework-aware client generation: Uses Axios for Vite-based React and Vue SPAs, and Nuxt's built-in $fetch for Nuxt projects, detected automatically. - Complete transport layer: Generates client, token provider, error normalization, dynamic HTTP methods (api.get/post/put/patch/delete), exported helper functions (getApi, postApi), types, and index exports. - Architecture-aware placement: Detects shared/features layouts, Nuxt app/ directories, and plain SPA conventions to place files in the right folder, and preserves existing custom transport clients. - Use Case: In a React + Vite project, run the bootstrap to get src/shared/api with a token-aware Axios client, then call getApi<User[]>('/users', { page: 1 }) from a feature hook without touching transport code. ## Quick Start Ask the AI to set up the API client with base URL, Bearer token handling, and normalized errors for your Vite or Nuxt frontend project.