{"owner":"NangoHQ","repo":"nango","hasSkills":true,"totalSkillsCount":5,"totalTokensCount":2198,"categories":["root-instruction","claude-rule","mcp-config","marketplace","plugin-manifest"],"hasMcp":true,"mcpConfig":{"mcpServers":{"nango":{"command":"npx","args":["-y","@modelcontextprotocol/server-nango"]}}},"found":["AGENTS.md","CLAUDE.md",".cursor/mcp.json",".claude-plugin/marketplace.json",".claude-plugin/plugin.json"],"skills":{"AGENTS.md":"Use `npm` as the project package manager.\nAfter running the initial `npm install` or `npm ci`, run `npm run prepare` to install Husky git hooks.\n\n## Linting & formatting\n\nLinting uses **oxlint** — `npm run lint` (and `npm run lint:fix`), configured in `.oxlintrc.json`. Type-aware rules run via `oxlint-tsgolint`, which resolves types from source, so no `ts-build`/`dist` is needed first. Formatting is **Prettier** — `npm run format` (CI checks it via `npm run format:check`).\n\nFor inline editor diagnostics, install the oxlint extension: VS Code / Cursor → `oxc.oxc-vscode`; JetBrains → the `oxc` plugin; Neovim/Emacs/Helix/Sublime → any LSP client via `oxlint --lsp`. The ESLint extension will no longer show diagnostics.\n\n## Product analytics\n\nEvery analytics event the webapp, server or CLI sends is defined in `packages/types/lib/analytics/catalogue.ts`. To add, rename or remove one, use the `managing-analytics-events` skill.\n\n## Running Nango locally\n\nFor full local dev setup (Docker, service URLs, auth flows, troubleshooting), use the `running-and-testing-locally` skill.\n\n## Running the webapp dev server\n\n### Multiple worktrees (local backend)\n\nRun `npm run dev -w packages/webapp` from each worktree. Vite picks the next free port (3000 → 3001 → 3002 …) and each dashboard calls the local backend at `localhost:3003` directly — the API's dev CORS trusts any `localhost` port, so no proxy or `apiUrl` rewrite is needed. Only `/env.js` is proxied so `window._env` loads same-origin.\n\n### Remote API\n\nPass `REMOTE_API=<env>` to proxy all API traffic to a live backend instead. No local backend needed.\n\n```bash\nREMOTE_API=dev npm run dev -w packages/webapp       # https://api-development.nango.dev\nREMOTE_API=staging npm run dev -w packages/webapp   # https://api-staging.nango.dev\nREMOTE_API=prod npm run dev -w packages/webapp      # https://api.nango.dev\n```\n\n## Design system\n\n`@nangohq/design-system` components (`Button`, `IconButton`, …) own their styling. In any package that consumes the design system (webapp, …), **don't override it with `className` or `style`** — a lint rule (`react/forbid-component-props`) flags these props where the design system is used. Instead:\n\n- Use the component's `variant`/`size` and other props.\n- Put layout (margin, positioning, width) on a **wrapper element**, not the component.\n- Need a look no prop covers? Add a variant to the design system — see `packages/design-system/AGENTS.md`.\n\nFull guidance: `packages/design-system/stories/StylingAndCustomization.mdx`\n","CLAUDE.md":"Use `npm` as the project package manager.\nAfter running the initial `npm install` or `npm ci`, run `npm run prepare` to install Husky git hooks.\n\n## Linting & formatting\n\nLinting uses **oxlint** — `npm run lint` (and `npm run lint:fix`), configured in `.oxlintrc.json`. Type-aware rules run via `oxlint-tsgolint`, which resolves types from source, so no `ts-build`/`dist` is needed first. Formatting is **Prettier** — `npm run format` (CI checks it via `npm run format:check`).\n\nFor inline editor diagnostics, install the oxlint extension: VS Code / Cursor → `oxc.oxc-vscode`; JetBrains → the `oxc` plugin; Neovim/Emacs/Helix/Sublime → any LSP client via `oxlint --lsp`. The ESLint extension will no longer show diagnostics.\n\n## Product analytics\n\nEvery analytics event the webapp, server or CLI sends is defined in `packages/types/lib/analytics/catalogue.ts`. To add, rename or remove one, use the `managing-analytics-events` skill.\n\n## Running Nango locally\n\nFor full local dev setup (Docker, service URLs, auth flows, troubleshooting), use the `running-and-testing-locally` skill.\n\n## Running the webapp dev server\n\n### Multiple worktrees (local backend)\n\nRun `npm run dev -w packages/webapp` from each worktree. Vite picks the next free port (3000 → 3001 → 3002 …) and each dashboard calls the local backend at `localhost:3003` directly — the API's dev CORS trusts any `localhost` port, so no proxy or `apiUrl` rewrite is needed. Only `/env.js` is proxied so `window._env` loads same-origin.\n\n### Remote API\n\nPass `REMOTE_API=<env>` to proxy all API traffic to a live backend instead. No local backend needed.\n\n```bash\nREMOTE_API=dev npm run dev -w packages/webapp       # https://api-development.nango.dev\nREMOTE_API=staging npm run dev -w packages/webapp   # https://api-staging.nango.dev\nREMOTE_API=prod npm run dev -w packages/webapp      # https://api.nango.dev\n```\n\n## Design system\n\n`@nangohq/design-system` components (`Button`, `IconButton`, …) own their styling. In any package that consumes the design system (webapp, …), **don't override it with `className` or `style`** — a lint rule (`react/forbid-component-props`) flags these props where the design system is used. Instead:\n\n- Use the component's `variant`/`size` and other props.\n- Put layout (margin, positioning, width) on a **wrapper element**, not the component.\n- Need a look no prop covers? Add a variant to the design system — see `packages/design-system/AGENTS.md`.\n\nFull guidance: `packages/design-system/stories/StylingAndCustomization.mdx`\n",".cursor/mcp.json":"# Model Context Protocol (MCP) Configuration\n\nPath: `.cursor/mcp.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/NangoHQ/nango/HEAD/.cursor/mcp.json)",".claude-plugin/marketplace.json":"# Claude Plugin Marketplace Catalog\n\nPath: `.claude-plugin/marketplace.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/NangoHQ/nango/HEAD/.claude-plugin/marketplace.json)",".claude-plugin/plugin.json":"# claude-plugin Plugin Manifest\n\nPath: `.claude-plugin/plugin.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/NangoHQ/nango/HEAD/.claude-plugin/plugin.json)"},"files":{"AGENTS.md":"Use `npm` as the project package manager.\nAfter running the initial `npm install` or `npm ci`, run `npm run prepare` to install Husky git hooks.\n\n## Linting & formatting\n\nLinting uses **oxlint** — `npm run lint` (and `npm run lint:fix`), configured in `.oxlintrc.json`. Type-aware rules run via `oxlint-tsgolint`, which resolves types from source, so no `ts-build`/`dist` is needed first. Formatting is **Prettier** — `npm run format` (CI checks it via `npm run format:check`).\n\nFor inline editor diagnostics, install the oxlint extension: VS Code / Cursor → `oxc.oxc-vscode`; JetBrains → the `oxc` plugin; Neovim/Emacs/Helix/Sublime → any LSP client via `oxlint --lsp`. The ESLint extension will no longer show diagnostics.\n\n## Product analytics\n\nEvery analytics event the webapp, server or CLI sends is defined in `packages/types/lib/analytics/catalogue.ts`. To add, rename or remove one, use the `managing-analytics-events` skill.\n\n## Running Nango locally\n\nFor full local dev setup (Docker, service URLs, auth flows, troubleshooting), use the `running-and-testing-locally` skill.\n\n## Running the webapp dev server\n\n### Multiple worktrees (local backend)\n\nRun `npm run dev -w packages/webapp` from each worktree. Vite picks the next free port (3000 → 3001 → 3002 …) and each dashboard calls the local backend at `localhost:3003` directly — the API's dev CORS trusts any `localhost` port, so no proxy or `apiUrl` rewrite is needed. Only `/env.js` is proxied so `window._env` loads same-origin.\n\n### Remote API\n\nPass `REMOTE_API=<env>` to proxy all API traffic to a live backend instead. No local backend needed.\n\n```bash\nREMOTE_API=dev npm run dev -w packages/webapp       # https://api-development.nango.dev\nREMOTE_API=staging npm run dev -w packages/webapp   # https://api-staging.nango.dev\nREMOTE_API=prod npm run dev -w packages/webapp      # https://api.nango.dev\n```\n\n## Design system\n\n`@nangohq/design-system` components (`Button`, `IconButton`, …) own their styling. In any package that consumes the design system (webapp, …), **don't override it with `className` or `style`** — a lint rule (`react/forbid-component-props`) flags these props where the design system is used. Instead:\n\n- Use the component's `variant`/`size` and other props.\n- Put layout (margin, positioning, width) on a **wrapper element**, not the component.\n- Need a look no prop covers? Add a variant to the design system — see `packages/design-system/AGENTS.md`.\n\nFull guidance: `packages/design-system/stories/StylingAndCustomization.mdx`\n","CLAUDE.md":"Use `npm` as the project package manager.\nAfter running the initial `npm install` or `npm ci`, run `npm run prepare` to install Husky git hooks.\n\n## Linting & formatting\n\nLinting uses **oxlint** — `npm run lint` (and `npm run lint:fix`), configured in `.oxlintrc.json`. Type-aware rules run via `oxlint-tsgolint`, which resolves types from source, so no `ts-build`/`dist` is needed first. Formatting is **Prettier** — `npm run format` (CI checks it via `npm run format:check`).\n\nFor inline editor diagnostics, install the oxlint extension: VS Code / Cursor → `oxc.oxc-vscode`; JetBrains → the `oxc` plugin; Neovim/Emacs/Helix/Sublime → any LSP client via `oxlint --lsp`. The ESLint extension will no longer show diagnostics.\n\n## Product analytics\n\nEvery analytics event the webapp, server or CLI sends is defined in `packages/types/lib/analytics/catalogue.ts`. To add, rename or remove one, use the `managing-analytics-events` skill.\n\n## Running Nango locally\n\nFor full local dev setup (Docker, service URLs, auth flows, troubleshooting), use the `running-and-testing-locally` skill.\n\n## Running the webapp dev server\n\n### Multiple worktrees (local backend)\n\nRun `npm run dev -w packages/webapp` from each worktree. Vite picks the next free port (3000 → 3001 → 3002 …) and each dashboard calls the local backend at `localhost:3003` directly — the API's dev CORS trusts any `localhost` port, so no proxy or `apiUrl` rewrite is needed. Only `/env.js` is proxied so `window._env` loads same-origin.\n\n### Remote API\n\nPass `REMOTE_API=<env>` to proxy all API traffic to a live backend instead. No local backend needed.\n\n```bash\nREMOTE_API=dev npm run dev -w packages/webapp       # https://api-development.nango.dev\nREMOTE_API=staging npm run dev -w packages/webapp   # https://api-staging.nango.dev\nREMOTE_API=prod npm run dev -w packages/webapp      # https://api.nango.dev\n```\n\n## Design system\n\n`@nangohq/design-system` components (`Button`, `IconButton`, …) own their styling. In any package that consumes the design system (webapp, …), **don't override it with `className` or `style`** — a lint rule (`react/forbid-component-props`) flags these props where the design system is used. Instead:\n\n- Use the component's `variant`/`size` and other props.\n- Put layout (margin, positioning, width) on a **wrapper element**, not the component.\n- Need a look no prop covers? Add a variant to the design system — see `packages/design-system/AGENTS.md`.\n\nFull guidance: `packages/design-system/stories/StylingAndCustomization.mdx`\n",".cursor/mcp.json":"# Model Context Protocol (MCP) Configuration\n\nPath: `.cursor/mcp.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/NangoHQ/nango/HEAD/.cursor/mcp.json)",".claude-plugin/marketplace.json":"# Claude Plugin Marketplace Catalog\n\nPath: `.claude-plugin/marketplace.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/NangoHQ/nango/HEAD/.claude-plugin/marketplace.json)",".claude-plugin/plugin.json":"# claude-plugin Plugin Manifest\n\nPath: `.claude-plugin/plugin.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/NangoHQ/nango/HEAD/.claude-plugin/plugin.json)"},"items":[{"name":"AGENTS.md","path":"AGENTS.md","rawUrl":"https://raw.githubusercontent.com/NangoHQ/nango/HEAD/AGENTS.md","title":"AI Agent Protocol & Instructions","category":"root-instruction","format":"markdown","content":"Use `npm` as the project package manager.\nAfter running the initial `npm install` or `npm ci`, run `npm run prepare` to install Husky git hooks.\n\n## Linting & formatting\n\nLinting uses **oxlint** — `npm run lint` (and `npm run lint:fix`), configured in `.oxlintrc.json`. Type-aware rules run via `oxlint-tsgolint`, which resolves types from source, so no `ts-build`/`dist` is needed first. Formatting is **Prettier** — `npm run format` (CI checks it via `npm run format:check`).\n\nFor inline editor diagnostics, install the oxlint extension: VS Code / Cursor → `oxc.oxc-vscode`; JetBrains → the `oxc` plugin; Neovim/Emacs/Helix/Sublime → any LSP client via `oxlint --lsp`. The ESLint extension will no longer show diagnostics.\n\n## Product analytics\n\nEvery analytics event the webapp, server or CLI sends is defined in `packages/types/lib/analytics/catalogue.ts`. To add, rename or remove one, use the `managing-analytics-events` skill.\n\n## Running Nango locally\n\nFor full local dev setup (Docker, service URLs, auth flows, troubleshooting), use the `running-and-testing-locally` skill.\n\n## Running the webapp dev server\n\n### Multiple worktrees (local backend)\n\nRun `npm run dev -w packages/webapp` from each worktree. Vite picks the next free port (3000 → 3001 → 3002 …) and each dashboard calls the local backend at `localhost:3003` directly — the API's dev CORS trusts any `localhost` port, so no proxy or `apiUrl` rewrite is needed. Only `/env.js` is proxied so `window._env` loads same-origin.\n\n### Remote API\n\nPass `REMOTE_API=<env>` to proxy all API traffic to a live backend instead. No local backend needed.\n\n```bash\nREMOTE_API=dev npm run dev -w packages/webapp       # https://api-development.nango.dev\nREMOTE_API=staging npm run dev -w packages/webapp   # https://api-staging.nango.dev\nREMOTE_API=prod npm run dev -w packages/webapp      # https://api.nango.dev\n```\n\n## Design system\n\n`@nangohq/design-system` components (`Button`, `IconButton`, …) own their styling. In any package that consumes the design system (webapp, …), **don't override it with `className` or `style`** — a lint rule (`react/forbid-component-props`) flags these props where the design system is used. Instead:\n\n- Use the component's `variant`/`size` and other props.\n- Put layout (margin, positioning, width) on a **wrapper element**, not the component.\n- Need a look no prop covers? Add a variant to the design system — see `packages/design-system/AGENTS.md`.\n\nFull guidance: `packages/design-system/stories/StylingAndCustomization.mdx`\n","isInternal":false,"tokens":649,"sizeBytes":2548},{"name":"CLAUDE.md","path":"CLAUDE.md","rawUrl":"https://raw.githubusercontent.com/NangoHQ/nango/HEAD/CLAUDE.md","title":"Claude Agent Guidelines & System Prompt","category":"claude-rule","format":"markdown","content":"Use `npm` as the project package manager.\nAfter running the initial `npm install` or `npm ci`, run `npm run prepare` to install Husky git hooks.\n\n## Linting & formatting\n\nLinting uses **oxlint** — `npm run lint` (and `npm run lint:fix`), configured in `.oxlintrc.json`. Type-aware rules run via `oxlint-tsgolint`, which resolves types from source, so no `ts-build`/`dist` is needed first. Formatting is **Prettier** — `npm run format` (CI checks it via `npm run format:check`).\n\nFor inline editor diagnostics, install the oxlint extension: VS Code / Cursor → `oxc.oxc-vscode`; JetBrains → the `oxc` plugin; Neovim/Emacs/Helix/Sublime → any LSP client via `oxlint --lsp`. The ESLint extension will no longer show diagnostics.\n\n## Product analytics\n\nEvery analytics event the webapp, server or CLI sends is defined in `packages/types/lib/analytics/catalogue.ts`. To add, rename or remove one, use the `managing-analytics-events` skill.\n\n## Running Nango locally\n\nFor full local dev setup (Docker, service URLs, auth flows, troubleshooting), use the `running-and-testing-locally` skill.\n\n## Running the webapp dev server\n\n### Multiple worktrees (local backend)\n\nRun `npm run dev -w packages/webapp` from each worktree. Vite picks the next free port (3000 → 3001 → 3002 …) and each dashboard calls the local backend at `localhost:3003` directly — the API's dev CORS trusts any `localhost` port, so no proxy or `apiUrl` rewrite is needed. Only `/env.js` is proxied so `window._env` loads same-origin.\n\n### Remote API\n\nPass `REMOTE_API=<env>` to proxy all API traffic to a live backend instead. No local backend needed.\n\n```bash\nREMOTE_API=dev npm run dev -w packages/webapp       # https://api-development.nango.dev\nREMOTE_API=staging npm run dev -w packages/webapp   # https://api-staging.nango.dev\nREMOTE_API=prod npm run dev -w packages/webapp      # https://api.nango.dev\n```\n\n## Design system\n\n`@nangohq/design-system` components (`Button`, `IconButton`, …) own their styling. In any package that consumes the design system (webapp, …), **don't override it with `className` or `style`** — a lint rule (`react/forbid-component-props`) flags these props where the design system is used. Instead:\n\n- Use the component's `variant`/`size` and other props.\n- Put layout (margin, positioning, width) on a **wrapper element**, not the component.\n- Need a look no prop covers? Add a variant to the design system — see `packages/design-system/AGENTS.md`.\n\nFull guidance: `packages/design-system/stories/StylingAndCustomization.mdx`\n","isInternal":false,"tokens":649,"sizeBytes":2548},{"name":"marketplace.json","path":".claude-plugin/marketplace.json","rawUrl":"https://raw.githubusercontent.com/NangoHQ/nango/HEAD/.claude-plugin/marketplace.json","title":"Claude Plugin Marketplace Catalog","category":"marketplace","format":"json","content":"# Claude Plugin Marketplace Catalog\n\nPath: `.claude-plugin/marketplace.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/NangoHQ/nango/HEAD/.claude-plugin/marketplace.json)","tokens":300,"sizeBytes":192},{"name":"plugin.json","path":".claude-plugin/plugin.json","rawUrl":"https://raw.githubusercontent.com/NangoHQ/nango/HEAD/.claude-plugin/plugin.json","title":"claude-plugin Plugin Manifest","category":"plugin-manifest","format":"json","content":"# claude-plugin Plugin Manifest\n\nPath: `.claude-plugin/plugin.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/NangoHQ/nango/HEAD/.claude-plugin/plugin.json)","tokens":300,"sizeBytes":178},{"name":"mcp.json","path":".cursor/mcp.json","rawUrl":"https://raw.githubusercontent.com/NangoHQ/nango/HEAD/.cursor/mcp.json","title":"Model Context Protocol (MCP) Configuration","category":"mcp-config","format":"json","content":"# Model Context Protocol (MCP) Configuration\n\nPath: `.cursor/mcp.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/NangoHQ/nango/HEAD/.cursor/mcp.json)","tokens":300,"sizeBytes":171}],"systemPromptSnippet":"<yakaai_skills repo=\"NangoHQ/nango\">\n<!-- File: AGENTS.md (Tokens: ~649 | Category: root-instruction) -->\nUse `npm` as the project package manager.\nAfter running the initial `npm install` or `npm ci`, run `npm run prepare` to install Husky git hooks.\n\n## Linting & formatting\n\nLinting uses **oxlint** — `npm run lint` (and `npm run lint:fix`), configured in `.oxlintrc.json`. Type-aware rules run via `oxlint-tsgolint`, which resolves types from source, so no `ts-build`/`dist` is needed first. Formatting is **Prettier** — `npm run format` (CI checks it via `npm run format:check`).\n\nFor inline editor diagnostics, install the oxlint extension: VS Code / Cursor → `oxc.oxc-vscode`; JetBrains → the `oxc` plugin; Neovim/Emacs/Helix/Sublime → any LSP client via `oxlint --lsp`. The ESLint extension will no longer show diagnostics.\n\n## Product analytics\n\nEvery analytics event the webapp, server or CLI sends is defined in `packages/types/lib/analytics/catalogue.ts`. To add, rename or remove one, use the `managing-analytics-events` skill.\n\n## Running Nango locally\n\nFor full local dev setup (Docker, service URLs, auth flows, troubleshooting), use the `running-and-testing-locally` skill.\n\n## Running the webapp dev server\n\n### Multiple worktrees (local backend)\n\nRun `npm run dev -w packages/webapp` from each worktree. Vite picks the next free port (3000 → 3001 → 3002 …) and each dashboard calls the local backend at `localhost:3003` directly — the API's dev CORS trusts any `localhost` port, so no proxy or `apiUrl` rewrite is needed. Only `/env.js` is proxied so `window._env` loads same-origin.\n\n### Remote API\n\nPass `REMOTE_API=<env>` to proxy all API traffic to a live backend instead. No local backend needed.\n\n```bash\nREMOTE_API=dev npm run dev -w packages/webapp       # https://api-development.nango.dev\nREMOTE_API=staging npm run dev -w packages/webapp   # https://api-staging.nango.dev\nREMOTE_API=prod npm run dev -w packages/webapp      # https://api.nango.dev\n```\n\n## Design system\n\n`@nangohq/design-system` components (`Button`, `IconButton`, …) own their styling. In any package that consumes the design system (webapp, …), **don't override it with `className` or `style`** — a lint rule (`react/forbid-component-props`) flags these props where the design system is used. Instead:\n\n- Use the component's `variant`/`size` and other props.\n- Put layout (margin, positioning, width) on a **wrapper element**, not the component.\n- Need a look no prop covers? Add a variant to the design system — see `packages/design-system/AGENTS.md`.\n\nFull guidance: `packages/design-system/stories/StylingAndCustomization.mdx`\n\n<!-- File: CLAUDE.md (Tokens: ~649 | Category: claude-rule) -->\nUse `npm` as the project package manager.\nAfter running the initial `npm install` or `npm ci`, run `npm run prepare` to install Husky git hooks.\n\n## Linting & formatting\n\nLinting uses **oxlint** — `npm run lint` (and `npm run lint:fix`), configured in `.oxlintrc.json`. Type-aware rules run via `oxlint-tsgolint`, which resolves types from source, so no `ts-build`/`dist` is needed first. Formatting is **Prettier** — `npm run format` (CI checks it via `npm run format:check`).\n\nFor inline editor diagnostics, install the oxlint extension: VS Code / Cursor → `oxc.oxc-vscode`; JetBrains → the `oxc` plugin; Neovim/Emacs/Helix/Sublime → any LSP client via `oxlint --lsp`. The ESLint extension will no longer show diagnostics.\n\n## Product analytics\n\nEvery analytics event the webapp, server or CLI sends is defined in `packages/types/lib/analytics/catalogue.ts`. To add, rename or remove one, use the `managing-analytics-events` skill.\n\n## Running Nango locally\n\nFor full local dev setup (Docker, service URLs, auth flows, troubleshooting), use the `running-and-testing-locally` skill.\n\n## Running the webapp dev server\n\n### Multiple worktrees (local backend)\n\nRun `npm run dev -w packages/webapp` from each worktree. Vite picks the next free port (3000 → 3001 → 3002 …) and each dashboard calls the local backend at `localhost:3003` directly — the API's dev CORS trusts any `localhost` port, so no proxy or `apiUrl` rewrite is needed. Only `/env.js` is proxied so `window._env` loads same-origin.\n\n### Remote API\n\nPass `REMOTE_API=<env>` to proxy all API traffic to a live backend instead. No local backend needed.\n\n```bash\nREMOTE_API=dev npm run dev -w packages/webapp       # https://api-development.nango.dev\nREMOTE_API=staging npm run dev -w packages/webapp   # https://api-staging.nango.dev\nREMOTE_API=prod npm run dev -w packages/webapp      # https://api.nango.dev\n```\n\n## Design system\n\n`@nangohq/design-system` components (`Button`, `IconButton`, …) own their styling. In any package that consumes the design system (webapp, …), **don't override it with `className` or `style`** — a lint rule (`react/forbid-component-props`) flags these props where the design system is used. Instead:\n\n- Use the component's `variant`/`size` and other props.\n- Put layout (margin, positioning, width) on a **wrapper element**, not the component.\n- Need a look no prop covers? Add a variant to the design system — see `packages/design-system/AGENTS.md`.\n\nFull guidance: `packages/design-system/stories/StylingAndCustomization.mdx`\n\n<!-- File: .claude-plugin/marketplace.json (Tokens: ~300 | Category: marketplace) -->\n# Claude Plugin Marketplace Catalog\n\nPath: `.claude-plugin/marketplace.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/NangoHQ/nango/HEAD/.claude-plugin/marketplace.json)\n\n<!-- File: .claude-plugin/plugin.json (Tokens: ~300 | Category: plugin-manifest) -->\n# claude-plugin Plugin Manifest\n\nPath: `.claude-plugin/plugin.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/NangoHQ/nango/HEAD/.claude-plugin/plugin.json)\n\n<!-- File: .cursor/mcp.json (Tokens: ~300 | Category: mcp-config) -->\n# Model Context Protocol (MCP) Configuration\n\nPath: `.cursor/mcp.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/NangoHQ/nango/HEAD/.cursor/mcp.json)\n</yakaai_skills>"}