nx AGENTS.md

When responding to queries about this repository:

1. Suggest relevant commands from the "Essential Commands" section when applicable
2. Highlight Nx's focus on monorepos and its key features like smart task execution, code generation, and project graph analysis
3. Mention the plugin ecosystem and support for various frameworks when relevant
4. Emphasize the importance of running the full validation suite before committing changes

Always strive to provide accurate, helpful responses that align with the best practices and workflows described in this file.

Documentation Contributions

When working on Nx documentation, all documentation content lives in the astro-docs/ folder. This is the new Astro-based documentation site built with Starlight.

Important: Before making any documentation changes, read the astro-docs/README.md file for detailed guidance on:

• Project structure and architecture
• Content types (regular docs, dynamic plugin docs, CLI docs)
• Available Markdoc tags for rich content
• Development workflow and commands
• Sidebar management

Quick Reference

• Documentation content: astro-docs/src/content/docs/
• Use .mdoc (Markdoc) or .mdx format for documentation files
• Run nx serve astro-docs to start the local dev server
• Sidebar structure is defined in astro-docs/sidebar.mts

GitHub Issue Response Mode

When responding to GitHub issues, determine your approach based on how the request is phrased:

Plan-First Mode (Default)

Use this approach when users ask you to:

• "analyze", "investigate", "assess", "review", "examine", or "plan"
• Or when the request is ambiguous

In this mode:

1. Provide a detailed analysis of the issue
2. Create a comprehensive implementation plan
3. Break down the solution into clear steps
4. Then please post the plan as a comment on the issue

Immediate Implementation Mode

Use this approach when users ask you to:

• "fix", "implement", "solve", "build", "create", "update", or "add"
• Or when they explicitly request immediate action