[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79DHH3KE26ABC6R4WJKRYPR":3,"skill-same:01M79DHH3KE26ABC6R4WJKRYPR":45},{"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":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M79DHH3KE26ABC6R4WJKRYPR","nx-developer",null,"General Nx workspace guidance. USE WHEN working in an Nx workspace, answering Nx architecture\u002Fconfiguration questions, choosing Nx commands, or deciding which Nx-specific skill\u002Fhelper to use. Routes to nx-workspace, nx-generate, nx-run-tasks, nx-plugins, nx-import, and nx-docs as appropriate.","araketski\u002Fpi-packages","araketski","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F211123241?v=4","01M79DGNR6TAW7QF1C5MKPYZER","Aliaksei Raketski","01M79DGNSAHG54WD4Q20WQ014N",0,"MIT","https:\u002F\u002Fgithub.com\u002Faraketski\u002Fpi-packages\u002Fblob\u002Fmain\u002Fpackages\u002Fnx-developer\u002Foverlays\u002Fnx-developer\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: nx-developer\ndescription: General Nx workspace guidance. USE WHEN working in an Nx workspace, answering Nx architecture\u002Fconfiguration questions, choosing Nx commands, or deciding which Nx-specific skill\u002Fhelper to use. Routes to nx-workspace, nx-generate, nx-run-tasks, nx-plugins, nx-import, and nx-docs as appropriate.\n---\n\n# Nx Developer\n\nUse this skill as the general router for Nx work. Load the more focused Nx skills when they match the task.\n\n## General Nx command rules\n\n- Prefer Nx commands (`nx run`, `nx run-many`, `nx affected`, `nx show`, `nx graph`) over calling underlying tools directly.\n- Prefix Nx commands with the workspace package manager, for example `pnpm nx ...`, `npm exec nx ...`, `yarn nx ...`, or `bunx nx ...`. Check the lockfile before choosing.\n- Use `--no-interactive` for generators and commands that could prompt.\n- Do not guess unfamiliar CLI flags. Use `\u003Cpackage-manager> nx \u003Ccommand> --help` first, then the `nx-docs` skill for deeper\u002Fcurrent documentation.\n\n## Workspace exploration routing\n\nUse the `nx-workspace` skill when answering questions about projects, targets, dependencies, or workspace architecture.\n\nUseful CLI commands:\n\n```bash\npnpm nx show projects --json\npnpm nx show project \u003Cproject-name> --json\npnpm nx graph --print\n```\n\nFor project-specific structure and inferred targets, prefer `pnpm nx show project \u003Cproject-name> --json` over reading `project.json` directly.\n\n## Generator\u002Fscaffolding routing\n\nUse the `nx-generate` skill before scaffolding projects, libraries, plugins, package structure, or other generated artifacts.\n\nKey rules:\n\n- Prefer local workspace generators over external plugin generators when both apply.\n- Check generator help with `pnpm nx g \u003Cgenerator> --help`.\n- Read the generator source when behavior or file placement matters.\n- Run a dry run first when supported.\n\n## Task running routing\n\nUse the `nx-run-tasks` skill when running build, test, lint, typecheck, serve, e2e, or other Nx targets.\n\nPrefer:\n\n```bash\npnpm nx run \u003Cproject>:\u003Ctarget>\npnpm nx run-many -t \u003Ctarget>\npnpm nx affected -t \u003Ctarget>\n```\n\n## Plugin and import routing\n\n- Use `nx-plugins` when discovering or adding Nx plugins.\n- Use `nx-import` when migrating\u002Fimporting existing projects into an Nx workspace.\n- Use `link-workspace-packages` when sibling workspace packages need dependency links or imports fail for workspace packages.\n\n## Documentation lookup routing\n\nUse the `nx-docs` skill when CLI help is not enough, especially for advanced configuration, migrations, plugin setup, release configuration, caching, affected behavior, or project graph behavior.\n\nThe local helper can be run from the `nx-docs` skill directory:\n\n```bash\nnode scripts\u002Fsearch-documentation.mjs \"targetDefaults nx.json\" --limit 4\n```\n\nOr from any directory with an absolute path to that script.\n\n## Plugin best practices\n\nWhen plugin-specific best practices are needed, check `node_modules\u002F@nx\u002F\u003Cplugin>\u002FPLUGIN.md` if it exists. Not every plugin ships this file.\n\n## Not included yet\n\nNx Cloud CI monitoring\u002Fself-healing automation is intentionally not included in this package yet. Use standard Nx\u002FNx Cloud CLI workflows or repository-specific guidance until script-based support is added.\n","# Nx Developer\n\nUse this skill as the general router for Nx work. Load the more focused Nx skills when they match the task.\n\n## General Nx command rules\n\n- Prefer Nx commands (`nx run`, `nx run-many`, `nx affected`, `nx show`, `nx graph`) over calling underlying tools directly.\n- Prefix Nx commands with the workspace package manager, for example `pnpm nx ...`, `npm exec nx ...`, `yarn nx ...`, or `bunx nx ...`. Check the lockfile before choosing.\n- Use `--no-interactive` for generators and commands that could prompt.\n- Do not guess unfamiliar CLI flags. Use `\u003Cpackage-manager> nx \u003Ccommand> --help` first, then the `nx-docs` skill for deeper\u002Fcurrent documentation.\n\n## Workspace exploration routing\n\nUse the `nx-workspace` skill when answering questions about projects, targets, dependencies, or workspace architecture.\n\nUseful CLI commands:\n\n```bash\npnpm nx show projects --json\npnpm nx show project \u003Cproject-name> --json\npnpm nx graph --print\n```\n\nFor project-specific structure and inferred targets, prefer `pnpm nx show project \u003Cproject-name> --json` over reading `project.json` directly.\n\n## Generator\u002Fscaffolding routing\n\nUse the `nx-generate` skill before scaffolding projects, libraries, plugins, package structure, or other generated artifacts.\n\nKey rules:\n\n- Prefer local workspace generators over external plugin generators when both apply.\n- Check generator help with `pnpm nx g \u003Cgenerator> --help`.\n- Read the generator source when behavior or file placement matters.\n- Run a dry run first when supported.\n\n## Task running routing\n\nUse the `nx-run-tasks` skill when running build, test, lint, typecheck, serve, e2e, or other Nx targets.\n\nPrefer:\n\n```bash\npnpm nx run \u003Cproject>:\u003Ctarget>\npnpm nx run-many -t \u003Ctarget>\npnpm nx affected -t \u003Ctarget>\n```\n\n## Plugin and import routing\n\n- Use `nx-plugins` when discovering or adding Nx plugins.\n- Use `nx-import` when migrating\u002Fimporting existing projects into an Nx workspace.\n- Use `link-workspace-packages` when sibling workspace packages need dependency links or imports fail for workspace packages.\n\n## Documentation lookup routing\n\nUse the `nx-docs` skill when CLI help is not enough, especially for advanced configuration, migrations, plugin setup, release configuration, caching, affected behavior, or project graph behavior.\n\nThe local helper can be run from the `nx-docs` skill directory:\n\n```bash\nnode scripts\u002Fsearch-documentation.mjs \"targetDefaults nx.json\" --limit 4\n```\n\nOr from any directory with an absolute path to that script.\n\n## Plugin best practices\n\nWhen plugin-specific best practices are needed, check `node_modules\u002F@nx\u002F\u003Cplugin>\u002FPLUGIN.md` if it exists. Not every plugin ships this file.\n\n## Not included yet\n\nNx Cloud CI monitoring\u002Fself-healing automation is intentionally not included in this package yet. Use standard Nx\u002FNx Cloud CLI workflows or repository-specific guidance until script-based support is added.\n",{"name":5,"description":7},"main","d9b1b8c72bf261be74d3229e766adb685b940aa4","packages\u002Fnx-developer\u002Foverlays\u002Fnx-developer",2,"https:\u002F\u002Fgithub.com\u002Faraketski\u002Fpi-packages","https:\u002F\u002Fgithub.com\u002Faraketski","2026-10-26 23:06:21",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add araketski\u002Fpi-packages --skill nx-developer",{"tool":37,"command":38},"bunx","bunx skills add araketski\u002Fpi-packages --skill nx-developer",{"tool":40,"command":41},"pnpm","pnpm dlx skills add araketski\u002Fpi-packages --skill nx-developer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Faraketski\u002Fpi-packages\u002Fblob\u002Fmain\u002Fpackages\u002Fnx-developer\u002Foverlays\u002Fnx-developer\u002FSKILL.md",true,[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":19},"01M79DJSQ1DE940XNF88TSA624","taiga-ui-docs","Use when implementing, debugging, reviewing, migrating, or looking up Angular Taiga UI components. Provides a bundled helper script equivalent to Taiga UI MCP docs tools for overview\u002Fimport guidance, section lists, exact component documentation\u002Fexamples, and migration guide content from llms-full.txt.","https:\u002F\u002Fgithub.com\u002Faraketski\u002Fpi-packages\u002Fblob\u002Fmain\u002Fpackages\u002Ftaiga-ui-docs\u002Fskills\u002Ftaiga-ui-docs\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M79DJN6T3K2HKXBNPCSN5T4Z","nx-workspace","Explore and understand Nx workspaces. USE WHEN answering questions about the workspace, projects, or tasks. ALSO USE WHEN an nx command fails or you need to check available targets\u002Fconfiguration before running a task. EXAMPLES: 'What projects are in this workspace?', 'How is project X configured?', 'What depends on library Y?', 'What targets can I run?', 'Cannot find configuration for task', 'debug nx task failure'.","https:\u002F\u002Fgithub.com\u002Faraketski\u002Fpi-packages\u002Fblob\u002Fmain\u002Fpackages\u002Fnx-developer\u002Fskills\u002Fnx-workspace\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M79DJJXEA2AKZBK49WFTVH43","nx-run-tasks","Helps with running tasks in an Nx workspace. USE WHEN the user wants to execute build, test, lint, serve, or run any other tasks defined in the workspace.","https:\u002F\u002Fgithub.com\u002Faraketski\u002Fpi-packages\u002Fblob\u002Fmain\u002Fpackages\u002Fnx-developer\u002Fskills\u002Fnx-run-tasks\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M79DJGSN8JRD741EB4HKNHXJ","nx-plugins","Find and add Nx plugins. USE WHEN user wants to discover available plugins, install a new plugin, or add support for a specific framework or technology to the workspace.","https:\u002F\u002Fgithub.com\u002Faraketski\u002Fpi-packages\u002Fblob\u002Fmain\u002Fpackages\u002Fnx-developer\u002Fskills\u002Fnx-plugins\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":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M79DJBPC0M2Q91P2C59JN88Q","nx-import","Import, merge, or combine repositories into an Nx workspace using nx import. USE WHEN the user asks to adopt Nx across repos, move projects into a monorepo, or bring code\u002Fhistory from another repository.","https:\u002F\u002Fgithub.com\u002Faraketski\u002Fpi-packages\u002Fblob\u002Fmain\u002Fpackages\u002Fnx-developer\u002Fskills\u002Fnx-import\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M79DJ78DFAHNRDKAK3ZHR7W6","nx-generate","Generate code using nx generators. INVOKE IMMEDIATELY when user mentions scaffolding, setup, structure, creating apps\u002Flibs, or setting up project structure. Trigger words - scaffold, setup, create a new app, create a new lib, project structure, generate, add a new project. ALWAYS use this BEFORE using the nx-docs skill or local Nx documentation helper or exploring - this skill handles discovery internally.","https:\u002F\u002Fgithub.com\u002Faraketski\u002Fpi-packages\u002Fblob\u002Fmain\u002Fpackages\u002Fnx-developer\u002Fskills\u002Fnx-generate\u002FSKILL.md",[],[]]