Install the "nx-monorepo" agent skill from https://github.com/giuseppe-trisciuoglio/developer-kit/tree/main/plugins/developer-kit-typescript/skills/nx-monorepo into .claude/skills/nx-monorepo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nx-monorepo", then confirm the skill loads.
Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
skills CLI
$ npx skills add giuseppe-trisciuoglio/developer-kit --skill nx-monorepo -a codex
Project install goes to .agents/skills/; add -g for ~/.codex/skills/.
Install the "nx-monorepo" agent skill from https://github.com/giuseppe-trisciuoglio/developer-kit/tree/main/plugins/developer-kit-typescript/skills/nx-monorepo into .agents/skills/nx-monorepo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nx-monorepo", then confirm the skill loads.
Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skills CLI
$ npx skills add giuseppe-trisciuoglio/developer-kit --skill nx-monorepo -a cursor
Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.
Install the "nx-monorepo" agent skill from https://github.com/giuseppe-trisciuoglio/developer-kit/tree/main/plugins/developer-kit-typescript/skills/nx-monorepo into .cursor/skills/nx-monorepo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nx-monorepo", then confirm the skill loads.
Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
skills CLI
$ npx skills add giuseppe-trisciuoglio/developer-kit --skill nx-monorepo -a gemini-cli
Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.
Install the "nx-monorepo" agent skill from https://github.com/giuseppe-trisciuoglio/developer-kit/tree/main/plugins/developer-kit-typescript/skills/nx-monorepo into .gemini/skills/nx-monorepo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nx-monorepo", then confirm the skill loads.
Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
skills CLI
$ npx skills add giuseppe-trisciuoglio/developer-kit --skill nx-monorepo -a github-copilot
Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.
Install the "nx-monorepo" agent skill from https://github.com/giuseppe-trisciuoglio/developer-kit/tree/main/plugins/developer-kit-typescript/skills/nx-monorepo into .github/skills/nx-monorepo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nx-monorepo", then confirm the skill loads.
GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skills CLI
$ npx skills add giuseppe-trisciuoglio/developer-kit --skill nx-monorepo -a opencode
OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
Install the "nx-monorepo" agent skill from https://github.com/giuseppe-trisciuoglio/developer-kit/tree/main/plugins/developer-kit-typescript/skills/nx-monorepo into .opencode/skills/nx-monorepo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nx-monorepo", then confirm the skill loads.
OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
Skill name
nx-monorepo
GitHub stars
357
Token cost
~2.3k tokens
SKILL.md length
749 words
Files
8 (incl. references)
Skills in repo
115
Repo updated
First seen
Licence
MIT
At a glance
Provides comprehensive Nx monorepo management guidance for TypeScript/JavaScript projects.
Works in 3 steps: Create a new workspace with interactive… → Initialize Nx in an existing project → Create with specific preset…
Creating Nx workspaces
SKILL.md covers Overview, When to Use, Instructions and Examples, plus 3 more sections
Calls nx and npx
What it does
Nx Monorepo is an agent skill from giuseppe-trisciuoglio/developer-kit. Provides comprehensive Nx monorepo management guidance for TypeScript/JavaScript projects. Use when creating Nx workspaces, generating apps/libraries/components, running affected commands, setting up CI/CD, configuring Module Federation, or implementing NestJS backends within Nx
Its SKILL.md is about 2.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 8 other files, including reference files (for example `references/advanced.md`, `references/basics.md` and `references/ci-cd.md`).
It sits in DevOps & Cloud, covering CI/CD and Monorepo tooling. It works with Nx, NestJS, TypeScript and JavaScript. The repository describes itself as: Modular plugin marketplace for Claude Code and agentic CLIs, with validated, spec-driven skills, agents, commands, and workflows for Java, TypeScript, Python, PHP, AWS, and AI. The licence is MIT.
When your agent uses it
Creating Nx workspaces
Generating apps/libraries/components
Running affected commands
Setting up CI/CD
Example prompts
“Use the nx-monorepo skill to provide comprehensive Nx monorepo management guidance for TypeScript/JavaScript projects”
3 steps, taken from the first numbered list in SKILL.md.
1Create a new workspace with interactive setup
2Initialize Nx in an existing project
3Create with specific preset (non-interactive)
What it can do on your machine
Read from SKILL.md and the folder at commit fe73fb3. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
Read
Write
Edit
Bash
Glob
Grep
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
nx
npx
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npx, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Nx Monorepo loads about 2.3k tokens when it runs, and up to ~14k if it reads all its reference files. Until then it costs about 73 tokens; SKILL.md has 749 words of instructions outside code blocks.
Always· name and description, kept in context so the agent knows when to use it
~73
When it runs· the whole SKILL.md, loaded when a task matches
~2.3k
With references· SKILL.md plus every file in references/, read only if the agent opens them
~14k
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
Download SKILL.mdSave it as .claude/skills/nx-monorepo/SKILL.md (or your agent's skills folder). This skill also uses 7 other files; get the full folder from GitHub.
name
nx-monorepo
description
Provides comprehensive Nx monorepo management guidance for TypeScript/JavaScript projects. Use when creating Nx workspaces, generating apps/libraries/components, running affected commands, setting up CI/CD, configuring Module Federation, or implementing NestJS backends within Nx
allowed-tools
Read, Write, Edit, Bash, Glob, Grep
Nx Monorepo
Overview
Provides guidance for Nx monorepo management in TypeScript/JavaScript projects. Covers workspace creation, project generation, task execution, caching strategies, Module Federation, and CI/CD integration.
When to Use
Use this skill when:
Creating a new Nx workspace or initializing Nx in an existing project
Generating applications, libraries, or components with Nx generators
Running affected commands or executing tasks across multiple projects
Setting up CI/CD pipelines for Nx projects (GitHub Actions, CircleCI, etc.)
Configuring Module Federation with React or Next.js
Implementing NestJS backend applications within Nx
Managing TypeScript package libraries with buildable and publishable libs
Setting up remote caching or Nx Cloud
Optimizing monorepo build times and caching strategies
Debugging dependency graph issues or circular dependencies
Verify:nx show projects lists the new workspace projects
Project Generation
Generate a React application:
bash
nx g @nx/react:app my-app
Generate a library:
bash
# React library
nx g @nx/react:lib my-lib
# TypeScript library
nx g @nx/js:lib my-util
Verify:nx show projects lists the new lib
Generate a component in lib:
bash
nx g @nx/react:component my-comp --project=my-lib
Generate NestJS backend:
bash
nx g @nx/nest:app my-api
Verify:nx show projects lists my-api and nx run my-api:build succeeds
Task Execution
Run tasks for affected projects only:
bash
nx affected -t lint test build
Run tasks across all projects:
bash
# Build all projects
nx run-many -t build
# Test specific projects
nx run-many -t test -p=my-app,my-lib
# Test by pattern
nx run-many -t test --projects=*-app
Run specific target on single project:
bash
nx run my-app:build
Visualize dependency graph:
bash
nx graph
Project Configuration
Each project has a project.json defining targets, executor, and configurations:
Verify:cd my-workspace && nx show projects lists the created app
Expected Result: Workspace created with:
apps/ directory with React app
libs/ directory for shared libraries
nx.json with cache configuration
CI/CD workflow files ready
Example 2: Run Tests for Changed Projects
Input: "Run tests only for projects affected by recent changes"
Command:
bash
nx affected -t test --base=main~1 --head=main
Expected Result: Only tests for projects affected by changes between commits are executed, leveraging cached results from previous runs.
Example 3: Generate and Build a Shared Library
Input: "Create a shared UI library and use it in the app"
Steps:
bash
# Generate library
nx g @nx/react:lib shared-ui
# Generate component in library
nx g @nx/react:component button --project=shared-ui
# Import in app (tsconfig paths auto-configured)
import { Button } from '@my-workspace/shared-ui'
Verify:nx run shared-ui:build completes successfully and nx graph shows the dependency link to your app
Expected Result: Buildable library at libs/shared-ui with proper TypeScript path mapping configured.
Show full SKILL.md (318 more words)Show less
Example 4: Set Up Module Federation
Input: "Configure Module Federation for micro-frontends"
Steps:
bash
# Create host app
nx g @nx/react:host dashboard
# Add remote to host
nx g @nx/react:remote product-catalog --host=dashboard
# Start dev servers
nx run dashboard:serve
nx run product-catalog:serve
Verify: Both servers start without errors and nx graph shows dashboard → product-catalog remote connection
Expected Result: Two separate applications running where product-catalog loads dynamically into dashboard at runtime.
Example 5: Debug Build Dependencies
Input: "Why is my app rebuilding when unrelated lib changes?"
Diagnosis:
bash
# Show project graph
nx graph --focused=my-app
# Check implicit dependencies
nx show project my-app --json | grep implicitDependencies
Solution: Add explicit dependency configuration or use namedInputs in nx.json to exclude certain files from triggering builds.
Verify Fix Worked: Make a change to the unrelated lib, run nx affected -t build — my-app should not appear in the affected projects list.
Best Practices
Always use nx affected in CI to only test/build changed projects
Organize libs by domain/business capability, not by technical layer
Use tags consistently (type:app|lib, scope:frontend|backend|shared)
Prevent circular dependencies by configuring workspaceLayout boundaries in nx.json
Enable remote caching with Nx Cloud for team productivity
Keep project.json simple - use defaults from nx.json when possible
Leverage generators instead of manual file creation for consistency
Configure namedInputs to exclude test files from production cache keys
Use Module Federation for independent deployment of micro-frontends
Keep workspace generators in tools/ for project-specific scaffolding
Constraints and Warnings
Node.js 18.10+ is required for Nx 17+
Windows users: Use WSL or Git Bash for best experience
First-time setup may take longer due to package installation
Large monorepos (50+ projects) should use distributed task execution
Module Federation requires webpack 5+ and specific Nx configuration
Some generators require additional plugins to be installed first
Cache location: Default ~/.nx/cache can grow large; configure cacheDirectory in nx.json if needed
Circular dependencies will cause build failures; use nx graph to visualize
Preset migration: Converting between Integrated/Standalone/Package-based requires manual effort
Reference Files
For detailed guidance on specific topics, consult:
Nx Monorepo next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
Nx Monorepo compared with similar skills
Skill
Stars
Used in
Tokens
Auto-check
Licence
Repo updated
Nx Monorepo this skillgiuseppe-trisciuoglio/developer-kit
Safely plan and execute dependency maintenance for JavaScript/TypeScript (npm, pnpm) and GitHub Actions, including npm lockfiles, pnpm workspaces, catalogs, overrides, SHA-pinned action versions…
Guides design of modular-monolith platforms with DDD, flat-by-aggregate modules, anti-corruption layers, outbox events and resilience, plus an architecture document with SVG diagrams.
Provides patterns to configure Spring Boot Actuator for production-grade monitoring, health probes, secured management endpoints, and Micrometer metrics across JVM services.
Provides JWT authentication and authorization patterns for Spring Boot 3.5.x covering token generation with JJWT, Bearer/cookie authentication, database/OAuth2 integration, and RBAC/permission-based…
Run `npx skills add giuseppe-trisciuoglio/developer-kit --skill nx-monorepo -a claude-code`. Or copy the skill folder (plugins/developer-kit-typescript/skills/nx-monorepo in giuseppe-trisciuoglio/developer-kit) into .claude/skills/nx-monorepo in your project. Claude Code loads it when a task matches its description.
How do I install Nx Monorepo in Codex?
Run `npx skills add giuseppe-trisciuoglio/developer-kit --skill nx-monorepo -a codex`. Or copy the skill folder (plugins/developer-kit-typescript/skills/nx-monorepo in giuseppe-trisciuoglio/developer-kit) into .agents/skills/nx-monorepo in your project. Codex loads it when a task matches its description.
Can I use Nx Monorepo in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add giuseppe-trisciuoglio/developer-kit --skill nx-monorepo -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/nx-monorepo, .gemini/skills/nx-monorepo, .github/skills/nx-monorepo and .opencode/skills/nx-monorepo in your project.
What does Nx Monorepo need to run?
Going by SKILL.md and its folder, Nx Monorepo needs the command-line tools its instructions call (nx and npx). Our summary lists: Node.js. Its frontmatter pre-approves these tools: Read, Write, Edit, Bash, Glob, Grep.
Does Nx Monorepo access the network?
SKILL.md contains no URLs. Its commands use npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Nx Monorepo safe to install?
Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Nx Monorepo use?
Nx Monorepo is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Nx Monorepo use?
About 2.3k tokens (SKILL.md is roughly 9.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 11k tokens, read only when the agent opens those files.
What are the alternatives to Nx Monorepo?
Skills that share tags, products or a category with Nx Monorepo: Linea Dependency Maintenance (Consensys-Incorporated/linea-attestation-registry, 177 stars), Pnpm Engine (teambit/bit, 18k stars), Typescript Tooling Migration (Arize-ai/phoenix, 12k stars) and Novu Framework Integration (novuhq/novu, 40k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Nx Monorepo?
giuseppe-trisciuoglio (a GitHub user) maintains it in giuseppe-trisciuoglio/developer-kit, which has 357 GitHub stars. The repository holds 115 skills in this directory. The repository was last updated on September 10, 2026.