What problem does it solve? Building a consistent Vue 3 / Nuxt 4 frontend for a financial data portal requires enforcing many project-specific rules: Spanish-only UI strings, Lazy-prefixed heavy components, design tokens derived from a LaTeX style file, and skeleton/empty/error states without layout shift. This Skill encodes all of those conventions so generated components comply on the first pass. ## Core Features & Use Cases - Component scaffolding by domain: Pages, chat tool-call cards, dashboard insight cards, admin user management, and common skeleton/empty states, all following the Nuxt 4 app/ directory structure with typed <script setup lang="ts">. - Design token enforcement: Tailwind v4 @theme tokens generated from uxdoc.sty, prohibiting hand-written colors and ensuring UI matches course documents. - State handling patterns: Four-state ToolCallCard (announced/running/done/error), skeleton blocks with reserved dimensions to prevent layout shift, and SSR-safe client-only code. - Use Case: Ask the assistant to build the /admin/usuarios panel and receive a UserTable with soft-delete confirmation, a UserFormModal handling 409 duplicate errors, and admin-role middleware, all in Spanish with correct tokens. ## Quick Start Create the ToolCallCard component for the chat panel with its four states using the portal frontend conventions.