chore(repo): create claude.md

Author: FrozenPandaz

.claude/settings.json

@@ -0,0 +1,25 @@
+{
+  "permissions": {
+    "allow": [
+      "Bash(find:*)",
+      "Bash(ls:*)",
+      "WebFetch(domain:github.com)",
+      "Bash(gh issue list:*)",
+      "Bash(gh issue view:*)",
+      "Bash(npx prettier:*)",
+      "mcp__nx__nx_workspace",
+      "mcp__nx__nx_project_details",
+      "Bash(nx show projects:*)",
+      "Bash(nx run-many:*)",
+      "Bash(nx lint:*)",
+      "Bash(nx test:*)",
+      "Bash(nx build:*)",
+      "Bash(nx documentation:*)"
+    ],
+    "deny": []
+  },
+  "enableAllProjectMcpServers": true,
+  "env": {
+    "BASH_MAX_TIMEOUT_MS": "1800000"
+  }
+}

.github/workflows/claude.yml

@@ -19,15 +19,44 @@ jobs:
       (github.event_name == 'issues' && (contains(github.event.issue.body, '@claude') || contains(github.event.issue.title, '@claude')))
     runs-on: ubuntu-latest
     permissions:
-      contents: read
-      pull-requests: read
-      issues: read
+      contents: write
+      pull-requests: write
+      issues: write
+      actions: read
       id-token: write
     steps:
       - name: Checkout repository
         uses: actions/checkout@v4
         with:
-          fetch-depth: 1
+          fetch-depth: 250
+
+      - name: Install dependencies
+        run: |
+          sudo apt-get update
+          sudo apt-get install -y ca-certificates lsof libvips-dev libglib2.0-dev libgirepository1.0-dev
+
+      - name: Install Chrome
+        uses: browser-actions/setup-chrome@v1
+
+      - uses: pnpm/action-setup@v4
+        name: Install pnpm
+        with:
+          version: 9.8.0
+          run_install: false
+
+      - name: Install project dependencies
+        run: |
+          pnpm install --frozen-lockfile
+          pnpm playwright install --with-deps
+
+      - name: Install Rust
+        uses: dtolnay/rust-toolchain@stable
+
+      - name: Setup Java
+        uses: actions/setup-java@v4
+        with:
+          distribution: temurin
+          java-version: 17
 
       - name: Run Claude Code
         id: claude

.gitignore

@@ -73,6 +73,8 @@ storybook-static
 .gradle
 .kotlin
 
+.claude/settings.local.json
+
 .cursor/rules/nx-rules.mdc
 .github/instructions/nx.instructions.md
 .cursor/rules/nx-rules.mdc

.mcp.json

@@ -0,0 +1,9 @@
+{
+  "mcpServers": {
+    "nx": {
+      "command": "pnpm",
+      "args": ["nx-mcp", "/home/jason/projects/nx"],
+      "env": {}
+    }
+  }
+}

CLAUDE.md

