Nx workspace commands and guidelines for running tasks, generators, and using Nx MCP tools
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
This is an Nx 22.5.3 monorepo using npm. Prefer the Nx MCP server over guessing about the workspace — it reflects the live project graph and config.
nx_workspace — understand the project graph / architecture, and surface
project-graph or config errors, before answering workspace questions.nx_project_details — inspect a single project's targets and config.nx_docs — fetch up-to-date Nx docs for any configuration/best-practice
question instead of assuming.nx_visualize_graph — show task/project dependencies.nx_current_running_tasks_details / nx_current_running_task_output — inspect
tasks already running in the user's terminals; rerun with nx run <taskId> so
it executes in the same Nx context. Don't offer to rerun a continuous task.When scaffolding, drive it through the MCP flow rather than hand-writing files:
nx_generators to list, nx_generator_schema for options, then
nx_open_generate_ui and read back nx_read_generator_log. Keep options minimal;
use nx_available_plugins if no generator fits.
nx run <project>[:target]; targets live in each project's
project.json (or are inferred from config).Commands and Libraries sections of
AGENTS.md — not duplicated here.No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Creates and maintains Figma Code Connect files (`*.figma.tsx`) that map Figma components to code via the parser-based `figma.connect()` API. Use when the user mentions Code Connect, Figma component mapping, design-to-code translation, or asks to create/update .figma.tsx files.
The English summary is being prepared. Showing the original description.
Use when creating, naming, or placing a file or folder in libs/*, or when modifying or adding a file to an existing component (even when the barrel isn't touched) — component vs utility naming, the one-responsibility-per-file layout, when a folder needs an `index.ts` barrel (public API only), and the required set of files a component needs per lib. Load this before scaffolding or restructuring a component so the layout matches the codebase.
The English summary is being prepared. Showing the original description.
Use when designing or changing a component's public API, its composition, or its state model in libs/ui-react or libs/ui-rnative — layering (core vs internal vs primitives), BaseProps/Props splits, converting a component to compound / changing its composition with createSafeContext, controlled/uncontrolled state, prop-naming conventions, and cross-platform API parity. Load this before shaping a new component, changing its props, or refactoring its composition.
The English summary is being prepared. Showing the original description.
Use when writing or editing Storybook MDX docs (*.mdx) — the two-tab Overview/Implementation structure, story-backed `<Source>` examples, and doc table guidelines.
The English summary is being prepared. Showing the original description.
Use when creating or editing Storybook stories (*.stories.tsx, React or React Native) — story layout, controls, and export naming conventions.
The English summary is being prepared. Showing the original description.
Use when building or styling a component in libs/ui-react or libs/ui-rnative — the cross-platform styling principles, plus routing to the platform mechanics: Tailwind + cva + cn on web, useStyleSheet + themeJS + lx on React Native. Load this before writing component styles.
The English summary is being prepared. Showing the original description.