nx-workspace
Configure, explore, and optimize Nx monorepo workspaces. Use when setting up Nx, exploring workspace structure, configuring project boundaries, analyzing affected projects, optimizing build caching, or implementing CI/CD with affected commands. Keywords — nx, monorepo, workspace, projects, targets, affected. Do NOT use for running tasks (use nx-run-tasks) or code generation with generators (use nx-generate).
What this skill does
# Nx Workspace Management ## Quick Start **Exploring workspace**: `nx show projects` and `nx show project <name> --json` **Running tasks**: `nx <target> <project>` (e.g., `nx build my-app`) **Affected analysis**: `nx show projects --affected` or `nx affected -t <target>` > **Note**: Prefix commands with `npx`/`pnpx`/`yarn` if nx isn't installed globally. ## Core Commands ### List and Explore Projects ```bash # List all projects nx show projects # Filter by type, pattern, or target nx show projects --type app nx show projects --projects "apps/*" nx show projects --withTarget build # Find affected projects nx show projects --affected --base=main ``` ### Get Project Information **Critical**: Always use `nx show project <name> --json` for full resolved configuration. Do NOT read `project.json` directly - it contains only partial configuration. ```bash # Get full configuration nx show project my-app --json # Extract targets nx show project my-app --json | jq '.targets | keys' ``` Configuration schemas: - Workspace: `node_modules/nx/schemas/nx-schema.json` - Project: `node_modules/nx/schemas/project-schema.json` ### Run Tasks ```bash # Run specific project nx build web --configuration=production # Run affected nx affected -t test --base=main # View dependency graph nx graph ``` ## Workspace Architecture ``` workspace/ ├── apps/ # Deployable applications ├── libs/ # Shared libraries │ ├── shared/ # Shared across scopes │ └── feature/ # Feature-specific ├── nx.json # Workspace configuration └── tools/ # Custom executors/generators ``` ### Library Types | Type | Purpose | Example | | --------------- | -------------------------------- | ------------------- | | **feature** | Business logic, smart components | `feature-auth` | | **ui** | Presentational components | `ui-buttons` | | **data-access** | API calls, state management | `data-access-users` | | **util** | Pure functions, helpers | `util-formatting` | ## Detailed Resources **Configuration**: See [reference/configuration.md](reference/configuration.md) for: - nx.json templates and options - project.json structure - Module boundary rules - Remote caching setup **Commands**: See [reference/commands.md](reference/commands.md) for: - Complete command reference - Advanced filtering options - Common workflows **CI/CD**: See [reference/ci-cd.md](reference/ci-cd.md) for: - GitHub Actions configuration - GitLab CI setup - Jenkins, Azure Pipelines, CircleCI examples - Affected commands in pipelines **Best Practices**: See [reference/best-practices.md](reference/best-practices.md) for: - Do's and don'ts - Complete troubleshooting guide - Performance optimization - Migration guides ## Common Workflows **"What's in this workspace?"** ```bash nx show projects --type app # List applications nx show projects --type lib # List libraries ``` **"How do I run project X?"** ```bash nx show project X --json | jq '.targets | keys' ``` **"What changed?"** ```bash nx show projects --affected --base=main ``` ## Quick Troubleshooting - **Targets not showing**: Use `nx show project <name> --json`, not project.json - **Affected not working**: Ensure git history available (`fetch-depth: 0` in CI) - **Cache issues**: Run `nx reset` For detailed troubleshooting, see [reference/best-practices.md](reference/best-practices.md).
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.