Explore and understand Nx workspaces. USE WHEN answering questions about the workspace, projects, or tasks. ALSO USE WHEN an nx command fails or you need to check available targets/configuration before running a task. EXAMPLES: 'What projects are in this workspace?', 'How is project X configured?',

Nx Workspace Exploration This skill provides read only exploration of Nx workspaces. Use it to understand workspace structure, project configuration, available targets, and dependencies. Keep in mind that you might have to prefix commands with npx / pnpx / yarn if nx isn't installed globally. Check the lockfile to determine the package manager in use. Listing Projects Use nx show projects to list projects in the workspace. The project filtering syntax ( p / projects ) works across many Nx commands including nx run many , nx release , nx show projects , and more. Filters support explicit names, glob patterns, tag references (e.g. tag:name ), directories, and negation (e.g. !project name ). Project Configuration Use nx show project <name json to get the full resolved configuration for a project. Important : Do NOT read project.json directly it only contains partial configuration. The nx show project json command returns the full resolved config including inferred targets from plugins. You can read the full project schema at node modules/nx/schemas/project schema.json to understand nx project configuration options. Target Information Targets define what tasks can be run on a project. Workspace Configuration Read nx.json directly for workspace level configuration. You can read the full project schema at node modules/nx/schemas/nx schema.json to understand nx project configuration options. Key nx.json sections: targetDefaults Default configuration applied to all targets of a given name namedInputs Reusable input definitions for caching plugins Nx plugins and their configuration ...and much more, read the schema or nx.json for details Affected Projects If the user is asking about affected projects, read the [affected projects reference](references/AFFECTED.md) for detailed commands and examples. Common Exploration Patterns "What's in this workspace?" "How do I build/test/lint project X?" "What depends on library Y?" Programmatic Answers When processing nx CLI results, use command line tools to compute the answer programmatically rather than counting or parsing output manually. Always use json flags to get structured output that can be processed with jq , grep , or other tools you have installed locally. Listing Projects Example output: Common operations: Project Details Example output: Common operations: Project Graph Example output: Common operations: Troubleshooting "Cannot find configuration for task X:target" "The workspace is out of sync"

nx-workspace