[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75MPJHA1DY49ZFRR8MHH36R":3,"skill-same:01M75MPJHA1DY49ZFRR8MHH36R":47},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M75MPJHA1DY49ZFRR8MHH36R","link-workspace-packages",null,"Link workspace packages in monorepos (npm, yarn, pnpm, bun). USE WHEN: (1) you just created or generated new packages and need to wire up their dependencies, (2) user imports from a sibling package and needs to add it as a dependency, (3) you get resolution errors for workspace packages (@org\u002F*) like \"cannot find module\", \"failed to resolve import\", \"TS2307\", or \"cannot resolve\". DO NOT patch around with tsconfig paths or manual package.json edits - use the package manager's workspace commands to fix actual linking.","whimzyLive\u002Fnightshift-ai","whimzyLive","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F22066605?v=4","01M75MMH22XX6R3NTAFHD7HEN7","Rushi Patel","01M75MMH32DHVVC61XRSHWVEV2",3,"MIT","https:\u002F\u002Fgithub.com\u002FwhimzyLive\u002Fnightshift-ai\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Flink-workspace-packages\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: link-workspace-packages\ndescription: 'Link workspace packages in monorepos (npm, yarn, pnpm, bun). USE WHEN: (1) you just created or generated new packages and need to wire up their dependencies, (2) user imports from a sibling package and needs to add it as a dependency, (3) you get resolution errors for workspace packages (@org\u002F*) like \"cannot find module\", \"failed to resolve import\", \"TS2307\", or \"cannot resolve\". DO NOT patch around with tsconfig paths or manual package.json edits - use the package manager''s workspace commands to fix actual linking.'\n---\n\n# Link Workspace Packages\n\nAdd dependencies between packages in a monorepo. All package managers support workspaces but with different syntax.\n\n## Detect Package Manager\n\nCheck whether there's a `packageManager` field in the root-level `package.json`.\n\nAlternatively check lockfile in repo root:\n\n- `pnpm-lock.yaml` → pnpm\n- `yarn.lock` → yarn\n- `bun.lock` \u002F `bun.lockb` → bun\n- `package-lock.json` → npm\n\n## Workflow\n\n1. Identify consumer package (the one importing)\n2. Identify provider package(s) (being imported)\n3. Add dependency using package manager's workspace syntax\n4. Verify symlinks created in consumer's `node_modules\u002F`\n\n---\n\n## pnpm\n\nUses `workspace:` protocol - symlinks only created when explicitly declared.\n\n```bash\n# From consumer directory\npnpm add @org\u002Fui --workspace\n\n# Or with --filter from anywhere\npnpm add @org\u002Fui --filter @org\u002Fapp --workspace\n```\n\nResult in `package.json`:\n\n```json\n{ \"dependencies\": { \"@org\u002Fui\": \"workspace:*\" } }\n```\n\n---\n\n## yarn (v2+\u002Fberry)\n\nAlso uses `workspace:` protocol.\n\n```bash\nyarn workspace @org\u002Fapp add @org\u002Fui\n```\n\nResult in `package.json`:\n\n```json\n{ \"dependencies\": { \"@org\u002Fui\": \"workspace:^\" } }\n```\n\n---\n\n## npm\n\nNo `workspace:` protocol. npm auto-symlinks workspace packages.\n\n```bash\nnpm install @org\u002Fui --workspace @org\u002Fapp\n```\n\nResult in `package.json`:\n\n```json\n{ \"dependencies\": { \"@org\u002Fui\": \"*\" } }\n```\n\nnpm resolves to local workspace automatically during install.\n\n---\n\n## bun\n\nSupports `workspace:` protocol (pnpm-compatible).\n\n```bash\ncd packages\u002Fapp && bun add @org\u002Fui\n```\n\nResult in `package.json`:\n\n```json\n{ \"dependencies\": { \"@org\u002Fui\": \"workspace:*\" } }\n```\n\n---\n\n## Examples\n\n**Example 1: pnpm - link ui lib to app**\n\n```bash\npnpm add @org\u002Fui --filter @org\u002Fapp --workspace\n```\n\n**Example 2: npm - link multiple packages**\n\n```bash\nnpm install @org\u002Fdata-access @org\u002Fui --workspace @org\u002Fdashboard\n```\n\n**Example 3: Debug \"Cannot find module\"**\n\n1. Check if dependency is declared in consumer's `package.json`\n2. If not, add it using appropriate command above\n3. Run install (`pnpm install`, `npm install`, etc.)\n\n## Notes\n\n- Symlinks appear in `\u003Cconsumer>\u002Fnode_modules\u002F@org\u002F\u003Cpackage>`\n- **Hoisting differs by manager:**\n  - npm\u002Fbun: hoist shared deps to root `node_modules`\n  - pnpm: no hoisting (strict isolation, prevents phantom deps)\n  - yarn berry: uses Plug'n'Play by default (no `node_modules`)\n- Root `package.json` should have `\"private\": true` to prevent accidental publish\n","# Link Workspace Packages\n\nAdd dependencies between packages in a monorepo. All package managers support workspaces but with different syntax.\n\n## Detect Package Manager\n\nCheck whether there's a `packageManager` field in the root-level `package.json`.\n\nAlternatively check lockfile in repo root:\n\n- `pnpm-lock.yaml` → pnpm\n- `yarn.lock` → yarn\n- `bun.lock` \u002F `bun.lockb` → bun\n- `package-lock.json` → npm\n\n## Workflow\n\n1. Identify consumer package (the one importing)\n2. Identify provider package(s) (being imported)\n3. Add dependency using package manager's workspace syntax\n4. Verify symlinks created in consumer's `node_modules\u002F`\n\n---\n\n## pnpm\n\nUses `workspace:` protocol - symlinks only created when explicitly declared.\n\n```bash\n# From consumer directory\npnpm add @org\u002Fui --workspace\n\n# Or with --filter from anywhere\npnpm add @org\u002Fui --filter @org\u002Fapp --workspace\n```\n\nResult in `package.json`:\n\n```json\n{ \"dependencies\": { \"@org\u002Fui\": \"workspace:*\" } }\n```\n\n---\n\n## yarn (v2+\u002Fberry)\n\nAlso uses `workspace:` protocol.\n\n```bash\nyarn workspace @org\u002Fapp add @org\u002Fui\n```\n\nResult in `package.json`:\n\n```json\n{ \"dependencies\": { \"@org\u002Fui\": \"workspace:^\" } }\n```\n\n---\n\n## npm\n\nNo `workspace:` protocol. npm auto-symlinks workspace packages.\n\n```bash\nnpm install @org\u002Fui --workspace @org\u002Fapp\n```\n\nResult in `package.json`:\n\n```json\n{ \"dependencies\": { \"@org\u002Fui\": \"*\" } }\n```\n\nnpm resolves to local workspace automatically during install.\n\n---\n\n## bun\n\nSupports `workspace:` protocol (pnpm-compatible).\n\n```bash\ncd packages\u002Fapp && bun add @org\u002Fui\n```\n\nResult in `package.json`:\n\n```json\n{ \"dependencies\": { \"@org\u002Fui\": \"workspace:*\" } }\n```\n\n---\n\n## Examples\n\n**Example 1: pnpm - link ui lib to app**\n\n```bash\npnpm add @org\u002Fui --filter @org\u002Fapp --workspace\n```\n\n**Example 2: npm - link multiple packages**\n\n```bash\nnpm install @org\u002Fdata-access @org\u002Fui --workspace @org\u002Fdashboard\n```\n\n**Example 3: Debug \"Cannot find module\"**\n\n1. Check if dependency is declared in consumer's `package.json`\n2. If not, add it using appropriate command above\n3. Run install (`pnpm install`, `npm install`, etc.)\n\n## Notes\n\n- Symlinks appear in `\u003Cconsumer>\u002Fnode_modules\u002F@org\u002F\u003Cpackage>`\n- **Hoisting differs by manager:**\n  - npm\u002Fbun: hoist shared deps to root `node_modules`\n  - pnpm: no hoisting (strict isolation, prevents phantom deps)\n  - yarn berry: uses Plug'n'Play by default (no `node_modules`)\n- Root `package.json` should have `\"private\": true` to prevent accidental publish\n",{"name":5,"description":7},"main","7d4ebd573a4218d5e92eced411b259f34e9203fe",".opencode\u002Fskills\u002Flink-workspace-packages",0,"https:\u002F\u002Fgithub.com\u002FwhimzyLive\u002Fnightshift-ai","https:\u002F\u002Fwithnightshift.com\u002F","https:\u002F\u002Fgithub.com\u002FwhimzyLive","Creator of @typedorm","2026-11-14 22:45:42",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add whimzyLive\u002Fnightshift-ai --skill link-workspace-packages",{"tool":39,"command":40},"bunx","bunx skills add whimzyLive\u002Fnightshift-ai --skill link-workspace-packages",{"tool":42,"command":43},"pnpm","pnpm dlx skills add whimzyLive\u002Fnightshift-ai --skill link-workspace-packages","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FwhimzyLive\u002Fnightshift-ai\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Flink-workspace-packages\u002FSKILL.md",true,[],[48,56,63,70,77,84],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":55},"01M7BCEWYHDS1FWAJ6G4CD9P54","designing-in-patterns","Use when designing, planning or auditing UI against a component library — naming surfaces with the repo's pattern vocabulary, deciding reuse versus extend versus new, exploring compositions, or writing the reuse table (component-plan.md, a spec's `## Reuse`, a UI audit). Carries the design method; the repo's own vocabulary, bundle and board rules come from project-context and the designer override.","https:\u002F\u002Fgithub.com\u002FwhimzyLive\u002Fnightshift-ai\u002Fblob\u002Fmain\u002Fplugins\u002Fsdlc\u002Fskills\u002Fdesigning-in-patterns\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M75MVN6GACAC87SV9RBPBMKH","typeorm","Use when defining TypeORM entities, writing migrations, or building repository\u002Fquery-builder code in TypeScript. Covers entity and relation decorators, the Data Mapper pattern, migrations, the query builder, transactions, and multi-database configuration.","https:\u002F\u002Fgithub.com\u002FwhimzyLive\u002Fnightshift-ai\u002Fblob\u002Fmain\u002Fskills\u002Ftypeorm\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M75MTEZV8SAZNS20YDSB7KG2","hono-api","Use when building or extending REST APIs with Hono + @hono\u002Fzod-openapi. Covers schema-first route declaration with createRoute, feature-grouped composable routers, a class-based service layer behind interfaces, the strategy pattern for multi-event webhooks, typed request validation, and auto-generated OpenAPI docs.","https:\u002F\u002Fgithub.com\u002FwhimzyLive\u002Fnightshift-ai\u002Fblob\u002Fmain\u002Fskills\u002Fhono-api\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M75MTB91SB6HPB3ZRT20F950","electrodb","Use when defining DynamoDB entities, modeling indexes, or writing queries\u002Fmutations with the ElectroDB ORM. Covers entity schema, access patterns, CRUD operations, update expressions, and single-table design patterns.","https:\u002F\u002Fgithub.com\u002FwhimzyLive\u002Fnightshift-ai\u002Fblob\u002Fmain\u002Fskills\u002Felectrodb\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M75MT7KT9A3XYX38TX5MY6MA","atomic-design","Use when structuring or decomposing any frontend UI into reusable components, regardless of framework. Applies Brad Frost's atomic design methodology — atoms, molecules, organisms, templates, and pages — to guide consistent component hierarchy, naming, and composition decisions.","https:\u002F\u002Fgithub.com\u002FwhimzyLive\u002Fnightshift-ai\u002Fblob\u002Fmain\u002Fskills\u002Fatomic-design\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M75MSTQ54EY0K29PKBF212K1","writing-docs","Use when writing, restructuring, or reviewing any prose documentation — a tutorial, how-to guide, reference page, or explanation\u002Fconceptual doc — for a public docs site (e.g. Mintlify MDX, docs\u002F, README material), a getting-started guide, an API\u002FCLI reference page, or a \"why we built it this way\" conceptual page. Applies the Diátaxis framework (see https:\u002F\u002Fdiataxis.fr\u002F) — every document belongs to exactly one of the four quadrants (tutorial \u002F how-to guide \u002F reference \u002F explanation), and mixing quadrants inside one document is the single most common documentation failure. Covers the four-quadrant compass for picking the right form, per-quadrant structure templates, an anti-pattern list for quadrant drift, and generic voice\u002Fcraft rules — repo-specific voice and target output format (e.g. Mintlify MDX) are resolved from the repo's docs-manifest (falling back to project-context), never hardcoded here.","https:\u002F\u002Fgithub.com\u002FwhimzyLive\u002Fnightshift-ai\u002Fblob\u002Fmain\u002Fplugins\u002Fsdlc\u002Fskills\u002Fwriting-docs\u002FSKILL.md",[],[]]