@@ -0,0 +1,105 @@
+When responding to queries about this repository:
+
+1. Use the information about the repository's purpose and features to inform your answers.
+2. Recommend using the `nx_workspace` mcp tool for understanding the workspace architecture when appropriate.
+3. Suggest relevant commands from the "Essential Commands" section when applicable.
+4. Emphasize the importance of testing changes as outlined in the file.
+
+For specific types of queries:
+
+- If asked about the purpose or features of Nx, refer to the "Repository Purpose" section.
+- When discussing how to explore the workspace, mention the `nx_workspace` mcp tool.
+- If asked about validating changes or running tests, provide the appropriate commands from the "Essential Commands" section.
+- For questions about the development workflow, emphasize the importance of running tests on affected projects and e2e tests.
+
+Remember to:
+
+- Highlight Nx's focus on monorepos and its key features like smart task execution, code generation, and project graph analysis.
+- Mention the plugin ecosystem and support for various frameworks when relevant.
+- Emphasize the importance of running the full validation suite before committing changes.
+- Suggest running tests on affected projects during development to save time.
+
+Always strive to provide accurate, helpful responses that align with the best practices and workflows described in this file. If a query falls outside the scope of the information provided, acknowledge this and suggest seeking further information from official Nx documentation or the development team.
+
+## Avoid making changes to generated files
+
+Files under `generated` directories are generated based on a different source file and should not be modified directly. Find the underlying source and modify that instead.
+
+## Essential Commands
+
+### Pre-push Validation
+
+```bash
+# Full validation suite - run before committing
+pnpm nx prepush
+```
+
+### Testing Changes
+
+After code changes are made, first test the specific project where the changes were made:
+
+```bash
+nx run-many -t test,build,lint -p PROJECT_NAME
+```
+
+After verifying the individual project, validate that the changes in projects which have been affected:
+
+```bash
+# Test only affected projects (recommended for development)
+nx affected -t build,test,lint
+```
+
+As the last step, run the e2e tests to fully ensure that changes are valid:
+
+```bash
+# Run affected e2e tests (recommended for development)
+nx affected -t e2e-local
+```
+
+## Fixing GitHub Issues
+
+When working on a GitHub issue, follow this systematic approach:
+
+### 1. Get Issue Details
+
+```bash
+# Get issue details using GitHub CLI (replace ISSUE_NUMBER with actual number)
+gh issue view ISSUE_NUMBER
+```
+
+When cloning reproduction repos, please clone within `./tmp/claude/repro-ISSUE_NUMBER`
+
+### 2. Analyze the Plan
+
+- Look for a plan or implementation details in the issue description
+- Check comments for additional context or clarification
+- Identify affected projects and components
+
+### 3. Implement the Solution
+
+- Follow the plan outlined in the issue
+- Make focused changes that address the specific problem
+- Ensure code follows existing patterns and conventions
+
+### 4. Run Full Validation
+
+```bash
+# Test specific affected projects first
+nx run-many -t test,build,lint -p PROJECT_NAME
+
+# Test all affected projects
+nx affected -t build,test,lint
+
+# Run affected e2e tests
+nx affected -t e2e-local
+
+# Final pre-push validation
+pnpm nx prepush
+```
+
+### 5. Submit Pull Request
+
+- Create a descriptive PR title that references the issue
+- Include "Fixes #ISSUE_NUMBER" in the PR description
+- Provide a clear summary of changes made
+- Request appropriate reviewers

CODEOWNERS

