[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CVVH4V2ZS4HV36CXADSJBW":3,"skill-same:01M7CVVH4V2ZS4HV36CXADSJBW":64},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":35,"commitSha":36,"skillDirectory":37,"forksCount":14,"repositoryHtmlUrl":38,"repositoryHomepageUrl":39,"ownerHtmlUrl":40,"ownerBlogUrl":41,"ownerDescription":42,"updatedAt":43,"install":44,"resources":57},"01M7CVVH4V2ZS4HV36CXADSJBW","turbopack",null,"Turbopack expert guidance. Use when configuring the Next.js bundler, optimizing HMR, debugging build issues, or understanding the Turbopack vs Webpack differences.","realsudarshan\u002FSD-skill","realsudarshan","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128029723?v=4","01M7CTP2JEKQ9KBJ51NRZ2777Z","Sudarshan Dhakal","01M7CTP2JYR2PRY3BWGA30HX7J",0,"MIT","https:\u002F\u002Fgithub.com\u002Frealsudarshan\u002FSD-skill\u002Fblob\u002Fmain\u002Fofficial-openai\u002Fopenai-local-vercel-turbopack\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: turbopack\ndescription: Turbopack expert guidance. Use when configuring the Next.js bundler, optimizing HMR, debugging build issues, or understanding the Turbopack vs Webpack differences.\nmetadata:\n  priority: 4\n  docs:\n    - \"https:\u002F\u002Fturbo.build\u002Fpack\u002Fdocs\"\n    - \"https:\u002F\u002Fnextjs.org\u002Fdocs\u002Farchitecture\u002Fturbopack\"\n  sitemap: \"https:\u002F\u002Fturbo.build\u002Fsitemap.xml\"\n  pathPatterns:\n    - 'next.config.*'\n  bashPatterns:\n    - '\\bnext\\s+dev\\s+--turbo\\b'\n    - '\\bnext\\s+dev\\s+--turbopack\\b'\n---\n\n# Turbopack\n\nYou are an expert in Turbopack â€” the Rust-powered JavaScript\u002FTypeScript bundler built by Vercel. It is the default bundler in Next.js 16.\n\n## Key Features\n\n- **Instant HMR**: Hot Module Replacement that doesn't degrade with app size\n- **File System Caching (Stable)**: Dev server artifacts cached on disk between restarts â€” up to 14x faster startup on large projects. Enabled by default in Next.js 16.1+, no config needed. Build caching planned next.\n- **Multi-environment builds**: Browser, Server, Edge, SSR, React Server Components\n- **Native RSC support**: Built for React Server Components from the ground up\n- **TypeScript, JSX, CSS, CSS Modules, WebAssembly**: Out of the box\n- **Rust-powered**: Incremental computation engine for maximum performance\n\n## Configuration (Next.js 16)\n\nIn Next.js 16, Turbopack config is top-level (moved from `experimental.turbopack`):\n\n```js\n\u002F\u002F next.config.ts\nimport type { NextConfig } from 'next'\n\nconst nextConfig: NextConfig = {\n  turbopack: {\n    \u002F\u002F Resolve aliases (like webpack resolve.alias)\n    resolveAlias: {\n      'old-package': 'new-package',\n    },\n    \u002F\u002F Custom file extensions to resolve\n    resolveExtensions: ['.ts', '.tsx', '.js', '.jsx', '.json'],\n  },\n}\n\nexport default nextConfig\n```\n\n## CSS and CSS Modules Handling\n\nTurbopack handles CSS natively without additional configuration.\n\n### Global CSS\n\nImport global CSS in your root layout:\n\n```tsx\n\u002F\u002F app\u002Flayout.tsx\nimport '.\u002Fglobals.css'\n```\n\n### CSS Modules\n\nCSS Modules work out of the box with `.module.css` files:\n\n```tsx\n\u002F\u002F components\u002FButton.tsx\nimport styles from '.\u002FButton.module.css'\n\nexport function Button({ children }) {\n  return \u003Cbutton className={styles.primary}>{children}\u003C\u002Fbutton>\n}\n```\n\n### PostCSS\n\nTurbopack reads your `postcss.config.js` automatically. Tailwind CSS v4 works with zero config:\n\n```js\n\u002F\u002F postcss.config.js\nmodule.exports = {\n  plugins: {\n    '@tailwindcss\u002Fpostcss': {},\n    autoprefixer: {},\n  },\n}\n```\n\n### Sass \u002F SCSS\n\nInstall `sass` and import `.scss` files directly â€” Turbopack compiles them natively:\n\n```bash\nnpm install sass\n```\n\n```tsx\nimport styles from '.\u002FComponent.module.scss'\n```\n\n### Common CSS pitfalls\n\n- **CSS ordering differs from webpack**: Turbopack may load CSS chunks in a different order. Avoid relying on source-order specificity across files â€” use more specific selectors or CSS Modules.\n- **`@import` in global CSS**: Use standard CSS `@import` â€” Turbopack resolves them, but circular imports cause build failures.\n- **CSS-in-JS libraries**: `styled-components` and `emotion` work but require their SWC plugins configured under `compiler` in next.config.\n\n## Tree Shaking\n\nTurbopack performs tree shaking at the module level in production builds. Key behaviors:\n\n- **ES module exports**: Only used exports are included â€” write `export` on each function\u002Fconstant rather than barrel `export *`\n- **Side-effect-free packages**: Mark packages as side-effect-free in `package.json` to enable aggressive tree shaking:\n\n```json\n{\n  \"name\": \"my-ui-lib\",\n  \"sideEffects\": false\n}\n```\n\n- **Barrel file optimization**: Turbopack can skip unused re-exports from barrel files (`index.ts`) when the package declares `\"sideEffects\": false`\n- **Dynamic imports**: `import()` expressions create async chunk boundaries â€” Turbopack splits these into separate chunks automatically\n\n### Diagnosing large bundles\n\n**Built-in analyzer (Next.js 16.1+, experimental)**: Works natively with Turbopack. Offers route-specific filtering, import tracing, and RSC boundary analysis:\n\n```ts\n\u002F\u002F next.config.ts\nconst nextConfig: NextConfig = {\n  experimental: {\n    bundleAnalyzer: true,\n  },\n}\n```\n\n**Legacy `@next\u002Fbundle-analyzer`**: Still works as a fallback:\n\n```bash\nANALYZE=true next build\n```\n\n```ts\n\u002F\u002F next.config.ts\nimport withBundleAnalyzer from '@next\u002Fbundle-analyzer'\n\nconst nextConfig = withBundleAnalyzer({\n  enabled: process.env.ANALYZE === 'true',\n})({\n  \u002F\u002F your config\n})\n```\n\n## Custom Loader Migration from Webpack\n\nTurbopack does not support webpack loaders directly. Here is how to migrate common patterns:\n\n| Webpack Loader | Turbopack Equivalent |\n|----------------|---------------------|\n| `css-loader` + `style-loader` | Built-in CSS support â€” remove loaders |\n| `sass-loader` | Built-in â€” install `sass` package |\n| `postcss-loader` | Built-in â€” reads `postcss.config.js` |\n| `file-loader` \u002F `url-loader` | Built-in static asset handling |\n| `svgr` \u002F `@svgr\u002Fwebpack` | Use `@svgr\u002Fwebpack` via `turbopack.rules` |\n| `raw-loader` | Use `import x from '.\u002Ffile?raw'` |\n| `graphql-tag\u002Floader` | Use a build-time codegen step instead |\n| `worker-loader` | Use native `new Worker(new URL(...))` syntax |\n\n### Configuring custom rules (loader replacement)\n\nFor loaders that have no built-in equivalent, use `turbopack.rules`:\n\n```js\n\u002F\u002F next.config.ts\nconst nextConfig: NextConfig = {\n  turbopack: {\n    rules: {\n      '*.svg': {\n        loaders: ['@svgr\u002Fwebpack'],\n        as: '*.js',\n      },\n    },\n  },\n}\n```\n\n### When migration isn't possible\n\nIf a webpack loader has no Turbopack equivalent and no workaround, fall back to webpack:\n\n```js\nconst nextConfig: NextConfig = {\n  bundler: 'webpack',\n}\n```\n\nFile an issue at [github.com\u002Fvercel\u002Fnext.js](https:\u002F\u002Fgithub.com\u002Fvercel\u002Fnext.js) â€” the Turbopack team tracks loader parity requests.\n\n## Production Build Diagnostics\n\n### Build failing with Turbopack\n\n1. **Check for unsupported config**: Remove any `webpack()` function from next.config â€” it's ignored by Turbopack and may mask the real config\n2. **Verify `turbopack.rules`**: Ensure custom rules reference valid loaders that are installed\n3. **Check for Node.js built-in usage in edge\u002Fclient**: Turbopack enforces environment boundaries â€” `fs`, `path`, etc. cannot be imported in client or edge bundles\n4. **Module not found errors**: Ensure `turbopack.resolveAlias` covers any custom resolution that was previously in webpack config\n\n### Build output too large\n\n- Audit `\"use client\"` directives â€” each client component boundary creates a new chunk\n- Check for accidentally bundled server-only packages in client components\n- Use `server-only` package to enforce server\u002Fclient boundaries at import time:\n\n```bash\nnpm install server-only\n```\n\n```ts\n\u002F\u002F lib\u002Fdb.ts\nimport 'server-only' \u002F\u002F Build fails if imported in a client component\n```\n\n### Comparing webpack vs Turbopack output\n\nRun both bundlers and compare:\n\n```bash\n# Turbopack build (default in Next.js 16)\nnext build\n\n# Webpack build\nBUNDLER=webpack next build\n```\n\nCompare `.next\u002F` output sizes and page-level chunks.\n\n## Performance Profiling\n\n### HMR profiling\n\nEnable verbose HMR timing in development:\n\n```bash\nNEXT_TURBOPACK_TRACING=1 next dev\n```\n\nThis writes a `trace.json` to the project root â€” open it in `chrome:\u002F\u002Ftracing` or [Perfetto](https:\u002F\u002Fui.perfetto.dev\u002F) to see module-level timing.\n\n### Build profiling\n\nProfile production builds:\n\n```bash\nNEXT_TURBOPACK_TRACING=1 next build\n```\n\nLook for:\n- **Long-running transforms**: Indicates a slow SWC plugin or heavy PostCSS config\n- **Large module graphs**: Reduce barrel file re-exports\n- **Cache misses**: If incremental builds aren't hitting cache, check for files that change every build (e.g., generated timestamps)\n\n### Memory usage\n\nTurbopack's Rust core manages its own memory. If builds OOM:\n- Increase Node.js heap: `NODE_OPTIONS='--max-old-space-size=8192' next build`\n- Reduce concurrent tasks if running inside Turborepo: `turbo build --concurrency=2`\n\n## Turbopack vs Webpack\n\n| Feature | Turbopack | Webpack |\n|---------|-----------|---------|\n| Language | Rust | JavaScript |\n| HMR speed | Constant (O(1)) | Degrades with app size |\n| RSC support | Native | Plugin-based |\n| Cold start | Fast | Slower |\n| Ecosystem | Growing | Massive (loaders, plugins) |\n| Status in Next.js 16 | Default | Still supported |\n| Tree shaking | Module-level | Module-level |\n| CSS handling | Built-in | Requires loaders |\n| Production builds | Supported | Supported |\n\n## When You Might Need Webpack\n\n- Custom webpack loaders with no Turbopack equivalent\n- Complex webpack plugin configurations (e.g., `ModuleFederationPlugin`)\n- Specific webpack features not yet in Turbopack (e.g., custom `externals` functions)\n\nTo use webpack instead:\n```js\n\u002F\u002F next.config.ts\nconst nextConfig: NextConfig = {\n  bundler: 'webpack', \u002F\u002F Opt out of Turbopack\n}\n```\n\n## Development vs Production\n\n- **Development**: Turbopack provides instant HMR and fast refresh\n- **Production**: Turbopack handles the production build (replaces webpack in Next.js 16)\n\n## Common Issues\n\n1. **Missing loader equivalent**: Some webpack loaders don't have Turbopack equivalents yet. Check Turbopack docs for supported transformations.\n2. **Config migration**: Move `experimental.turbopack` to top-level `turbopack` in next.config.\n3. **Custom aliases**: Use `turbopack.resolveAlias` instead of `webpack.resolve.alias`.\n4. **CSS ordering changes**: Test visual regressions when migrating â€” CSS chunk order may differ.\n5. **Environment boundary errors**: Server-only modules imported in client components fail at build time â€” use `server-only` package.\n\n## Official Documentation\n\n- [Turbopack](https:\u002F\u002Fturborepo.dev\u002Fpack)\n- [Turbopack Documentation](https:\u002F\u002Fturborepo.dev\u002Fpack\u002Fdocs)\n- [Next.js Turbopack Config](https:\u002F\u002Fnextjs.org\u002Fdocs\u002Fapp\u002Fapi-reference\u002Fconfig\u002Fnext-config-js\u002Fturbopack)\n- [GitHub: Turbopack](https:\u002F\u002Fgithub.com\u002Fvercel\u002Fturborepo)\n","# Turbopack\n\nYou are an expert in Turbopack â€” the Rust-powered JavaScript\u002FTypeScript bundler built by Vercel. It is the default bundler in Next.js 16.\n\n## Key Features\n\n- **Instant HMR**: Hot Module Replacement that doesn't degrade with app size\n- **File System Caching (Stable)**: Dev server artifacts cached on disk between restarts â€” up to 14x faster startup on large projects. Enabled by default in Next.js 16.1+, no config needed. Build caching planned next.\n- **Multi-environment builds**: Browser, Server, Edge, SSR, React Server Components\n- **Native RSC support**: Built for React Server Components from the ground up\n- **TypeScript, JSX, CSS, CSS Modules, WebAssembly**: Out of the box\n- **Rust-powered**: Incremental computation engine for maximum performance\n\n## Configuration (Next.js 16)\n\nIn Next.js 16, Turbopack config is top-level (moved from `experimental.turbopack`):\n\n```js\n\u002F\u002F next.config.ts\nimport type { NextConfig } from 'next'\n\nconst nextConfig: NextConfig = {\n  turbopack: {\n    \u002F\u002F Resolve aliases (like webpack resolve.alias)\n    resolveAlias: {\n      'old-package': 'new-package',\n    },\n    \u002F\u002F Custom file extensions to resolve\n    resolveExtensions: ['.ts', '.tsx', '.js', '.jsx', '.json'],\n  },\n}\n\nexport default nextConfig\n```\n\n## CSS and CSS Modules Handling\n\nTurbopack handles CSS natively without additional configuration.\n\n### Global CSS\n\nImport global CSS in your root layout:\n\n```tsx\n\u002F\u002F app\u002Flayout.tsx\nimport '.\u002Fglobals.css'\n```\n\n### CSS Modules\n\nCSS Modules work out of the box with `.module.css` files:\n\n```tsx\n\u002F\u002F components\u002FButton.tsx\nimport styles from '.\u002FButton.module.css'\n\nexport function Button({ children }) {\n  return \u003Cbutton className={styles.primary}>{children}\u003C\u002Fbutton>\n}\n```\n\n### PostCSS\n\nTurbopack reads your `postcss.config.js` automatically. Tailwind CSS v4 works with zero config:\n\n```js\n\u002F\u002F postcss.config.js\nmodule.exports = {\n  plugins: {\n    '@tailwindcss\u002Fpostcss': {},\n    autoprefixer: {},\n  },\n}\n```\n\n### Sass \u002F SCSS\n\nInstall `sass` and import `.scss` files directly â€” Turbopack compiles them natively:\n\n```bash\nnpm install sass\n```\n\n```tsx\nimport styles from '.\u002FComponent.module.scss'\n```\n\n### Common CSS pitfalls\n\n- **CSS ordering differs from webpack**: Turbopack may load CSS chunks in a different order. Avoid relying on source-order specificity across files â€” use more specific selectors or CSS Modules.\n- **`@import` in global CSS**: Use standard CSS `@import` â€” Turbopack resolves them, but circular imports cause build failures.\n- **CSS-in-JS libraries**: `styled-components` and `emotion` work but require their SWC plugins configured under `compiler` in next.config.\n\n## Tree Shaking\n\nTurbopack performs tree shaking at the module level in production builds. Key behaviors:\n\n- **ES module exports**: Only used exports are included â€” write `export` on each function\u002Fconstant rather than barrel `export *`\n- **Side-effect-free packages**: Mark packages as side-effect-free in `package.json` to enable aggressive tree shaking:\n\n```json\n{\n  \"name\": \"my-ui-lib\",\n  \"sideEffects\": false\n}\n```\n\n- **Barrel file optimization**: Turbopack can skip unused re-exports from barrel files (`index.ts`) when the package declares `\"sideEffects\": false`\n- **Dynamic imports**: `import()` expressions create async chunk boundaries â€” Turbopack splits these into separate chunks automatically\n\n### Diagnosing large bundles\n\n**Built-in analyzer (Next.js 16.1+, experimental)**: Works natively with Turbopack. Offers route-specific filtering, import tracing, and RSC boundary analysis:\n\n```ts\n\u002F\u002F next.config.ts\nconst nextConfig: NextConfig = {\n  experimental: {\n    bundleAnalyzer: true,\n  },\n}\n```\n\n**Legacy `@next\u002Fbundle-analyzer`**: Still works as a fallback:\n\n```bash\nANALYZE=true next build\n```\n\n```ts\n\u002F\u002F next.config.ts\nimport withBundleAnalyzer from '@next\u002Fbundle-analyzer'\n\nconst nextConfig = withBundleAnalyzer({\n  enabled: process.env.ANALYZE === 'true',\n})({\n  \u002F\u002F your config\n})\n```\n\n## Custom Loader Migration from Webpack\n\nTurbopack does not support webpack loaders directly. Here is how to migrate common patterns:\n\n| Webpack Loader | Turbopack Equivalent |\n|----------------|---------------------|\n| `css-loader` + `style-loader` | Built-in CSS support â€” remove loaders |\n| `sass-loader` | Built-in â€” install `sass` package |\n| `postcss-loader` | Built-in â€” reads `postcss.config.js` |\n| `file-loader` \u002F `url-loader` | Built-in static asset handling |\n| `svgr` \u002F `@svgr\u002Fwebpack` | Use `@svgr\u002Fwebpack` via `turbopack.rules` |\n| `raw-loader` | Use `import x from '.\u002Ffile?raw'` |\n| `graphql-tag\u002Floader` | Use a build-time codegen step instead |\n| `worker-loader` | Use native `new Worker(new URL(...))` syntax |\n\n### Configuring custom rules (loader replacement)\n\nFor loaders that have no built-in equivalent, use `turbopack.rules`:\n\n```js\n\u002F\u002F next.config.ts\nconst nextConfig: NextConfig = {\n  turbopack: {\n    rules: {\n      '*.svg': {\n        loaders: ['@svgr\u002Fwebpack'],\n        as: '*.js',\n      },\n    },\n  },\n}\n```\n\n### When migration isn't possible\n\nIf a webpack loader has no Turbopack equivalent and no workaround, fall back to webpack:\n\n```js\nconst nextConfig: NextConfig = {\n  bundler: 'webpack',\n}\n```\n\nFile an issue at [github.com\u002Fvercel\u002Fnext.js](https:\u002F\u002Fgithub.com\u002Fvercel\u002Fnext.js) â€” the Turbopack team tracks loader parity requests.\n\n## Production Build Diagnostics\n\n### Build failing with Turbopack\n\n1. **Check for unsupported config**: Remove any `webpack()` function from next.config â€” it's ignored by Turbopack and may mask the real config\n2. **Verify `turbopack.rules`**: Ensure custom rules reference valid loaders that are installed\n3. **Check for Node.js built-in usage in edge\u002Fclient**: Turbopack enforces environment boundaries â€” `fs`, `path`, etc. cannot be imported in client or edge bundles\n4. **Module not found errors**: Ensure `turbopack.resolveAlias` covers any custom resolution that was previously in webpack config\n\n### Build output too large\n\n- Audit `\"use client\"` directives â€” each client component boundary creates a new chunk\n- Check for accidentally bundled server-only packages in client components\n- Use `server-only` package to enforce server\u002Fclient boundaries at import time:\n\n```bash\nnpm install server-only\n```\n\n```ts\n\u002F\u002F lib\u002Fdb.ts\nimport 'server-only' \u002F\u002F Build fails if imported in a client component\n```\n\n### Comparing webpack vs Turbopack output\n\nRun both bundlers and compare:\n\n```bash\n# Turbopack build (default in Next.js 16)\nnext build\n\n# Webpack build\nBUNDLER=webpack next build\n```\n\nCompare `.next\u002F` output sizes and page-level chunks.\n\n## Performance Profiling\n\n### HMR profiling\n\nEnable verbose HMR timing in development:\n\n```bash\nNEXT_TURBOPACK_TRACING=1 next dev\n```\n\nThis writes a `trace.json` to the project root â€” open it in `chrome:\u002F\u002Ftracing` or [Perfetto](https:\u002F\u002Fui.perfetto.dev\u002F) to see module-level timing.\n\n### Build profiling\n\nProfile production builds:\n\n```bash\nNEXT_TURBOPACK_TRACING=1 next build\n```\n\nLook for:\n- **Long-running transforms**: Indicates a slow SWC plugin or heavy PostCSS config\n- **Large module graphs**: Reduce barrel file re-exports\n- **Cache misses**: If incremental builds aren't hitting cache, check for files that change every build (e.g., generated timestamps)\n\n### Memory usage\n\nTurbopack's Rust core manages its own memory. If builds OOM:\n- Increase Node.js heap: `NODE_OPTIONS='--max-old-space-size=8192' next build`\n- Reduce concurrent tasks if running inside Turborepo: `turbo build --concurrency=2`\n\n## Turbopack vs Webpack\n\n| Feature | Turbopack | Webpack |\n|---------|-----------|---------|\n| Language | Rust | JavaScript |\n| HMR speed | Constant (O(1)) | Degrades with app size |\n| RSC support | Native | Plugin-based |\n| Cold start | Fast | Slower |\n| Ecosystem | Growing | Massive (loaders, plugins) |\n| Status in Next.js 16 | Default | Still supported |\n| Tree shaking | Module-level | Module-level |\n| CSS handling | Built-in | Requires loaders |\n| Production builds | Supported | Supported |\n\n## When You Might Need Webpack\n\n- Custom webpack loaders with no Turbopack equivalent\n- Complex webpack plugin configurations (e.g., `ModuleFederationPlugin`)\n- Specific webpack features not yet in Turbopack (e.g., custom `externals` functions)\n\nTo use webpack instead:\n```js\n\u002F\u002F next.config.ts\nconst nextConfig: NextConfig = {\n  bundler: 'webpack', \u002F\u002F Opt out of Turbopack\n}\n```\n\n## Development vs Production\n\n- **Development**: Turbopack provides instant HMR and fast refresh\n- **Production**: Turbopack handles the production build (replaces webpack in Next.js 16)\n\n## Common Issues\n\n1. **Missing loader equivalent**: Some webpack loaders don't have Turbopack equivalents yet. Check Turbopack docs for supported transformations.\n2. **Config migration**: Move `experimental.turbopack` to top-level `turbopack` in next.config.\n3. **Custom aliases**: Use `turbopack.resolveAlias` instead of `webpack.resolve.alias`.\n4. **CSS ordering changes**: Test visual regressions when migrating â€” CSS chunk order may differ.\n5. **Environment boundary errors**: Server-only modules imported in client components fail at build time â€” use `server-only` package.\n\n## Official Documentation\n\n- [Turbopack](https:\u002F\u002Fturborepo.dev\u002Fpack)\n- [Turbopack Documentation](https:\u002F\u002Fturborepo.dev\u002Fpack\u002Fdocs)\n- [Next.js Turbopack Config](https:\u002F\u002Fnextjs.org\u002Fdocs\u002Fapp\u002Fapi-reference\u002Fconfig\u002Fnext-config-js\u002Fturbopack)\n- [GitHub: Turbopack](https:\u002F\u002Fgithub.com\u002Fvercel\u002Fturborepo)\n",{"name":5,"metadata":24,"description":7},{"docs":25,"sitemap":28,"priority":29,"bashPatterns":30,"pathPatterns":33},[26,27],"https:\u002F\u002Fturbo.build\u002Fpack\u002Fdocs","https:\u002F\u002Fnextjs.org\u002Fdocs\u002Farchitecture\u002Fturbopack","https:\u002F\u002Fturbo.build\u002Fsitemap.xml",4,[31,32],"\\bnext\\s+dev\\s+--turbo\\b","\\bnext\\s+dev\\s+--turbopack\\b",[34],"next.config.*","main","92c2f40ebfad0c0aa3cc1faa89ffd6b23f9e8d1b","official-openai\u002Fopenai-local-vercel-turbopack","https:\u002F\u002Fgithub.com\u002Frealsudarshan\u002FSD-skill","https:\u002F\u002Fsd-skill.vercel.app","https:\u002F\u002Fgithub.com\u002Frealsudarshan","sudarshandhakal.com.np","Innvotative","2026-11-12 23:03:50",{"source":8,"skillName":5,"commands":45,"prompt":55,"zipAvailable":56},[46,49,52],{"tool":47,"command":48},"npx","npx skills add realsudarshan\u002FSD-skill --skill turbopack",{"tool":50,"command":51},"bunx","bunx skills add realsudarshan\u002FSD-skill --skill turbopack",{"tool":53,"command":54},"pnpm","pnpm dlx skills add realsudarshan\u002FSD-skill --skill turbopack","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Frealsudarshan\u002FSD-skill\u002Fblob\u002Fmain\u002Fofficial-openai\u002Fopenai-local-vercel-turbopack\u002FSKILL.md",true,[58],{"path":59,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":62,"sourceHtmlUrl":63},"agents\u002Fopenai.yaml","REFERENCE","参考文档",88,"https:\u002F\u002Fgithub.com\u002Frealsudarshan\u002FSD-skill\u002Fblob\u002Fmain\u002Fofficial-openai\u002Fopenai-local-vercel-turbopack\u002Fagents\u002Fopenai.yaml",[65,74,82,90,98,106],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":69,"licenseFileUrl":70,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7CW5Y6EPMPMNDWE4EN2GXRX","winui-app","Bootstrap, develop, and design modern WinUI 3 desktop applications with C# and the Windows App SDK using official Microsoft guidance, WinUI Gallery patterns, Windows App SDK samples, and CommunityToolkit components. Use when creating a brand new app, preparing a machine for WinUI, reviewing, refactoring, planning, troubleshooting, environment-checking, or setting up WinUI 3 XAML, controls, navigation, windowing, theming, accessibility, responsiveness, performance, deployment, or related Windows app design and development work.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Frealsudarshan\u002FSD-skill\u002Fblob\u002Fmain\u002Freccomended\u002Fwinui-app\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Frealsudarshan\u002FSD-skill\u002Fblob\u002Fmain\u002Freccomended\u002Fwinui-app\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":78,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7CW5RWFX7616ENEG573VFWG","vercel-deploy","Deploy applications and websites to Vercel. Use when the user requests deployment actions like \"deploy my app\", \"deploy and give me the link\", \"push this live\", or \"create a preview deployment\".","https:\u002F\u002Fgithub.com\u002Frealsudarshan\u002FSD-skill\u002Fblob\u002Fmain\u002Freccomended\u002Fvercel-deploy\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Frealsudarshan\u002FSD-skill\u002Fblob\u002Fmain\u002Freccomended\u002Fvercel-deploy\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":69,"licenseFileUrl":86,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7CW5M4VZHQPWG764X1W0S3B","security-best-practices","Perform language and framework specific security best-practice reviews and suggest improvements. Trigger only when the user explicitly requests security best practices guidance, a security review\u002Freport, or secure-by-default coding help. Trigger only for supported languages (python, javascript\u002Ftypescript, go). Do not trigger for general code review, debugging, or non-security tasks.","https:\u002F\u002Fgithub.com\u002Frealsudarshan\u002FSD-skill\u002Fblob\u002Fmain\u002Freccomended\u002Fsecurity-best-practices\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Frealsudarshan\u002FSD-skill\u002Fblob\u002Fmain\u002Freccomended\u002Fsecurity-best-practices\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":69,"licenseFileUrl":94,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"01M7CW5EBTWA7PQ54HYFT1YW39","playwright","Use when the task requires automating a real browser from the terminal (navigation, form filling, snapshots, screenshots, data extraction, UI-flow debugging) via `playwright-cli` or the bundled wrapper script.","https:\u002F\u002Fgithub.com\u002Frealsudarshan\u002FSD-skill\u002Fblob\u002Fmain\u002Freccomended\u002Fplaywright\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Frealsudarshan\u002FSD-skill\u002Fblob\u002Fmain\u002Freccomended\u002Fplaywright\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":69,"licenseFileUrl":102,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":19},"01M7CW4DA7SZ4D9JMR3P7VJVM0","openai-docs","Use when the user asks how to build with OpenAI products or APIs and needs up-to-date official documentation with citations, help choosing the latest model for a use case, or model upgrade and prompt-upgrade guidance; prioritize OpenAI docs MCP tools, use bundled references only as helper context, and restrict any fallback browsing to official OpenAI domains.","https:\u002F\u002Fgithub.com\u002Frealsudarshan\u002FSD-skill\u002Fblob\u002Fmain\u002Freccomended\u002Fopenai-docs\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Frealsudarshan\u002FSD-skill\u002Fblob\u002Fmain\u002Freccomended\u002Fopenai-docs\u002FSKILL.md",[],[],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":69,"licenseFileUrl":110,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":19},"01M7CW3EHY7X60KB9SYEMRD3YR","netlify-deploy","Deploy web projects to Netlify using the Netlify CLI (`npx netlify`). Use when the user asks to deploy, host, publish, or link a site\u002Frepo on Netlify, including preview and production deploys.","https:\u002F\u002Fgithub.com\u002Frealsudarshan\u002FSD-skill\u002Fblob\u002Fmain\u002Freccomended\u002Fnetlify-deploy\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Frealsudarshan\u002FSD-skill\u002Fblob\u002Fmain\u002Freccomended\u002Fnetlify-deploy\u002FSKILL.md",[],[]]