<< All versions

Skill v1.0.1

currentAutomated scan100/100
monkilabs/opencastle/nx

+2 new

──Details
PublishedAugust 29, 2026 at 06:37 AM
Content Hashsha256:58fe958f1fd9876c...
Git SHAf297837635b1
Bump Typepatch
Compare with v1.0.0
──Files
Files (1 file, 2.7 KB)
SKILL.md2.7 KBactive
SKILL.md · 60 lines · 2.7 KB

version: "1.0.1" name: nx-workspace description: "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'."


<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the .opencastle/ directory instead. -->

NX Workspace

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

Never bypass NX

bash
# 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 npx nx run <project>:<target> for one project, npx 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: npx nx run <project>:lint-styles --fix.
  • npx nx run <project>:test -u updates snapshots. npx nx format --fix after any generation.

MCP tools — query, don't guess

ToolWhen
nx_workspaceFirst call — architecture and current errors
nx_docsAny config question; check before assuming
nx_project_detailsOne project's targets, config, dependencies
nx_visualize_graphProject/task dependency graph
nx_generatorsList generators (plugin + local)
nx_generator_schemaRequired options and defaults for one generator
nx_available_pluginsOnly when no existing generator fits
nx_current_running_tasks_detailsRunning/completed/failed tasks
nx_current_running_task_outputTerminal 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).

bash
npx nx generate <generator> <options> --dry-run --no-interactive # preview
npx 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: npx 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 npx nx run <taskId> so NX context is preserved.

← v1.0.0All versions