[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EW40HZNKEE0WJAMD2YZ2FF":3,"skill-same:01M7EW40HZNKEE0WJAMD2YZ2FF":45},{"skillNo":4,"name":5,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7EW40HZNKEE0WJAMD2YZ2FF","ams-swc-pro",null,"TanNhatCMS\u002Fjarvis","TanNhatCMS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F113796420?v=4","01M753MV17KG5CD3152G3WQEQY","KietNT","01M7EKEDYVYQ6PWVJJMZ911VMX",0,"MIT","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-swc-pro\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: swc-pro\ndescription: Use SWC for fast transpilation: config, plugins, integration with Next.js\u002FVite\u002FRollup, and migration from Babel. Use when replacing Babel or speeding up transforms.\ncategory: development\n---\n\n# SWC Pro\n\nA practical guide to SWC (Speedy Web Compiler): the Rust-based platform for JavaScript\u002FTypeScript transformation — configuration, framework integrations, the plugin system, and migrating from Babel without breaking behavior.\n\n## Overview\n\nSWC replaces Babel's transform pipeline with a Rust implementation that's roughly 20x faster, covering parsing, transpiling (TS\u002FJSX → JS), and minification (`swcMinify`). It's the engine behind Next.js's compiler and available as a loader\u002Fplugin for webpack, Vite, and Rollup. The mental shift from Babel: **SWC is a single fast binary with a narrower plugin story** — most Babel plugins have no direct equivalent, so migration means re-expressing config, not porting plugins one-to-one.\n\n## When to use\n\n- Speeding up webpack builds (`swc-loader` replacing `babel-loader`).\n- Next.js projects (already the default compiler — know how to configure it).\n- Vite\u002FRollup pipelines via `@vitejs\u002Fplugin-react-swc` \u002F `rollup-plugin-swc`.\n- Minification with `swcMinify` as a terser alternative.\n- Evaluating Babel → SWC migration.\n\n## Core concepts\n\n- **`.swcrc`.** JSON config: `jsc.parser` (typescript\u002Ftsx, ecmascript\u002Fjsx, decorators), `jsc.target` (es2020...), `jsc.transform.react` (runtime: automatic\u002Fclassic, development), `module.type` (es6\u002Fcommonjs), `minify`.\n- **Parser options.** `syntax: 'typescript'`, `tsx: true`, `decorators: true` (+ `decoratorsBeforeExport` for legacy decorator semantics), `dynamicImport: true`.\n- **React transform.** `runtime: 'automatic'` for the new JSX transform; `development: true` adds debug info — must match between dev and build configs or behavior differs.\n- **Minifier.** `minify: true` + `jsc.minify` options (compress\u002Fmangle). Faster than Terser, comparable output; test mangling on your codebase.\n- **Plugins (WASM).** SWC plugins are WebAssembly modules (`@swc\u002Fplugin-styled-components`, relay, etc.) — a smaller ecosystem than Babel's; check availability before migrating a plugin-dependent setup.\n- **Visitors.** For custom transforms, SWC's Rust visitor API (advanced) — most teams never need this; config + existing plugins suffice.\n\n## Practical workflow\n\n**1. Basic config.**\n```json\n{\n  \"$schema\": \"https:\u002F\u002Fjson.schemastore.org\u002Fswcrc\",\n  \"jsc\": {\n    \"parser\": { \"syntax\": \"typescript\", \"tsx\": true, \"decorators\": true },\n    \"target\": \"es2020\",\n    \"transform\": { \"react\": { \"runtime\": \"automatic\", \"development\": false } }\n  },\n  \"module\": { \"type\": \"es6\" },\n  \"sourceMaps\": true\n}\n```\n\n**2. webpack integration.**\n```js\n\u002F\u002F replace babel-loader\n{ test: \u002F\\.[jt]sx?$\u002F, exclude: \u002Fnode_modules\u002F, use: {\n  loader: 'swc-loader',\n  options: { jsc: { parser: { syntax: 'typescript', tsx: true }, target: 'es2020',\n    transform: { react: { runtime: 'automatic' } } } } } }\n```\n\n**3. Next.js.** SWC is default; customize in `next.config.js` (`swcMinify`, `modularizeImports`, `transpilePackages`). styled-components support via `compiler.styledComponents: true`.\n\n**4. Migrate from Babel.**\n- Inventory `.babelrc` plugins\u002Fpresets → map each to SWC config or a WASM plugin.\n- Common gaps: custom Babel plugins (rewrite as SWC WASM plugin or drop), `babel-plugin-macros`, specific preset-env targeting (use `jsc.target` + browserslist via `env`).\n- Diff build outputs on a sample: bundle size, runtime behavior, sourcemaps. Run the full test suite against SWC-built code.\n\n**5. Verify.** Build → run e2e tests → compare bundle sizes → check sourcemaps resolve in error tracking.\n\n## Common pitfalls\n\n- **Babel plugin has no SWC equivalent.** The #1 migration blocker. Audit plugin usage first; some Babel-isms (macros, custom transforms) must be reimplemented or removed.\n- **Decorator semantics.** Legacy vs 2022 decorators differ; mismatched `decorators` config silently changes behavior. Match what your framework expects (Angular vs MobX vs TypeORM differ).\n- **Dev\u002Fprod transform mismatch.** `development: true` in dev but not prod (or vice versa) causes React warning\u002Fbehavior differences. Keep the react transform consistent.\n- **Assuming type checking.** Like esbuild, SWC strips types without checking. `tsc --noEmit` stays in CI.\n- **Minify regressions.** `swcMinify` is excellent but not identical to Terser — property mangling and compress passes can break code relying on function names (e.g., some DI patterns). Test minified builds.\n- **`.swcrc` discovery.** SWC reads `.swcrc` from the file's directory upward; monorepos need per-package configs or explicit `options` in loader config — implicit discovery surprises.\n- **WASM plugin versioning.** SWC WASM plugins must match the SWC core version. Upgrading SWC without upgrading plugins breaks builds cryptically.\n- **Source map quality.** Verify mappings in production error tracking after switching — minifier + transpiler changes can degrade them.\n","# SWC Pro\n\nA practical guide to SWC (Speedy Web Compiler): the Rust-based platform for JavaScript\u002FTypeScript transformation — configuration, framework integrations, the plugin system, and migrating from Babel without breaking behavior.\n\n## Overview\n\nSWC replaces Babel's transform pipeline with a Rust implementation that's roughly 20x faster, covering parsing, transpiling (TS\u002FJSX → JS), and minification (`swcMinify`). It's the engine behind Next.js's compiler and available as a loader\u002Fplugin for webpack, Vite, and Rollup. The mental shift from Babel: **SWC is a single fast binary with a narrower plugin story** — most Babel plugins have no direct equivalent, so migration means re-expressing config, not porting plugins one-to-one.\n\n## When to use\n\n- Speeding up webpack builds (`swc-loader` replacing `babel-loader`).\n- Next.js projects (already the default compiler — know how to configure it).\n- Vite\u002FRollup pipelines via `@vitejs\u002Fplugin-react-swc` \u002F `rollup-plugin-swc`.\n- Minification with `swcMinify` as a terser alternative.\n- Evaluating Babel → SWC migration.\n\n## Core concepts\n\n- **`.swcrc`.** JSON config: `jsc.parser` (typescript\u002Ftsx, ecmascript\u002Fjsx, decorators), `jsc.target` (es2020...), `jsc.transform.react` (runtime: automatic\u002Fclassic, development), `module.type` (es6\u002Fcommonjs), `minify`.\n- **Parser options.** `syntax: 'typescript'`, `tsx: true`, `decorators: true` (+ `decoratorsBeforeExport` for legacy decorator semantics), `dynamicImport: true`.\n- **React transform.** `runtime: 'automatic'` for the new JSX transform; `development: true` adds debug info — must match between dev and build configs or behavior differs.\n- **Minifier.** `minify: true` + `jsc.minify` options (compress\u002Fmangle). Faster than Terser, comparable output; test mangling on your codebase.\n- **Plugins (WASM).** SWC plugins are WebAssembly modules (`@swc\u002Fplugin-styled-components`, relay, etc.) — a smaller ecosystem than Babel's; check availability before migrating a plugin-dependent setup.\n- **Visitors.** For custom transforms, SWC's Rust visitor API (advanced) — most teams never need this; config + existing plugins suffice.\n\n## Practical workflow\n\n**1. Basic config.**\n```json\n{\n  \"$schema\": \"https:\u002F\u002Fjson.schemastore.org\u002Fswcrc\",\n  \"jsc\": {\n    \"parser\": { \"syntax\": \"typescript\", \"tsx\": true, \"decorators\": true },\n    \"target\": \"es2020\",\n    \"transform\": { \"react\": { \"runtime\": \"automatic\", \"development\": false } }\n  },\n  \"module\": { \"type\": \"es6\" },\n  \"sourceMaps\": true\n}\n```\n\n**2. webpack integration.**\n```js\n\u002F\u002F replace babel-loader\n{ test: \u002F\\.[jt]sx?$\u002F, exclude: \u002Fnode_modules\u002F, use: {\n  loader: 'swc-loader',\n  options: { jsc: { parser: { syntax: 'typescript', tsx: true }, target: 'es2020',\n    transform: { react: { runtime: 'automatic' } } } } } }\n```\n\n**3. Next.js.** SWC is default; customize in `next.config.js` (`swcMinify`, `modularizeImports`, `transpilePackages`). styled-components support via `compiler.styledComponents: true`.\n\n**4. Migrate from Babel.**\n- Inventory `.babelrc` plugins\u002Fpresets → map each to SWC config or a WASM plugin.\n- Common gaps: custom Babel plugins (rewrite as SWC WASM plugin or drop), `babel-plugin-macros`, specific preset-env targeting (use `jsc.target` + browserslist via `env`).\n- Diff build outputs on a sample: bundle size, runtime behavior, sourcemaps. Run the full test suite against SWC-built code.\n\n**5. Verify.** Build → run e2e tests → compare bundle sizes → check sourcemaps resolve in error tracking.\n\n## Common pitfalls\n\n- **Babel plugin has no SWC equivalent.** The #1 migration blocker. Audit plugin usage first; some Babel-isms (macros, custom transforms) must be reimplemented or removed.\n- **Decorator semantics.** Legacy vs 2022 decorators differ; mismatched `decorators` config silently changes behavior. Match what your framework expects (Angular vs MobX vs TypeORM differ).\n- **Dev\u002Fprod transform mismatch.** `development: true` in dev but not prod (or vice versa) causes React warning\u002Fbehavior differences. Keep the react transform consistent.\n- **Assuming type checking.** Like esbuild, SWC strips types without checking. `tsc --noEmit` stays in CI.\n- **Minify regressions.** `swcMinify` is excellent but not identical to Terser — property mangling and compress passes can break code relying on function names (e.g., some DI patterns). Test minified builds.\n- **`.swcrc` discovery.** SWC reads `.swcrc` from the file's directory upward; monorepos need per-package configs or explicit `options` in loader config — implicit discovery surprises.\n- **WASM plugin versioning.** SWC WASM plugins must match the SWC core version. Upgrading SWC without upgrading plugins breaks builds cryptically.\n- **Source map quality.** Verify mappings in production error tracking after switching — minifier + transpiler changes can degrade them.\n",{},"main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-swc-pro",1,"https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis","https:\u002F\u002Fgithub.com\u002FTanNhatCMS","https:\u002F\u002Fmrkiet.name.vn","2026-11-07 14:23:08",{"source":7,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add TanNhatCMS\u002Fjarvis --skill ams-swc-pro",{"tool":37,"command":38},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill ams-swc-pro",{"tool":40,"command":41},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill ams-swc-pro","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-swc-pro\u002FSKILL.md",true,[],[46,53,61,68,75,82],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":18},"01M7EWYJR0J8DARY7E59Z6Y9MV","web-scrape","Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open\u002Ffetch fails on JS-heavy pages, or when you need clean markdown\u002Fstructured extraction from a site. Requires FIRECRAWL_API_KEY.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fweb-scrape\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":57,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":18},"01M7EWYBN5P6F2AJG3FR24T9BP","design-taste-frontend","tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML\u002FCSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, \"AI-made\", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Not for dashboards or app screens.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":18},"01M7EWY8FQFNQ2GB7NZZWGSSDX","test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-tdd\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":18},"01M7EWY5SHBFRH1HDHVWM9K7TV","systematic-debugging","Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-debugging\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":18},"01M7EWY3NM0Z0JAKS7HDZ24K66","requesting-code-review","Use when completing tasks, implementing major features, or before merging to verify work meets requirements","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-code-review\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":18},"01M7EWY0WRMWX4M9ZFY0WKC593","brainstorming","You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-brainstorming\u002FSKILL.md",[],[]]