[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EWFCJDGQRPFWAAXSW48610":3,"skill-same:01M7EWFCJDGQRPFWAAXSW48610":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},"01M7EWFCJDGQRPFWAAXSW48610","ams-yarn-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-yarn-pro\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: yarn-pro\ndescription: Use Yarn effectively: Berry vs Classic, Plug'n'Play, workspaces, constraints, and release workflows. Use when managing JS dependencies with Yarn.\ncategory: development\n---\n\n# Yarn Pro\n\nA practical guide to Yarn — primarily modern Yarn Berry (v2+): Plug'n'Play, workspaces, constraints, and the release workflow, plus notes for teams still on Yarn Classic (v1).\n\n## Overview\n\nYarn Berry rethought package management: **Plug'n'Play (PnP)** eliminates `node_modules` entirely (packages load from zip archives via a loader), **constraints** enforce workspace consistency with Prolog-like rules, and **releases** are checked into the repo (`yarn set version`) so everyone runs the identical Yarn. It's powerful but opinionated — editor SDKs and some tools need explicit setup for PnP.\n\nKnow which Yarn you have: `yarn --version` — v1.x is Classic (node_modules, still common), v2+ is Berry.\n\n## When to use\n\n- Monorepos wanting strong consistency guarantees (constraints) and fast installs.\n- Zero-install workflows (check in `.yarn\u002Fcache` for instant CI).\n- Teams hitting phantom-dependency or version-drift issues.\n- Migrating from Classic to Berry, or maintaining a Classic repo.\n\n## Core concepts\n\n- **Plug'n'Play.** No `node_modules`; `.pnp.cjs` maps packages to zip locations. Strict: undeclared deps fail at runtime. Editor support via `yarn dlx @yarnpkg\u002Fsdks`.\n- **Zero-installs.** Commit `.yarn\u002Fcache` (zips) → `yarn install` becomes nearly instant, CI needs no network. Costs repo size; worth it for many teams.\n- **Workspaces.** Like other managers, plus `yarn workspaces foreach` for running commands across packages with topological ordering.\n- **Constraints (`constraints.pro`).** Declarative rules: \"all workspaces must use the same version of react\", \"no workspace may depend on X\". `yarn constraints` checks; `yarn constraints --fix` repairs.\n- **`packageExtensions`.** Fix packages with missing peer deps declaratively in `.yarnrc.yml` instead of forking — but prefer upstream fixes long-term.\n- **Release workflow.** `yarn version check` \u002F `yarn version apply` manage deferred version bumps across workspaces; pairs with release plugins.\n- **Classic (v1).** `node_modules` + `yarn.lock`; workspaces exist but are thinner. Still fine; just lacks Berry's strictness tooling.\n\n## Practical workflow\n\n**1. Setup (Berry).**\n```bash\nyarn init -2                    # or: yarn set version stable in existing repo\necho 'nodeLinker: pnp' >> .yarnrc.yml   # or node-modules if PnP fights your tools\nyarn install\n```\n\n**2. Daily commands.**\n```bash\nyarn add react                  # add dep\nyarn add -D typescript          # devDep\nyarn up react                   # upgrade across workspaces\nyarn dedupe                     # reduce duplicates\nyarn why react                  # explain a dependency\nyarn workspaces foreach -R --topological-dev run build\nyarn constraints --fix          # enforce consistency rules\n```\n\n**3. `.yarnrc.yml` essentials.**\n```yaml\nnodeLinker: pnp\npackageExtensions:\n  \"some-lib@*\":\n    peerDependencies: { \"react\": \"*\" }\n```\n\n**4. Editor SDKs (PnP).**\n```bash\nyarn dlx @yarnpkg\u002Fsdks vscode vim  # generates editor SDKs so TS\u002Feslint resolve PnP\n```\nWithout this, TypeScript and ESLint can't find packages under PnP.\n\n**5. CI.**\n```bash\nyarn install --immutable   # fail if lockfile would change\n```\n\n## Common pitfalls\n\n- **PnP vs tooling.** Some tools assume `node_modules` exists. Options: `nodeLinker: node-modules` (pragmatic), or `packageExtensions` + SDKs. Don't suffer silently — pick the linker that fits your toolchain.\n- **Skipping editor SDKs.** Red squiggles everywhere under PnP = missing SDKs, not broken code. Run the SDK generator.\n- **Undeclared deps.** Same strictness lesson as pnpm: `Cannot find module` → declare the dependency properly.\n- **Zero-install repo bloat.** `.yarn\u002Fcache` can grow large; use `yarn cache clean --all` equivalents judiciously and consider `enableGlobalCache` for huge monorepos.\n- **Constraints ignored.** Writing `constraints.pro` but never running `yarn constraints` in CI = documentation, not enforcement. Gate CI on it.\n- **Classic\u002FBerry confusion.** Docs and Stack Overflow answers differ wildly by version. Always check which major version an answer targets.\n- **Forgetting `--immutable` in CI.** Without it, CI may update the lockfile instead of failing on drift — the opposite of what you want.\n- **Overriding with resolutions carelessly.** `resolutions` force versions globally — powerful for fixing CVEs fast, dangerous as a permanent crutch. Prefer upstream fixes.\n","# Yarn Pro\n\nA practical guide to Yarn — primarily modern Yarn Berry (v2+): Plug'n'Play, workspaces, constraints, and the release workflow, plus notes for teams still on Yarn Classic (v1).\n\n## Overview\n\nYarn Berry rethought package management: **Plug'n'Play (PnP)** eliminates `node_modules` entirely (packages load from zip archives via a loader), **constraints** enforce workspace consistency with Prolog-like rules, and **releases** are checked into the repo (`yarn set version`) so everyone runs the identical Yarn. It's powerful but opinionated — editor SDKs and some tools need explicit setup for PnP.\n\nKnow which Yarn you have: `yarn --version` — v1.x is Classic (node_modules, still common), v2+ is Berry.\n\n## When to use\n\n- Monorepos wanting strong consistency guarantees (constraints) and fast installs.\n- Zero-install workflows (check in `.yarn\u002Fcache` for instant CI).\n- Teams hitting phantom-dependency or version-drift issues.\n- Migrating from Classic to Berry, or maintaining a Classic repo.\n\n## Core concepts\n\n- **Plug'n'Play.** No `node_modules`; `.pnp.cjs` maps packages to zip locations. Strict: undeclared deps fail at runtime. Editor support via `yarn dlx @yarnpkg\u002Fsdks`.\n- **Zero-installs.** Commit `.yarn\u002Fcache` (zips) → `yarn install` becomes nearly instant, CI needs no network. Costs repo size; worth it for many teams.\n- **Workspaces.** Like other managers, plus `yarn workspaces foreach` for running commands across packages with topological ordering.\n- **Constraints (`constraints.pro`).** Declarative rules: \"all workspaces must use the same version of react\", \"no workspace may depend on X\". `yarn constraints` checks; `yarn constraints --fix` repairs.\n- **`packageExtensions`.** Fix packages with missing peer deps declaratively in `.yarnrc.yml` instead of forking — but prefer upstream fixes long-term.\n- **Release workflow.** `yarn version check` \u002F `yarn version apply` manage deferred version bumps across workspaces; pairs with release plugins.\n- **Classic (v1).** `node_modules` + `yarn.lock`; workspaces exist but are thinner. Still fine; just lacks Berry's strictness tooling.\n\n## Practical workflow\n\n**1. Setup (Berry).**\n```bash\nyarn init -2                    # or: yarn set version stable in existing repo\necho 'nodeLinker: pnp' >> .yarnrc.yml   # or node-modules if PnP fights your tools\nyarn install\n```\n\n**2. Daily commands.**\n```bash\nyarn add react                  # add dep\nyarn add -D typescript          # devDep\nyarn up react                   # upgrade across workspaces\nyarn dedupe                     # reduce duplicates\nyarn why react                  # explain a dependency\nyarn workspaces foreach -R --topological-dev run build\nyarn constraints --fix          # enforce consistency rules\n```\n\n**3. `.yarnrc.yml` essentials.**\n```yaml\nnodeLinker: pnp\npackageExtensions:\n  \"some-lib@*\":\n    peerDependencies: { \"react\": \"*\" }\n```\n\n**4. Editor SDKs (PnP).**\n```bash\nyarn dlx @yarnpkg\u002Fsdks vscode vim  # generates editor SDKs so TS\u002Feslint resolve PnP\n```\nWithout this, TypeScript and ESLint can't find packages under PnP.\n\n**5. CI.**\n```bash\nyarn install --immutable   # fail if lockfile would change\n```\n\n## Common pitfalls\n\n- **PnP vs tooling.** Some tools assume `node_modules` exists. Options: `nodeLinker: node-modules` (pragmatic), or `packageExtensions` + SDKs. Don't suffer silently — pick the linker that fits your toolchain.\n- **Skipping editor SDKs.** Red squiggles everywhere under PnP = missing SDKs, not broken code. Run the SDK generator.\n- **Undeclared deps.** Same strictness lesson as pnpm: `Cannot find module` → declare the dependency properly.\n- **Zero-install repo bloat.** `.yarn\u002Fcache` can grow large; use `yarn cache clean --all` equivalents judiciously and consider `enableGlobalCache` for huge monorepos.\n- **Constraints ignored.** Writing `constraints.pro` but never running `yarn constraints` in CI = documentation, not enforcement. Gate CI on it.\n- **Classic\u002FBerry confusion.** Docs and Stack Overflow answers differ wildly by version. Always check which major version an answer targets.\n- **Forgetting `--immutable` in CI.** Without it, CI may update the lockfile instead of failing on drift — the opposite of what you want.\n- **Overriding with resolutions carelessly.** `resolutions` force versions globally — powerful for fixing CVEs fast, dangerous as a permanent crutch. Prefer upstream fixes.\n",{},"main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-yarn-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-yarn-pro",{"tool":37,"command":38},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill ams-yarn-pro",{"tool":40,"command":41},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill ams-yarn-pro","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-yarn-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",[],[]]