[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M76RM05AXCZ9AYK9ST030D42":3,"skill-same:01M76RM05AXCZ9AYK9ST030D42":59},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"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":13,"repositoryHtmlUrl":26,"repositoryHomepageUrl":6,"ownerHtmlUrl":27,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":28,"install":29,"resources":42},"01M76RM05AXCZ9AYK9ST030D42","monorepo-navigator",null,"Navigate, manage, and optimize monorepos. Covers Turborepo, Nx, pnpm workspaces, and Lerna. Cross-package impact analysis, selective builds\u002Ftests on affected packages, remote caching, dependency graph visualization, and structured multi-repo to monorepo migrations. Use when setting up a new monorepo, optimizing CI for a large workspace, debugging cross-package dependency issues, or planning a multi-repo consolidation.","msm47\u002FGitskil","msm47","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F288053465?v=4","01M754J0R2V3Q31DD8BV9CCDEN","01M754J0S8Q6Y7P0S3AYCY0YQ5",0,"MIT","https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fengineering\u002Fskills\u002Fmonorepo-navigator\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: \"monorepo-navigator\"\ndescription: \"Navigate, manage, and optimize monorepos. Covers Turborepo, Nx, pnpm workspaces, and Lerna. Cross-package impact analysis, selective builds\u002Ftests on affected packages, remote caching, dependency graph visualization, and structured multi-repo to monorepo migrations. Use when setting up a new monorepo, optimizing CI for a large workspace, debugging cross-package dependency issues, or planning a multi-repo consolidation.\"\n---\n\n# Monorepo Navigator\n\n**Tier:** POWERFUL  \n**Category:** Engineering  \n**Domain:** Monorepo Architecture \u002F Build Systems  \n\n---\n\n## Overview\n\nNavigate, manage, and optimize monorepos. Covers Turborepo, Nx, pnpm workspaces, and Lerna. Enables cross-package impact analysis, selective builds\u002Ftests on affected packages only, remote caching, dependency graph visualization, and structured migrations from multi-repo to monorepo. Includes Claude Code configuration for workspace-aware development.\n\n---\n\n## Core Capabilities\n\n- **Cross-package impact analysis** — determine which apps break when a shared package changes\n- **Selective commands** — run tests\u002Fbuilds only for affected packages (not everything)\n- **Dependency graph** — visualize package relationships as Mermaid diagrams\n- **Build optimization** — remote caching, incremental builds, parallel execution\n- **Migration** — step-by-step multi-repo → monorepo with zero history loss\n- **Publishing** — changesets for versioning, pre-release channels, npm publish workflows\n- **Claude Code config** — workspace-aware CLAUDE.md with per-package instructions\n\n---\n\n## When to Use\n\nUse when:\n- Multiple packages\u002Fapps share code (UI components, utils, types, API clients)\n- Build times are slow because everything rebuilds when anything changes\n- Migrating from multiple repos to a single repo\n- Need to publish packages to npm with coordinated versioning\n- Teams work across multiple packages and need unified tooling\n\nSkip when:\n- Single-app project with no shared packages\n- Team\u002Fproject boundaries are completely isolated (polyrepo is fine)\n- Shared code is minimal and copy-paste overhead is acceptable\n\n---\n\n## Tool Selection\n\n| Tool | Best For | Key Feature |\n|---|---|---|\n| **Turborepo** | JS\u002FTS monorepos, simple pipeline config | Best-in-class remote caching, minimal config |\n| **Nx** | Large enterprises, plugin ecosystem | Project graph, code generation, affected commands |\n| **pnpm workspaces** | Workspace protocol, disk efficiency | `workspace:*` for local package refs |\n| **Lerna** | npm publishing, versioning | Batch publishing, conventional commits |\n| **Changesets** | Modern versioning (preferred over Lerna) | Changelog generation, pre-release channels |\n\nMost modern setups: **pnpm workspaces + Turborepo + Changesets**\n\n---\n\n## Turborepo\n→ See references\u002Fmonorepo-tooling-reference.md for details\n\n## Workspace Analyzer\n\n```bash\npython3 scripts\u002Fmonorepo_analyzer.py \u002Fpath\u002Fto\u002Fmonorepo\npython3 scripts\u002Fmonorepo_analyzer.py \u002Fpath\u002Fto\u002Fmonorepo --json\n```\n\nAlso see `references\u002Fmonorepo-patterns.md` for common architecture and CI patterns.\n\n## Common Pitfalls\n\n| Pitfall | Fix |\n|---|---|\n| Running `turbo run build` without `--filter` on every PR | Always use `--filter=...[origin\u002Fmain]` in CI |\n| `workspace:*` refs cause publish failures | Use `pnpm changeset publish` — it replaces `workspace:*` with real versions automatically |\n| All packages rebuild when unrelated file changes | Tune `inputs` in turbo.json to exclude docs, config files from cache keys |\n| Shared tsconfig causes one package to break all type-checks | Use `extends` properly — each package extends root but overrides `rootDir` \u002F `outDir` |\n| git history lost during migration | Use `git filter-repo --to-subdirectory-filter` before merging — never move files manually |\n| Remote cache not working in CI | Check TURBO_TOKEN and TURBO_TEAM env vars; verify with `turbo run build --summarize` |\n| CLAUDE.md too generic — Claude modifies wrong package | Add explicit \"When working on X, only touch files in apps\u002FX\" rules per package CLAUDE.md |\n\n---\n\n## Best Practices\n\n1. **Root CLAUDE.md defines the map** — document every package, its purpose, and dependency rules\n2. **Per-package CLAUDE.md defines the rules** — what's allowed, what's forbidden, testing commands\n3. **Always scope commands with --filter** — running everything on every change defeats the purpose\n4. **Remote cache is not optional** — without it, monorepo CI is slower than multi-repo CI\n5. **Changesets over manual versioning** — never hand-edit package.json versions in a monorepo\n6. **Shared configs in root, extended in packages** — tsconfig.base.json, .eslintrc.base.js, jest.base.config.js\n7. **Impact analysis before merging shared package changes** — run affected check, communicate blast radius\n8. **Keep packages\u002Ftypes as pure TypeScript** — no runtime code, no dependencies, fast to build and type-check\n","# Monorepo Navigator\n\n**Tier:** POWERFUL  \n**Category:** Engineering  \n**Domain:** Monorepo Architecture \u002F Build Systems  \n\n---\n\n## Overview\n\nNavigate, manage, and optimize monorepos. Covers Turborepo, Nx, pnpm workspaces, and Lerna. Enables cross-package impact analysis, selective builds\u002Ftests on affected packages only, remote caching, dependency graph visualization, and structured migrations from multi-repo to monorepo. Includes Claude Code configuration for workspace-aware development.\n\n---\n\n## Core Capabilities\n\n- **Cross-package impact analysis** — determine which apps break when a shared package changes\n- **Selective commands** — run tests\u002Fbuilds only for affected packages (not everything)\n- **Dependency graph** — visualize package relationships as Mermaid diagrams\n- **Build optimization** — remote caching, incremental builds, parallel execution\n- **Migration** — step-by-step multi-repo → monorepo with zero history loss\n- **Publishing** — changesets for versioning, pre-release channels, npm publish workflows\n- **Claude Code config** — workspace-aware CLAUDE.md with per-package instructions\n\n---\n\n## When to Use\n\nUse when:\n- Multiple packages\u002Fapps share code (UI components, utils, types, API clients)\n- Build times are slow because everything rebuilds when anything changes\n- Migrating from multiple repos to a single repo\n- Need to publish packages to npm with coordinated versioning\n- Teams work across multiple packages and need unified tooling\n\nSkip when:\n- Single-app project with no shared packages\n- Team\u002Fproject boundaries are completely isolated (polyrepo is fine)\n- Shared code is minimal and copy-paste overhead is acceptable\n\n---\n\n## Tool Selection\n\n| Tool | Best For | Key Feature |\n|---|---|---|\n| **Turborepo** | JS\u002FTS monorepos, simple pipeline config | Best-in-class remote caching, minimal config |\n| **Nx** | Large enterprises, plugin ecosystem | Project graph, code generation, affected commands |\n| **pnpm workspaces** | Workspace protocol, disk efficiency | `workspace:*` for local package refs |\n| **Lerna** | npm publishing, versioning | Batch publishing, conventional commits |\n| **Changesets** | Modern versioning (preferred over Lerna) | Changelog generation, pre-release channels |\n\nMost modern setups: **pnpm workspaces + Turborepo + Changesets**\n\n---\n\n## Turborepo\n→ See references\u002Fmonorepo-tooling-reference.md for details\n\n## Workspace Analyzer\n\n```bash\npython3 scripts\u002Fmonorepo_analyzer.py \u002Fpath\u002Fto\u002Fmonorepo\npython3 scripts\u002Fmonorepo_analyzer.py \u002Fpath\u002Fto\u002Fmonorepo --json\n```\n\nAlso see `references\u002Fmonorepo-patterns.md` for common architecture and CI patterns.\n\n## Common Pitfalls\n\n| Pitfall | Fix |\n|---|---|\n| Running `turbo run build` without `--filter` on every PR | Always use `--filter=...[origin\u002Fmain]` in CI |\n| `workspace:*` refs cause publish failures | Use `pnpm changeset publish` — it replaces `workspace:*` with real versions automatically |\n| All packages rebuild when unrelated file changes | Tune `inputs` in turbo.json to exclude docs, config files from cache keys |\n| Shared tsconfig causes one package to break all type-checks | Use `extends` properly — each package extends root but overrides `rootDir` \u002F `outDir` |\n| git history lost during migration | Use `git filter-repo --to-subdirectory-filter` before merging — never move files manually |\n| Remote cache not working in CI | Check TURBO_TOKEN and TURBO_TEAM env vars; verify with `turbo run build --summarize` |\n| CLAUDE.md too generic — Claude modifies wrong package | Add explicit \"When working on X, only touch files in apps\u002FX\" rules per package CLAUDE.md |\n\n---\n\n## Best Practices\n\n1. **Root CLAUDE.md defines the map** — document every package, its purpose, and dependency rules\n2. **Per-package CLAUDE.md defines the rules** — what's allowed, what's forbidden, testing commands\n3. **Always scope commands with --filter** — running everything on every change defeats the purpose\n4. **Remote cache is not optional** — without it, monorepo CI is slower than multi-repo CI\n5. **Changesets over manual versioning** — never hand-edit package.json versions in a monorepo\n6. **Shared configs in root, extended in packages** — tsconfig.base.json, .eslintrc.base.js, jest.base.config.js\n7. **Impact analysis before merging shared package changes** — run affected check, communicate blast radius\n8. **Keep packages\u002Ftypes as pure TypeScript** — no runtime code, no dependencies, fast to build and type-check\n",{"name":5,"description":7},"main","56d41613d1ca1e2b0614a19c3816ec97a6159ec2","engineering\u002Fskills\u002Fmonorepo-navigator","https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil","https:\u002F\u002Fgithub.com\u002Fmsm47","2026-06-22 18:36:50",{"source":8,"skillName":5,"commands":30,"prompt":40,"zipAvailable":41},[31,34,37],{"tool":32,"command":33},"npx","npx skills add msm47\u002FGitskil --skill monorepo-navigator",{"tool":35,"command":36},"bunx","bunx skills add msm47\u002FGitskil --skill monorepo-navigator",{"tool":38,"command":39},"pnpm","pnpm dlx skills add msm47\u002FGitskil --skill monorepo-navigator","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fengineering\u002Fskills\u002Fmonorepo-navigator\u002FSKILL.md",true,[43,49,53],{"path":44,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":47,"sourceHtmlUrl":48},"references\u002Fmonorepo-patterns.md","REFERENCE","参考文档",1011,"https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fengineering\u002Fskills\u002Fmonorepo-navigator\u002Freferences\u002Fmonorepo-patterns.md",{"path":50,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":51,"sourceHtmlUrl":52},"references\u002Fmonorepo-tooling-reference.md",11999,"https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fengineering\u002Fskills\u002Fmonorepo-navigator\u002Freferences\u002Fmonorepo-tooling-reference.md",{"path":54,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":57,"sourceHtmlUrl":58},"scripts\u002Fmonorepo_analyzer.py","SCRIPT","脚本",5561,"https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fengineering\u002Fskills\u002Fmonorepo-navigator\u002Fscripts\u002Fmonorepo_analyzer.py",[60,67,74,81,88,95],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":18},"01M76S8VB9Q65XVZXC99QVF20M","syllabus","Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs — so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Triggers whenever a user uploads a syllabus, course outline, or curriculum document and wants supplementary readings. Also triggers on: 'syllabus reading list', 'find papers for my course', 'create a reading list from this syllabus', 'recent research for my class', 'supplementary readings', 'find journal articles for these topics', 'what recent papers cover this material', 'any new research on these course topics', 'update my syllabus with recent papers'. Even casual mentions when a syllabus is attached should trigger this skill.","https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fresearch\u002Fsyllabus\u002Fskills\u002Fsyllabus\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":18},"01M76S8K8X17M3CV7RENS6KA32","research","Default entry point for any research request — a hybrid router that classifies the question deterministically and either delegates to a specialist research skill (pulse for trends\u002Fsentiment, grants for NIH funding, litreview for academic literature, syllabus for course reading, patent for prior-art + IP landscape, dossier for entity research) or runs its own plan-decompose-multi-source-search-synthesize-cite fallback workflow when no specialist matches. Always surfaces the routing decision so users can override. Triggers — \"research [topic]\", \"look into [topic]\", \"what do we know about [topic]\", \"investigate [topic]\", \"find me information on [topic]\", \"do some research on [topic]\", \"I need to understand [topic]\", or any research request that doesn't obviously match a more-specific specialist skill. Output is a markdown briefing (default) or .docx document (on request) with full citations and an audit log.","https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fresearch\u002Fresearch\u002Fskills\u002Fresearch\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":18},"01M76S8AZCNS7Q5M4G1SBQ8HDV","pulse","Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X\u002FTwitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend\u002Fsentiment\u002Fproblems\u002Fopportunities\u002Fcomparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Triggers: 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]', or any variation requesting multi-source recency intelligence on a topic. Also use for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.","https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fresearch\u002Fpulse\u002Fskills\u002Fpulse\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":18},"01M76S7YVS0NHD51AFTZM5965R","patent","Patent prior-art and landscape intelligence skill — not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search \u002F freedom-to-operate \u002F competitive landscape \u002F acquisition diligence \u002F litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Triggers: 'prior art search for [invention]', 'patent search on [topic]', 'freedom to operate analysis', 'FTO for [product]', 'patent landscape for [field]', 'is [invention] novel', 'patents on [topic]', 'competitive patent analysis', 'prior art for litigation', 'patent diligence on [company]'. Produces search signal, not legal advice — always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope.","https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fresearch\u002Fpatent\u002Fskills\u002Fpatent\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":18},"01M76S7MQDZR49Y3DRXF394R2F","notebooklm","Browser automation skill for controlling Google's NotebookLM. Handles reading and querying notebooks, adding sources (URLs, text, files, YouTube links, synthesized content), generating Studio outputs (Audio Overview, infographics, slide decks, study guides, briefing docs, mind maps, timelines, FAQs), and creating new notebooks. Triggers on any phrase involving NotebookLM — 'open NotebookLM', 'check my [name] notebook', 'pull info from NotebookLM', 'ask my notebook about X', 'add [source] to NotebookLM', 'create an infographic in NotebookLM', 'use NotebookLM Studio', 'generate a slide deck from my notebook', or any variation where the goal involves NotebookLM. Requires browser automation environment — fails gracefully when unavailable.","https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fresearch\u002Fnotebooklm\u002Fskills\u002Fnotebooklm\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":18},"01M76S78K1ZJ092YYRKX0KBTYJ","litreview","Academic literature orientation skill that searches papers via Consensus, builds a strategic search plan using PICO (default) or SPIDER \u002F Decomposition \u002F hybrid as fallbacks, and synthesizes findings into a professionally formatted Word document (.docx) research guide. Grill-me intake (research question specificity + framework hint + tentative depth) before the recon search; a second forcing checkpoint after Phase 2 confirms framework + sub-areas + depth before searches consume budget. Configurable depth (5\u002F10\u002F20 queries) controls coverage vs. speed. Output is a 'launching pad' — not a finished review, but an orientation guide that lets a researcher dive in confidently. Triggers: 'litreview on [topic]', 'literature review on [topic]', 'I'm starting a literature review on X', 'I'm writing a paper on X', 'help me research X', 'I'm doing research on X', 'can you help me research X'. Do NOT trigger for single one-off paper searches where the user just wants a quick list — that's a plain Consensus search.","https:\u002F\u002Fgithub.com\u002Fmsm47\u002FGitskil\u002Fblob\u002Fmain\u002Fresearch\u002Flitreview\u002Fskills\u002Flitreview\u002FSKILL.md",[],[]]