nx
Nx workspace configuration, generators, and affected commands.
npx skills add a5c-ai/babysitter --skill nx --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Nx Skill Expert assistance for Nx monorepo management. ## Capabilities - Configure Nx workspaces - Create custom generators - Use affected commands - Set up caching - Define project boundaries ## Configuration ```json // nx.json { "targetDefaults": { "build": { "dependsOn": ["^build"], "cache": true }, "test": { "cache": true } }, "affected": { "defaultBase": "main" } } ``` ## Commands ```bash # Run affected nx affected:build nx affected:test # Graph nx graph # Generate nx generate @nx/react:component Button ``` ## Target Processes - monorepo-management - enterprise-architecture - code-generation
- Capabilities
- Configuration
- Commands
- Target Processes
Run affected nx affected:build nx affected:test Graph nx graph Generate nx generate @nx/react:component Button
What does the nx skill do?
Nx workspace configuration, generators, and affected commands.
How do I install it?
Run `npx skills add a5c-ai/babysitter --skill nx --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From a5c-ai/babysitter, a repository with 1,642 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.