nx-workspace
Skill1.7k starsChanged 9 days agoMITView on GitHub
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?', 'What depends on library Y?', 'What targets can I run?', 'Cannot find configuration for task', 'debug nx task failure'.
18 other projects use a version of this, 8 of them edited.
Trending
Less talk lately.about the whole repository
Most recently taken up by
- getlarge/themoltnetedited, first seen Nov 3, 2026
- code-dimension/code-dimension-skillsword for word, first seen Oct 17, 2026
- nrwl/nx-consoleedited, first seen Oct 8, 2026
- ever-co/ever-teamsedited, first seen Oct 8, 2026
- dotCMS/coreword for word, first seen Oct 8, 2026
- epam/ai-dial-chatword for word, first seen Oct 8, 2026
Who's talking about daveyplate/better-auth-ui
- AmanVarshney01/create-better-t-stack“Feature request: better-auth-ui”GitHub · Jun 13, 2025 · 8 reactions
- better-auth-ui/better-auth-ui“providers-card not showing linked providers correctly”GitHub · Sep 15, 2025 · 2 reactions
- better-auth-ui/better-auth-ui“[Feature request] Show Gravatar images as fallback only if user avatar is not available”GitHub · Sep 30, 2025 · 1 reactions
- better-auth/better-auth“Add new hook useActiveMemberRole on the authClient”GitHub · Sep 2, 2025 · 1 reactions
- gustavovalverde/zentity“chore(deps): bump the prod-dependencies group across 1 directory with 69 updates”GitHub · Oct 19, 2026
The biggest 5 of 50 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 50
Talked about on GitHub (50 times).
On GitHub · 50
- Jun 13, 2025Feature request: better-auth-ui — AmanVarshney01/create-better-t-stack8 reactions · 3 comments
- Sep 15, 2025providers-card not showing linked providers correctly — better-auth-ui/better-auth-ui2 reactions · 6 comments
- Sep 30, 2025[Feature request] Show Gravatar images as fallback only if user avatar is not available — better-auth-ui/better-auth-ui1 reaction · 1 comment
- Sep 2, 2025Add new hook useActiveMemberRole on the authClient — better-auth/better-auth1 reaction · 2 comments
- Oct 19, 2026chore(deps): bump the prod-dependencies group across 1 directory with 69 updates — gustavovalverde/zentity0 reactions · 2 comments
45 more on GitHub
- Oct 13, 2026chore(deps): bump the prod-dependencies group across 1 directory with 68 updates — gustavovalverde/zentity0 reactions · 2 comments
- Oct 5, 2026chore(deps): bump the prod-dependencies group across 1 directory with 59 updates — gustavovalverde/zentity0 reactions · 2 comments
- Sep 29, 2026chore(deps): bump the prod-dependencies group across 1 directory with 58 updates — gustavovalverde/zentity0 reactions · 2 comments
- Aug 25, 2026build(deps): bump the production-dependencies group with 2 updates — moira-mcp/moira0 reactions
- Aug 25, 2026build(deps): bump the production-dependencies group with 3 updates — moira-mcp/moira0 reactions · 2 comments
- Aug 25, 2026build(deps): bump the production-dependencies group with 4 updates — moira-mcp/moira0 reactions · 2 comments
- Aug 25, 2026build(deps): bump the production-dependencies group with 3 updates — moira-mcp/moira0 reactions · 2 comments
- Aug 24, 2026build(deps): bump the production-dependencies group across 1 directory with 35 updates — moira-mcp/moira0 reactions · 2 comments
- Aug 24, 2026build(deps): bump the production-dependencies group with 59 updates — moira-mcp/moira0 reactions · 1 comment
- Aug 18, 2026chore(deps): bump @daveyplate/better-auth-ui from 3.2.0 to 3.4.0 — lolimmlost/app-map-appahouse0 reactions · 1 comment
- Jun 15, 2026chore(deps): bump the prod-dependencies group across 1 directory with 49 updates — gustavovalverde/zentity0 reactions · 2 comments
- Jun 8, 2026chore(deps): bump the prod-dependencies group across 1 directory with 36 updates — gustavovalverde/zentity0 reactions · 2 comments
- Jun 3, 2026chore(deps): bump the prod-dependencies group across 1 directory with 34 updates — gustavovalverde/zentity0 reactions · 2 comments
- Jun 3, 2026chore(deps): bump the prod-dependencies group across 1 directory with 49 updates — gustavovalverde/zentity0 reactions · 2 comments
- May 25, 2026chore(deps): bump the prod-dependencies group across 1 directory with 46 updates — gustavovalverde/zentity0 reactions · 2 comments
- May 19, 2026chore(deps): bump the prod-dependencies group across 1 directory with 44 updates — gustavovalverde/zentity0 reactions · 2 comments
- May 12, 2026chore(deps): bump the prod-dependencies group across 1 directory with 40 updates — gustavovalverde/zentity0 reactions · 2 comments
- May 8, 2026chore(deps): bump the prod-dependencies group across 1 directory with 39 updates — gustavovalverde/zentity0 reactions · 2 comments
- May 8, 2026chore(deps): bump the prod-dependencies group across 1 directory with 40 updates — gustavovalverde/zentity0 reactions · 2 comments
- May 4, 2026chore(deps): bump the prod-dependencies group across 1 directory with 36 updates — gustavovalverde/zentity0 reactions · 2 comments
- Apr 27, 2026chore(deps): bump the prod-dependencies group across 1 directory with 33 updates — gustavovalverde/zentity0 reactions · 2 comments
- Apr 24, 2026chore(deps): bump the prod-dependencies group across 1 directory with 32 updates — gustavovalverde/zentity0 reactions · 2 comments
- Apr 20, 2026chore(deps): bump the prod-dependencies group across 1 directory with 34 updates — gustavovalverde/zentity0 reactions · 2 comments
- Apr 20, 2026chore(deps): bump the prod-dependencies group across 1 directory with 36 updates — gustavovalverde/zentity0 reactions · 2 comments
- Apr 11, 2026chore(deps): bump the prod-dependencies group across 1 directory with 28 updates — gustavovalverde/zentity0 reactions · 2 comments
- Mar 30, 2026deps(deps): bump the minor-and-patch group across 1 directory with 35 updates — vleletko/planner0 reactions · 1 comment
- Jan 12, 2026chore(deps): bump @daveyplate/better-auth-ui from 3.3.14 to 3.3.15 — a1um1/v-template0 reactions · 1 comment
- Jan 12, 2026build(deps): bump the version group with 7 updates — MuntasirSZN/csmc0 reactions · 2 comments
- Jan 12, 2026build(deps): bump the prod-deps-patch group with 2 updates — trunklabs/marshant0 reactions · 1 comment
- Jan 5, 2026build(deps): bump the version group with 4 updates — MuntasirSZN/csmc0 reactions · 1 comment
- Dec 25, 2025build(deps): bump @daveyplate/better-auth-ui from 3.3.9 to 3.3.10 in the version group — MuntasirSZN/csmc0 reactions · 1 comment
- Dec 4, 2025chore(deps): bump the patch-updates group across 1 directory with 25 updates — taucad/tau0 reactions · 4 comments
- Dec 1, 2025chore(deps): bump @daveyplate/better-auth-ui from 3.2.11 to 3.2.13 — a1um1/v-template0 reactions · 1 comment
- Nov 24, 2025build(deps): bump the version group with 4 updates — MuntasirSZN/csmc0 reactions · 3 comments
- Nov 21, 2025build(deps): bump the version group with 2 updates — MuntasirSZN/csmc0 reactions · 2 comments
- Nov 17, 2025build(deps): bump the version group with 2 updates — MuntasirSZN/csmc0 reactions · 3 comments
- Nov 11, 2025PasskeyCard doesn't properly handle errors — better-auth-ui/better-auth-ui0 reactions · 1 comment
- Nov 3, 2025Docs Update: Use per-request QueryClient in TanStack Start integration — better-auth-ui/better-auth-ui0 reactions · 2 comments
- Oct 30, 2025build(deps): bump the version group with 3 updates — MuntasirSZN/csmc0 reactions · 3 comments
- Oct 15, 2025build(deps): bump @daveyplate/better-auth-ui from 3.2.5 to 3.2.6 in the version group — MuntasirSZN/csmc0 reactions · 2 comments
- Oct 9, 2025FAILED_TO_UNLINK_LAST_ACCOUNT Localization Fails in AuthUIProvider — better-auth-ui/better-auth-ui0 reactions · 2 comments
- Sep 24, 2025[AUTH] Upgrade @daveyplate/better-auth-ui to v3 — atomly/journl0 reactions
- Sep 17, 2025fix: CSS variable syntax as an arbitrary value shorthand — better-auth-ui/better-auth-ui0 reactions · 5 comments
- Sep 17, 2025build(deps): bump the version group with 4 updates — MuntasirSZN/csmc0 reactions · 2 comments
- Sep 15, 2025build(deps): bump the version group with 3 updates — MuntasirSZN/csmc0 reactions · 2 comments
Other versions18 projects use a version of this.
Word for word · 9
- nrwl/nx★ 29k100% same
- tsparticles/tsparticles★ 9.1k100% same
- better-auth-ui/better-auth-ui★ 1.7k100% same
- dotCMS/core★ 971100% same
- epam/ai-dial-chat★ 501100% same
- langchain-ai/macaw-design-system★ 12100% same
- socialrobot-io/agent-kit★ 6100% same
- code-dimension/code-dimension-skills★ 3100% same
- OpenThrottle/monorepo★ 2100% same
Edited · 8
- supabase/supabase-js★ 4.6k100% same
- nrwl/nx-console★ 1.4k100% same
- ever-co/ever-teams★ 606100% same
- getlarge/themoltnet★ 2895% same
- conectlens/lenserfight★ 18100% same
- anayatkhan1/kit★ 16100% same
- codeaiforge/ai-ready-nx-workspace★ 2100% same
- storm-software/sourcebook★ 0100% same
Wrote their own version · 1
- jander99/skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository8 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- link-workspace-packagesSkill
- monitor-ciSkill
- nx-generateSkill
- nx-importSkill
- nx-pluginsSkill
- nx-run-tasksSkill
The file
We split this skill into the rules it gives an agent
7 rules. 2 are common, 0 are distinctive, and 5 are very specific to this project.
2
Common
Most of the 9 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 10
Keep in mind that you might have to prefix commands with npx/pnpx/yarn if nx isn't installed globally.
- Very specific: line 14
Use nx show projects to list projects in the workspace.
- Very specific: line 48
Use nx show project <name> --json to get the full resolved configuration for a project.
- Very specific: line 50
Important: Do NOT read project.json directly - it only contains partial configuration.
- Very specific: line 96
Read nx.json directly for workspace-level configuration.
- Common: line 119
If the user is asking about affected projects, read the affected projects reference for detailed commands and examples.
- Common: line 147
When processing nx CLI results, use command-line tools to compute the answer programmatically rather than counting or parsing output …
“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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).
# List all projects
nx show projects
# Filter by pattern (glob)
nx show projects --projects "apps/*"
nx show projects --projects "shared-*"
# Filter by tag
nx show projects --projects "tag:publishable"
nx show projects -p 'tag:publishable,!tag:internal'
# Filter by target (projects that have a specific target)
nx show projects --withTarget build
# Combine filters
nx show projects --type lib --withTarget test
nx show projects --affected --exclude="*-e2e"
nx show projects -p "tag:scope:client,packages/*"
# Negate patterns
nx show projects -p '!tag:private'
nx show projects -p '!*-e2e'
# Output as JSON
nx show projects --jsonProject 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.
# Get full project configuration
nx show project my-app --json
# Extract specific parts from the JSON
nx show project my-app --json | jq '.targets'
nx show project my-app --json | jq '.targets.build'
nx show project my-app --json | jq '.targets | keys'
# Check project metadata
nx show project my-app --json | jq '{name, root, sourceRoot, projectType, tags}'Target Information
Targets define what tasks can be run on a project.
# List all targets for a project
nx show project my-app --json | jq '.targets | keys'
# Get full target configuration
nx show project my-app --json | jq '.targets.build'
# Check target executor/command
nx show project my-app --json | jq '.targets.build.executor'
nx show project my-app --json | jq '.targets.build.command'
# View target options
nx show project my-app --json | jq '.targets.build.options'
# Check target inputs/outputs (for caching)
nx show project my-app --json | jq '.targets.build.inputs'
nx show project my-app --json | jq '.targets.build.outputs'
# Find projects with a specific target
nx show projects --withTarget serve
nx show projects --withTarget e2eWorkspace 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.
# Read the full nx.json
cat nx.json
# Or use jq for specific sections
cat nx.json | jq '.targetDefaults'
cat nx.json | jq '.namedInputs'
cat nx.json | jq '.plugins'
cat nx.json | jq '.generators'Key nx.json sections:
targetDefaults- Default configuration applied to all targets of a given namenamedInputs- Reusable input definitions for cachingplugins- 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 for detailed commands and examples.
Common Exploration Patterns
"What's in this workspace?"
nx show projects
nx show projects --type app
nx show projects --type lib"How do I build/test/lint project X?"
nx show project X --json | jq '.targets | keys'
nx show project X --json | jq '.targets.build'"What depends on library Y?"
# Use the project graph to find dependents
nx graph --print | jq '.graph.dependencies | to_entries[] | select(.value[].target == "Y") | .key'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
nx show projects --jsonExample output:
["my-app", "my-app-e2e", "shared-ui", "shared-utils", "api"]Common operations:
# Count projects
nx show projects --json | jq 'length'
# Filter by pattern
nx show projects --json | jq '.[] | select(startswith("shared-"))'
# Get affected projects as array
nx show projects --affected --json | jq '.'Project Details
nx show project my-app --jsonExample output:
{
"root": "apps/my-app",
"name": "my-app",
"sourceRoot": "apps/my-app/src",
"projectType": "application",
"tags": ["type:app", "scope:client"],
"targets": {
"build": {
"executor": "@nx/vite:build",
"options": { "outputPath": "dist/apps/my-app" }
},
"serve": {
"executor": "@nx/vite:dev-server",
"options": { "buildTarget": "my-app:build" }
},
"test": {
"executor": "@nx/vite:test",
"options": {}
}
},
"implicitDependencies": []
}Common operations:
# Get target names
nx show project my-app --json | jq '.targets | keys'
# Get specific target config
nx show project my-app --json | jq '.targets.build'
# Get tags
nx show project my-app --json | jq '.tags'
# Get project root
nx show project my-app --json | jq -r '.root'Project Graph
nx graph --printExample output:
{
"graph": {
"nodes": {
"my-app": {
"name": "my-app",
"type": "app",
"data": { "root": "apps/my-app", "tags": ["type:app"] }
},
"shared-ui": {
"name": "shared-ui",
"type": "lib",
"data": { "root": "libs/shared-ui", "tags": ["type:ui"] }
}
},
"dependencies": {
"my-app": [
{ "source": "my-app", "target": "shared-ui", "type": "static" }
],
"shared-ui": []
}
}
}Common operations:
# Get all project names from graph
nx graph --print | jq '.graph.nodes | keys'
# Find dependencies of a project
nx graph --print | jq '.graph.dependencies["my-app"]'
# Find projects that depend on a library
nx graph --print | jq '.graph.dependencies | to_entries[] | select(.value[].target == "shared-ui") | .key'Troubleshooting
"Cannot find configuration for task X:target"
# Check what targets exist on the project
nx show project X --json | jq '.targets | keys'
# Check if any projects have that target
nx show projects --withTarget target"The workspace is out of sync"
nx sync
nx reset # if sync doesn't fix stale cacheDoes it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

