nx-workspace

Explains Nx workspace structure and inspects projects, targets, and dependencies via JSON output.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/sneat-co/sneat-apps --skill nx-workspace-sneat-co
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nx-workspace
Source: https://github.com/sneat-co/sneat-apps/tree/main/.cursor/skills/nx-workspace
Command: npx skills add https://github.com/sneat-co/sneat-apps --skill nx-workspace-sneat-co

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides read-only exploration of Nx workspaces to help understand project structure, targets, and dependencies, enabling faster debugging and configuration checks.

Core Features & Use Cases

  • Read-only exploration to identify projects, configurations, and dependencies within an Nx workspace.
  • Inspect project targets, tags, and implicit dependencies to plan changes or diagnose failures.
  • Quick guidance on using common Nx commands (e.g., nx show projects, nx show project, nx graph) and interpreting JSON outputs.

Quick Start

List all projects and their targets to get an overview of the workspace.

Frequently Asked Questions about nx-workspace

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I list all projects and targets in an Nx workspace?

To list all projects in an Nx workspace, use the nx show projects command to get a full overview, then inspect individual targets and configurations using nx show project with JSON output for reliable parsing.

What is the best way to inspect dependencies in an Nx monorepo?

Inspecting dependencies in an Nx monorepo is best done using the nx graph command, which visualizes project relationships, or by reading JSON outputs from nx show project to identify implicit dependencies and tags.

Why does my Nx command fail when reading partial project configurations?

Nx commands fail when reading partial configurations because the workspace relies on unified target definitions; always use JSON output from the Nx CLI to capture complete project configurations and avoid missing implicit dependencies.

How do I diagnose target configuration issues in a TypeScript Nx workspace?

Diagnose target configuration issues in a TypeScript Nx workspace by running nx show project with JSON output to audit the full structure, verifying that targets, tags, and dependencies are correctly mapped.

Can I use the Nx CLI to audit workspace structure without modifying files?

Yes, you can use the Nx CLI to audit workspace structure read-only, utilizing commands like nx show projects and nx graph to explore project configurations and dependencies without modifying any files.

When should I use nx graph instead of nx show project?

Use nx graph when you need a visual dependency map of the workspace, and use nx show project when you need detailed JSON output of a specific project's targets, tags, and configuration for debugging.