@@ -191,6 +191,11 @@ rust-toolchain.toml @nrwl/nx-native-reviewers
 /.husky/** @nrwl/nx-pipelines-reviewers
 /packages/workspace/src/generators/ci-workflow/** @nrwl/nx-pipelines-reviewers
 
+# Claude AI Integration
+CLAUDE.md @FrozenPandaz
+.claude/** @FrozenPandaz
+.mcp.json @FrozenPandaz
+
 # Global Files
 project.json @FrozenPandaz @vsavkin
 jest.config.ts @nrwl/nx-testing-tools-reviewers @FrozenPandaz

CONTRIBUTING.md

@@ -27,14 +27,25 @@ can [submit a Pull Request](https://github.com/nrwl/nx/blob/master/CONTRIBUTING.
 
 Source code and documentation are included in the top-level folders listed below.
 
-- `docs` - Markdown and configuration files for documentation including tutorials, guides for each supported platform,
-  and API docs.
-- `e2e` - E2E tests.
 - `packages` - Source code for Nx packages such as Angular, React, Web, NestJS, Next and others including generators and
   executors (or builders).
+- `e2e` - E2E tests for the Nx packages
+- `graph` - Source code for the Nx Graph application which shows the project graph, task graph, project details, and more in the browser.
+- `docs` - Markdown and configuration files for documentation including tutorials, guides for each supported platform,
+  and API docs.
+- `nx-dev` - Source code for the Nx documentation site which displays the markdown in `docs` and more.
+- `tools` - Workspace-specific tooling and plugins
 - `scripts` - Miscellaneous scripts for project tasks such as building documentation, testing, and code formatting.
 - `tmp` - Folder used by e2e tests. If you are a WebStorm user, make sure to mark this folder as excluded.
 
+## Technologies
+
+This repo contains a mix of different technologies, including:
+
+- **Rust**: The core of Nx is written in Rust, which provides performance and safety.
+- **TypeScript**: The primary language for Nx packages and the Nx DevKit.
+- **Kotlin**: Used for the Gradle and Java plugins.
+
 ## Development Workstation Setup
 
 If you are using `VSCode`, and provided you have [Docker](https://docker.com) installed on your machine, then you can leverage [Dev Containers](https://containers.dev) through this [VSCode extension](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers), to easily setup your development environment, with everything needed to contribute to Nx, already installed (namely `NodeJS`, `Yarn`, `Rust`, `Cargo`, plus some useful extensions like `Nx Console`).

docs/generated/cli/affected.md

@@ -1,11 +1,11 @@
 ---
-title: 'affected - CLI command'
-description: 'Run target for affected projects. See https://nx.dev/ci/features/affected for more details.'
+title: "affected - CLI command"
+description: "Run target for affected projects. "Affected projects" are those that have been changed in the current branch/PR, or that depend on a project that has been changed. See https://nx.dev/using-nx/affected for more details."
 ---
 
 # affected
 
-Run target for affected projects. See [https://nx.dev/ci/features/affected](/ci/features/affected) for more details.
+Run target for affected projects. "Affected projects" are those that have been changed in the current branch/PR, or that depend on a project that has been changed. See [https://nx.dev/using-nx/affected](/using-nx/affected) for more details.
 
 ## Usage
 

docs/generated/packages/nx/documents/affected.md

@@ -1,11 +1,11 @@
 ---
-title: 'affected - CLI command'
-description: 'Run target for affected projects. See https://nx.dev/ci/features/affected for more details.'
+title: "affected - CLI command"
+description: "Run target for affected projects. "Affected projects" are those that have been changed in the current branch/PR, or that depend on a project that has been changed. See https://nx.dev/using-nx/affected for more details."
 ---
 
 # affected
 
-Run target for affected projects. See [https://nx.dev/ci/features/affected](/ci/features/affected) for more details.
+Run target for affected projects. "Affected projects" are those that have been changed in the current branch/PR, or that depend on a project that has been changed. See [https://nx.dev/using-nx/affected](/using-nx/affected) for more details.
 
 ## Usage
 

package.json

@@ -78,8 +78,10 @@
     "@nuxt/kit": "^3.10.0",
     "@nuxt/schema": "^3.10.0",
     "@nx/angular": "21.2.0-beta.1",
+    "@nx/conformance": "2.0.1",
     "@nx/cypress": "21.2.0-beta.1",
     "@nx/devkit": "21.2.0-beta.1",
+    "@nx/enterprise-cloud": "2.0.1",
     "@nx/esbuild": "21.2.0-beta.1",
     "@nx/eslint": "21.2.0-beta.1",
     "@nx/eslint-plugin": "21.2.0-beta.1",
@@ -88,8 +90,6 @@
     "@nx/key": "2.0.1",
     "@nx/next": "21.2.0-beta.1",
     "@nx/playwright": "21.2.0-beta.1",
-    "@nx/conformance": "2.0.1",
-    "@nx/enterprise-cloud": "2.0.1",
     "@nx/powerpack-license": "2.0.1",
     "@nx/react": "21.2.0-beta.1",
     "@nx/rsbuild": "21.2.0-beta.1",
@@ -270,6 +270,7 @@
     "npm-package-arg": "11.0.1",
     "nuxt": "^3.10.0",
     "nx": "21.2.0-beta.1",
+    "nx-mcp": "^0.0.9",
     "octokit": "^2.0.14",
     "open": "^8.4.0",
     "openai": "~4.3.1",

packages/nx/src/command-line/affected/command-object.ts

@@ -15,7 +15,7 @@ import {
 export const yargsAffectedCommand: CommandModule = {
   command: 'affected',
   describe:
-    'Run target for affected projects. See https://nx.dev/ci/features/affected for more details.',
+    'Run target for affected projects. "Affected projects" are those that have been changed in the current branch/PR, or that depend on a project that has been changed. See https://nx.dev/using-nx/affected for more details.',
   builder: (yargs) =>
     linkToNxDevAndExamples(
       withAffectedOptions(