@gv-tech/design-system 2.5.0 → 2.5.2

package/CHANGELOG.md

@@ -1,5 +1,20 @@
 # Changelog
 
+## [2.5.2](https://github.com/Garcia-Ventures/gvtech-design/compare/design-system-v2.5.1...design-system-v2.5.2) (2026-02-20)
+
+
+### Bug Fixes
+
+* **ci:** migrate npm publish flags to package.json publishConfig and use yarn npm publish. ([df8f11e](https://github.com/Garcia-Ventures/gvtech-design/commit/df8f11e64eb6fb2b56f5f84b095f0332ee087ab9))
+
+## [2.5.1](https://github.com/Garcia-Ventures/gvtech-design/compare/design-system-v2.5.0...design-system-v2.5.1) (2026-02-20)
+
+
+### Bug Fixes
+
+* force release ([b28668d](https://github.com/Garcia-Ventures/gvtech-design/commit/b28668da1f27650c46983f01cd95794361572960))
+* format ([152e9f7](https://github.com/Garcia-Ventures/gvtech-design/commit/152e9f77b236393ce2ac6e33e8c6a61a4af482c2))
+
 ## [2.5.0](https://github.com/Garcia-Ventures/gvtech-design/compare/design-system-v2.4.0...design-system-v2.5.0) (2026-02-20)
 
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@gv-tech/design-system",
-  "version": "2.5.0",
+  "version": "2.5.2",
   "description": "Garcia Ventures react design system",
   "repository": "git@github.com:Garcia-Ventures/gvtech-design.git",
   "license": "MIT",
@@ -29,6 +29,9 @@
   "module": "dist/index.es.js",
   "types": "dist/index.d.ts",
   "style": "dist/design-system.css",
+  "files": [
+    "dist"
+  ],
   "workspaces": [
     "packages/*",
     "apps/*"
@@ -167,4 +170,4 @@
     "access": "public",
     "provenance": true
   }
-}
+}

package/.agent/skills/dogfood-components/SKILL.md

@@ -1,34 +0,0 @@
----
-name: dogfood-components
-description: Guidelines for using library components within the documentation site itself to ensure consistency and showcase real-world usage.
----
-
-# Dogfooding Components Skill
-
-Use this skill whenever you are modifying the documentation site structure, headers, or layout. The goal is to maximize the use of our own UI components within the documentation logic itself (dogfooding).
-
-## Workflow
-
-### 1. Analysis
-
-- **Identify Ad-hoc UI**: Look for custom HTML or static elements in the docs site (`src/App.tsx`, `src/components/docs/CombinedDocsLayout.tsx`, `src/pages/`) that replicate component functionality.
-- **Check Library availability**: Verify if a corresponding component exists in `@gv-tech/ui-web` (e.g., Breadcrumbs, Tabs, Alerts, Badges).
-
-### 2. Implementation
-
-- **Prioritize Library Components**: Replace custom implementations with components from `@gv-tech/ui-web`.
-- **Pass Real State**: Connect these components to the documentation's state (e.g., using `activeItem` with `Breadcrumb` or `Tabs`).
-- **Consistent Styling**: Use the same variants and props that we recommend to our users.
-
-### 3. Validation
-
-- **Functional Check**: Ensure the component behaves correctly within the documentation context (e.g., navigation links work).
-- **Visual Check**: Verify the component renders with the correct theme and layout in the docs.
-
-## Checklist
-
-- [ ] Identified custom UI elements that can be replaced.
-- [ ] Used components from `@gv-tech/ui-web` instead of ad-hoc HTML/CSS.
-- [ ] Component is correctly wired to relevant documentation state.
-- [ ] Verified that navigation and interaction remains functional.
-- [ ] `yarn validate` passes successfully.

package/.agent/skills/maintain-component/SKILL.md

@@ -1,77 +0,0 @@
----
-name: maintain-component
-description: Guidelines for creating or updating UI components, ensuring tests and documentation stay in sync.
----
-
-# Component Maintenance Skill
-
-Use this skill whenever you are tasked with creating a new UI component or modifying an existing one in the `gvtech-design` library. All components must follow the monorepo-based architecture to support Web, React Native, and shared contracts.
-
-## Architecture Standards
-
-Components are split across three primary packages:
-
-1. **`@gv-tech/ui-core`**: Shared contracts/interfaces.
-   - Location: `packages/ui-core/src/contracts/[name].ts`
-   - Role: Defines the "Truth" of what a component's API should be.
-2. **`@gv-tech/ui-web`**: Web (DOM/Radix) implementation.
-   - Location: `packages/ui-web/src/[name].tsx`
-   - Tests: `packages/ui-web/src/[name].test.tsx`
-3. **`@gv-tech/ui-native`**: React Native (NativeWind) implementation.
-   - Location: `packages/ui-native/src/[name].tsx`
-
-## Workflow
-
-### 1. Contract Definition (Core)
-
-- Always start by defining or updating the base props in `packages/ui-core/src/contracts/[name].ts`.
-- Export these props from `packages/ui-core/src/index.ts`.
-- **CRITICAL**: Use specific types. Avoid `any`. Use `unknown` or specific interfaces for extension.
-
-### 2. Platform Implementation
-
-- **Web**:
-  - Build the implementation in `packages/ui-web/src/[name].tsx`.
-  - Import contracts from `@gv-tech/ui-core`.
-  - Import internal utilities (like `cn`) from `./lib/utils` (relative).
-  - Export the component and its types from `packages/ui-web/src/index.ts`.
-- **Native**:
-  - Build the implementation in `packages/ui-native/src/[name].tsx`.
-  - If not yet implemented, provide a "Not implemented" shim.
-  - Import internal utilities from `./lib/utils` (relative).
-  - Export the component from `packages/ui-native/src/index.ts`.
-
-### 3. Documentation & Registry
-
-- **Documentation Implementation**:
-  - Create/Update web-specific docs in `src/pages/web/[ComponentName]Docs.tsx`.
-  - Create/Update native-specific docs in `src/pages/native/[ComponentName]Docs.tsx`.
-  - **Structure**: Documentation files should **not** use `ComponentSection` (this is now handled by the layout). They should return a React Fragment `<>...</>` containing `ComponentShowcase` and implementations.
-  - **Register in App.tsx**:
-    - Add the new route to `src/App.tsx`.
-    - Use `<CombinedDocsLayout />` and pass the `title`, `description`, `web`, and `native` implementations as props.
-  - **Context**: Ensure `PropsTable` matches the `ui-core` contract and covers both platforms if they differ.
-- **Registry**: Run `yarn build:registry` to update the component JSON files in `public/registry`.
-
-### 4. Verification
-
-- **Full Suite**: Run `yarn validate` from the root. This runs:
-  - `sync-tokens`: Ensures design tokens are updated.
-  - `lint`: Checks project-wide ESLint (no `any`, no unused vars).
-  - `tsc`: Verifies TypeScript types across all workspaces.
-  - `test`: Runs Vitest across all packages.
-  - `build`: Verifies Vite/Nx build status.
-
-## Checklist
-
-- [ ] Contract updated in `packages/ui-core/src/contracts/`.
-- [ ] Props exported from `packages/ui-core/src/index.ts`.
-- [ ] Web implementation updated in `packages/ui-web/src/`.
-- [ ] Native implementation/shim updated in `packages/ui-native/src/`.
-- [ ] Exported via `index.ts` in respective packages.
-- [ ] Web docs updated in `src/pages/web/` (without `ComponentSection`).
-- [ ] Native docs updated in `src/pages/native/` (without `ComponentSection`).
-- [ ] Route registered in `src/App.tsx` using `CombinedDocsLayout` with `title` and `description`.
-- [ ] `yarn build:registry` run to update public registry.
-- [ ] `yarn validate` passes successfully (Green state).
-- [ ] **Strict**: No `any` types used in new/modified code.

package/.agent/workflows/native-playground.md

@@ -1,93 +0,0 @@
----
-description: Running the native playground on an Android emulator
----
-
-# Native Playground — Local Development
-
-This workflow starts the Expo dev server for `apps/native-playground` and connects it to a local Android emulator.
-
-## Prerequisites
-
-- Android Studio installed (at `/snap/bin/android-studio`)
-- At least one AVD configured. Available AVDs:
-  - `Pixel_9` (recommended)
-  - `Medium_Phone_API_36.0`
-- Yarn dependencies installed (`yarn install` from repo root)
-
----
-
-## Step 1: Boot the Android Emulator
-
-Open a terminal and start the emulator (leave it running in the background):
-
-```bash
-$ANDROID_HOME/emulator/emulator -avd Pixel_9 &
-```
-
-Wait for the emulator to fully boot to the home screen (~30–60 seconds).
-
-> **Tip:** You can also launch the emulator from Android Studio → Device Manager → ▶ Run.
-
----
-
-## Step 2: Start the Expo Dev Server
-
-// turbo
-From the **monorepo root**, run:
-
-```bash
-yarn native:android
-```
-
-This runs `npx nx run native-playground:start --android`, which:
-
-1. Starts the Metro bundler (NativeWind + Nx monorepo-aware)
-2. Detects the running emulator
-3. Installs Expo Go (or the dev client) on the emulator automatically
-4. Opens the playground app
-
----
-
-## Alternative Commands
-
-| Command                                    | Description                                                        |
-| ------------------------------------------ | ------------------------------------------------------------------ |
-| `yarn native`                              | Start Expo with interactive picker (QR + emulator options)         |
-| `yarn native:android`                      | Start and immediately open on Android emulator                     |
-| `yarn native:clear`                        | Start Android with cleared Metro cache (fixes stale bundle issues) |
-| `npx nx run native-playground:run-android` | Full native build (slower, no Expo Go)                             |
-
----
-
-## Monorepo Hot Reload
-
-Changes to `packages/ui-native` will automatically hot-reload in the emulator because `metro.config.js` uses `withNxMetro`, which watches all monorepo workspace packages.
-
-If hot reload stops working, run `yarn native:clear` to reset the bundler cache.
-
----
-
-## Troubleshooting
-
-**Emulator not detected:**
-
-```bash
-adb devices   # should list the emulator
-adb kill-server && adb start-server  # restart ADB if needed
-```
-
-**Metro can't resolve monorepo packages:**
-
-```bash
-yarn install  # re-link workspace packages
-yarn native:clear  # clear bundler cache
-```
-
-**`ANDROID_HOME` not set:**
-
-```bash
-export ANDROID_HOME=$HOME/Android/Sdk
-export PATH=$PATH:$ANDROID_HOME/emulator:$ANDROID_HOME/platform-tools
-```
-
-Add these to your `~/.zshrc` for persistence.

package/.github/CODEOWNERS

@@ -1,2 +0,0 @@
-.github/CODEOWNERS @eng618
-* @eng618

package/.github/CONTRIBUTING.md

@@ -1,42 +0,0 @@
-# Contributing Guidelines
-
-This project uses **Vite** for development, builds, and as a component playground.
-
-## Available Scripts
-
-In the project directory, you can run:
-
-### `yarn dev`
-
-Runs the Vite development server for local development.
-
-Local: [http://localhost:5173](http://localhost:5173)
-
-Live: [https://gvtech-design.pages.dev/](https://gvtech-design.pages.dev/)
-
-The page will reload if you make edits, and HMR will update components instantly. You will also see any lint errors in the console.
-
-### `yarn test`
-
-Runs the test suite using **Vitest** (configured in `vitest.config.ts`). For interactive watch mode run `yarn test` locally; for CI the project uses `yarn test:ci`.
-
-See the Vitest docs for more information: <https://vitest.dev/guide/>.
-
-### `yarn build`
-
-Builds the library and the component registry using Vite.
-
-### `yarn build:site`
-
-Builds the playground site as a production-ready application.
-
-### Build configuration
-
-This project uses Vite for development and builds. If you need to customize build behavior, edit `vite.config.ts` or add Vite plugins. This project does not use `react-scripts` or `eject`.
-
-## Learn More
-
-- Vite docs: <https://vitejs.dev/> (build, config and plugins)
-- Vitest docs: <https://vitest.dev/> (testing guide)
-
-To customize build behavior, edit `vite.config.ts` or add Vite plugins. For component details and testing examples, check the `src` directory.

package/.github/FUNDING.yml

@@ -1,4 +0,0 @@
-# Funding
-
-github: [eng618]
-custom: ["https://www.paypal.me/garciaericn"]

package/.github/PULL_REQUEST_TEMPLATE/build.md

@@ -1,5 +0,0 @@
-<!-- This PR is used for build and dependency changes -->
-
-# Build updates
-
-<!-- Describe what dependency changes are made, and how you have tested them. -->

package/.github/PULL_REQUEST_TEMPLATE/standard.md

@@ -1,3 +0,0 @@
-# Description
-
-<!-- Describe the contents of this PR in more detail here: -->

package/.github/RELEASING.md

@@ -1,37 +0,0 @@
-# Releasing & Publishing 🔁
-
-This document explains how releases and publishing are handled for this repository and how to test or modify the release flow.
-
-## Release Please (automated Release PRs)
-
-**Overview**
-
-- We use `googleapis/release-please-action` to create Release PRs and tags based on Conventional Commits.
-
-**One-time setup**
-
-1. Create a **Personal Access Token (PAT)** with `repo` (write) permissions and a short expiration.
-2. Add the PAT as a repository secret named `RELEASE_PLEASE_TOKEN` (Repository → Settings → Secrets and variables → Actions → New repository secret).
-3. Confirm branch protection rules allow the PAT or the actor to create tags/releases, or allow the bot account to bypass restrictions where necessary.
-
-**Testing**
-
-- Trigger the action manually: GitHub → Actions → _Release Please_ → _Run workflow_ → choose `main` and run.
-- A Release PR (usually titled `chore(release): release X.Y.Z`) should be created. Review the changelog and changes in the PR.
-- Merge the PR into `main` to create a tag/release. If using a PAT (not `GITHUB_TOKEN`), downstream workflows triggered by `release` events should run normally.
-
-**Notes**
-
-- Make sure your commits follow **Conventional Commits** to get meaningful changelogs and correct SemVer bumps.
-- If release PRs are not being created, confirm that the `RELEASE_PLEASE_TOKEN` is present and has proper repository permissions.
-
-## Publishing to npm (current process)
-
-- The CI publish step currently expects `NPM_TOKEN` as a repository secret (Stored in repository secrets as `NPM_TOKEN`).
-- Publishing is currently automated via GitHub Actions using the `@gv-tech` scope.
-
-## Troubleshooting & Tips
-
-- **Release PR not generated**: Confirm commits use Conventional Commit messages, check action logs, and ensure the PAT is set.
-- **Downstream workflows not running on release**: Ensure releases/tags are created with a PAT (not `GITHUB_TOKEN`), otherwise they won't trigger other workflows.
-- **Scoped package publishing**: If you plan to publish to a scope (e.g., `@gvtech`), update `package.json.name` and set `publishConfig.access` to `public` for public scoped packages.

package/.github/copilot-instructions.md

@@ -1,61 +0,0 @@
-# GVTech Design System - AI Coding Guidelines
-
-## Architecture Overview
-
-This is a React component library built with **TypeScript**, **Tailwind CSS**, and **Radix UI**, using **Vite** for development and bundling. It provides a comprehensive set of accessible UI components based on the shadcn/ui pattern.
-
-**Key Structure:**
-
-- `src/components/ui/` - Core UI components (primitive components)
-- `src/lib/utils.ts` - Shared utilities (e.g., `cn` for Tailwind merging)
-- `src/index.ts` - Library entry point exporting public components
-- `src/App.tsx` - Playground application used for development and documentation
-
-**Build System:**
-
-- Vite library build outputs ES modules and CommonJS.
-- Externalizes **React** and **React DOM**.
-- Use `yarn build` to build both the library and the component registry.
-- Use `yarn build:site` to build the playground/documentation site.
-
-## Component Patterns
-
-**Styling:** Use **Tailwind CSS** utility classes. For complex conditional classes, use the `cn()` utility.
-
-```tsx
-import { cn } from '@/lib/utils';
-
-export function MyComponent({ className, ...props }) {
-  return <div className={cn('bg-background text-foreground p-4', className)} {...props} />;
-}
-```
-
-**Props & Types:**
-
-- Use TypeScript `interface` or `type` for component props.
-- Extend standard HTML attributes where appropriate (e.g., `React.ButtonHTMLAttributes<HTMLButtonElement>`).
-- Use `React.forwardRef` for components that need to expose their underlying DOM element.
-
-## Development Workflow
-
-- **Local dev:** `yarn dev` (runs the Vite playground site)
-- **Build lib:** `yarn build` (outputs to `dist/` and `public/registry/`)
-- **Build site:** `yarn build:site` (outputs to `dist-site/`)
-- **Test:** `yarn test` (Vitest with jsdom)
-- **Lint:** `yarn lint` (ESLint)
-- **Format:** `yarn format` (Prettier)
-
-**Testing Setup:**
-
-- Uses `@testing-library/react` and `@testing-library/jest-dom`.
-- Tests are co-located with components: `{component}.test.tsx`.
-- Run `yarn test:ci` for CI environments.
-
-## Integration Points
-
-- **Vite:** Handles development, site building, and library bundling.
-- **Cloudflare Pages:** Primary deployment target for the playground site: [https://gvtech-design.pages.dev/](https://gvtech-design.pages.dev/) (configured via `wrangler.toml`).
-- **ESLint + Prettier:** Code quality and formatting.
-- **Husky:** Git hooks for pre-commit checks.
-
-Reference existing components in `src/components/ui/` for implementation patterns.

package/.github/workflows/ci.yml

@@ -1,91 +0,0 @@
-name: CI
-
-on: [push, pull_request]
-
-jobs:
-  fossa-scan:
-    runs-on: ubuntu-latest
-    steps:
-      - name: "Checkout Code"
-        uses: actions/checkout@v6
-
-      - name: "Run FOSSA Scan"
-        uses: fossas/fossa-action@main # Use a specific version if locking is preferred
-        with:
-          api-key: ${{ secrets.FOSSA_API_KEY }}
-
-  test:
-    runs-on: ubuntu-latest
-    strategy:
-      matrix:
-        node: ["22", "24"]
-    steps:
-      - uses: actions/checkout@v6
-      - name: Use Node.js ${{ matrix.node }}
-        uses: actions/setup-node@v6
-        with:
-          node-version: ${{ matrix.node }}
-          cache: "yarn"
-
-      - name: Cache Yarn (optional extra)
-        uses: actions/cache@v4
-        with:
-          path: |
-            .yarn/cache
-            .yarn/unplugged
-            .yarn/build-state.yml
-            .yarn/install-state.gz
-          key: ${{ runner.os }}-yarn-${{ hashFiles('**/yarn.lock') }}
-          restore-keys: |
-            ${{ runner.os }}-yarn-
-
-      - name: Install dependencies
-        run: yarn install
-
-      - name: Restore Nx Cache
-        uses: actions/cache@v4
-        with:
-          path: .nx/cache
-          key: ${{ runner.os }}-nx-${{ matrix.node }}-${{ hashFiles('yarn.lock') }}-${{ github.sha }}
-          restore-keys: |
-            ${{ runner.os }}-nx-${{ matrix.node }}-${{ hashFiles('yarn.lock') }}-
-            ${{ runner.os }}-nx-${{ matrix.node }}-
-
-      - name: Format
-        run: yarn format:ci
-
-      - name: Lint
-        run: yarn lint
-
-      - name: Run Tests
-        run: yarn test:ci
-
-  build:
-    runs-on: ubuntu-latest
-    needs: [test]
-    steps:
-      - uses: actions/checkout@v6
-
-      - name: Use Node.js 24
-        uses: actions/setup-node@v6
-        with:
-          node-version: 24
-          cache: "yarn"
-
-      - name: Install dependencies
-        run: yarn install --immutable
-
-      - name: Restore Nx Cache
-        uses: actions/cache@v4
-        with:
-          path: .nx/cache
-          key: ${{ runner.os }}-nx-24-${{ hashFiles('yarn.lock') }}-${{ github.sha }}
-          restore-keys: |
-            ${{ runner.os }}-nx-24-${{ hashFiles('yarn.lock') }}-
-            ${{ runner.os }}-nx-24-
-
-      - name: Build Library
-        run: yarn build
-
-      - name: Build Site
-        run: yarn build:site

package/.github/workflows/codeql-analysis.yml

@@ -1,34 +0,0 @@
-name: "CodeQL"
-
-on:
-  push:
-    branches: [main]
-  pull_request:
-    branches: [main]
-  schedule:
-    - cron: "34 7 * * 4"
-
-jobs:
-  analyze:
-    name: Analyze
-    runs-on: ubuntu-latest
-
-    strategy:
-      fail-fast: false
-      matrix:
-        language: ["javascript"]
-
-    steps:
-      - name: Checkout repository
-        uses: actions/checkout@v4
-
-      - name: Initialize CodeQL
-        uses: github/codeql-action/init@v2
-        with:
-          languages: ${{ matrix.language }}
-
-      - name: Autobuild
-        uses: github/codeql-action/autobuild@v2
-
-      - name: Perform CodeQL Analysis
-        uses: github/codeql-action/analyze@v2

package/.github/workflows/release-please.yml

@@ -1,79 +0,0 @@
-name: Release Please
-
-on:
-  push:
-    branches: [main]
-  workflow_dispatch:
-
-permissions:
-  id-token: write # For OIDC trusted publishing
-  contents: write # For tags and releases
-  pull-requests: write # For creating release PRs
-
-jobs:
-  release:
-    runs-on: ubuntu-latest
-    steps:
-      - name: Checkout
-        uses: actions/checkout@v6
-
-      - name: Run release-please
-        id: release
-        uses: googleapis/release-please-action@v4.4
-        with:
-          manifest-file: .release-please-manifest.json
-          config-file: release-please-config.json
-          token: ${{ secrets.RELEASE_PLEASE_TOKEN }}
-
-      - name: Show notice
-        run: echo "If a release PR is created, review and merge it to create a tag/release."
-
-      - name: Checkout Code
-        if: ${{ steps.release.outputs.releases_created }}
-        uses: actions/checkout@v6
-
-      - name: Use Node.js 24
-        if: ${{ steps.release.outputs.releases_created }}
-        uses: actions/setup-node@v6
-        with:
-          node-version: 24
-          registry-url: "https://registry.npmjs.org"
-          cache: "yarn"
-
-      - name: Install dependencies
-        if: ${{ steps.release.outputs.releases_created }}
-        run: yarn install --immutable
-
-      - name: Build
-        if: ${{ steps.release.outputs.releases_created }}
-        run: yarn build
-
-      - name: Publish to npm
-        if: ${{ steps.release.outputs.releases_created }}
-        env:
-          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
-        run: |
-          # Iterate over each released package path
-          echo '${{ steps.release.outputs.paths_released }}' | jq -r '.[]' | while read -r path; do
-            echo "--- Publishing package at: $path ---"
-            cd "$path"
-            
-            # Skip if the package is private
-            if jq -e '.private == true' package.json > /dev/null; then
-              echo "Skipping private package: $(jq -r '.name' package.json)"
-              cd - > /dev/null
-              continue
-            fi
-            
-            # Build the package if a build script exists
-            if jq -e '.scripts.build' package.json > /dev/null; then
-              echo "Building $(jq -r '.name' package.json)..."
-              yarn build
-            fi
-            
-            # Publish to npm
-            echo "Publishing $(jq -r '.name' package.json)..."
-            npm publish --provenance --access public
-            
-            cd - > /dev/null
-          done

package/.husky/pre-commit

@@ -1 +0,0 @@
-npx lint-staged

package/.prettierignore

@@ -1,3 +0,0 @@
-CHANGELOG.md
-.yarn
-dist-site

package/.release-please-manifest.json

@@ -1,9 +0,0 @@
-{
-  ".": "2.5.0",
-  "packages/ui-web": "0.1.0",
-  "packages/ui-native": "0.1.0",
-  "packages/ui-core": "0.1.0",
-  "packages/design-tokens": "0.1.0",
-  "apps/playground-web": "0.1.0",
-  "apps/native-playground": "0.1.0"
-}

package/.tool-versions

@@ -1 +0,0 @@
-nodejs 24.13.1

package/.vscode/launch.json

@@ -1,22 +0,0 @@
-{
-  // Use IntelliSense to learn about possible attributes.
-  // Hover to view descriptions of existing attributes.
-  // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
-  "version": "0.2.0",
-  "configurations": [
-    {
-      "type": "chrome",
-      "request": "launch",
-      "name": "React app",
-      "url": "http://localhost:3000",
-      "webRoot": "${workspaceFolder}"
-    },
-    {
-      "type": "chrome",
-      "request": "launch",
-      "name": "Storybook",
-      "url": "http://localhost:6006",
-      "webRoot": "${workspaceFolder}"
-    }
-  ]
-}

package/.vscode/mcp.json

@@ -1,8 +0,0 @@
-{
-  "servers": {
-    "shadcn": {
-      "command": "npx",
-      "args": ["shadcn@latest", "mcp"]
-    }
-  }
-}