nx-workspace

Run and generate NX targets, configure project.json, and visualize dependency graphs. Use when you say: 'run affected tests', 'nx generate a library', 'configure project.json', or 'show dependency graph'.

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

NX Workspace

Docs: https://nx.dev/getting-started/intro. Project name → location mapping: project.instructions.md.

Never bypass NX

# FORBIDDEN — skips caching, parallelism, and dependency resolution:
npm test | npm run test | npm run lint | npm run build | npm run dev | npm start
npx jest | npx eslint | jest --coverage | eslint --fix

Always yarn nx run <project>:<target> for one project, yarn nx affected -t <target> for multi-project changes.

Requirements

Minimum coverage 95% for new components/functions. Reports land in reports/coverage/jest/.
Lint always with --fix. CSS/SCSS uses a separate target: yarn nx run <project>:lint-styles --fix.
yarn nx run <project>:test -u updates snapshots. yarn nx format --fix after any generation.

MCP tools — query, don't guess

Tool	When
`nx_workspace`	First call — architecture and current errors
`nx_docs`	Any config question; check before assuming
`nx_project_details`	One project's targets, config, dependencies
`nx_visualize_graph`	Project/task dependency graph
`nx_generators`	List generators (plugin + local)
`nx_generator_schema`	Required options and defaults for one generator
`nx_available_plugins`	Only when no existing generator fits
`nx_current_running_tasks_details`	Running/completed/failed tasks
`nx_current_running_task_output`	Terminal output for one task

Generation

Prefer local generators over plugin generators — they encode repo conventions. Manual file creation is a last resort after nx_generators and nx_available_plugins both come up empty. Read nx_generator_schema, then read the generator source for side effects (config edits, dep installs).

yarn nx generate <generator> <options> --dry-run --no-interactive   # preview
yarn nx generate <generator> <options> --no-interactive

--no-interactive is mandatory — prompts hang the run with no output.
Verify cwd first — generators derive file placement from it.

After generating: yarn nx format --fix, then lint/test/build the affected projects.

Running tasks

Check nx_current_running_tasks_details before starting anything. Continuous targets (serve, dev) are already running — read their output instead of re-running. To rerun, use yarn nx run <taskId> so NX context is preserved.

Repository: monkilabs/opencastle
Path: src/orchestrator/plugins/nx/SKILL.md
Commit: fa0c341

Last updated: 5 days ago
First committed: 5 months ago

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.