nx-workspace-architect

Initialize Nx workspaces with Angular, NestJS, and shared libraries.

28|6|Updated Aug 31, 2025
One-click install
npx skills add https://github.com/Hive-Academy/ptah-extension --skill nx-workspace-architect
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nx-workspace-architect
Source: https://github.com/Hive-Academy/ptah-extension/tree/main/apps/ptah-extension-vscode/assets/plugins/ptah-nx-saas/skills/nx-workspace-architect
Command: npx skills add https://github.com/Hive-Academy/ptah-extension --skill nx-workspace-architect

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

This Skill guides developers in establishing structured, maintainable Nx monorepos for large-scale projects.

Core Features & Use Cases

  • Workspace Initialization: Automates creation of Nx workspaces with best practices for Angular, NestJS, and shared libraries.
  • Library Structuring: Facilitates domain-based organization with multiple library types, including feature, ui, data-access, and util.
  • Dependency Management: Sets up path mappings, module boundaries, and project tagging for clean architecture enforcement.
  • Use Case: A developer wants to kickstart a new micro-frontend and backend project with a consistent structure and dependency rules.

Quick Start

Run the workspace setup guide to create and configure a monorepo with Angular and NestJS applications, shared libraries, and enforced boundaries.

Frequently Asked Questions about nx-workspace-architect

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure an Nx monorepo for scalable Angular and NestJS applications?

Structure a scalable Nx monorepo by initializing the workspace and organizing code into domain-based libraries like feature, ui, data-access, and util. This ensures modularization and maintainable dependency control for enterprise-level applications.

What is the best way to enforce module boundaries in an Nx workspace?

Enforce module boundaries in an Nx workspace by configuring path mappings and project tagging. These dependency rules restrict unauthorized imports between domain libraries, ensuring clean architecture and maintainable project structure.

When do I need to use domain-based library types in an Nx workspace?

Use domain-based library types in an Nx workspace when building large-scale projects requiring strict modularization. Categorizing libraries into feature, ui, data-access, and util types facilitates clean architecture enforcement and manages dependencies effectively across teams.

Can I use an Nx workspace to set up a micro-frontend and backend project?

Yes, you can use an Nx workspace to kickstart a micro-frontend and backend project. It provides comprehensive instructions for initializing workspaces with integrated frameworks like Angular and NestJS, ensuring consistent structure and enforced dependency rules.

How do I manage dependencies across shared libraries in an Nx monorepo?

Manage dependencies across shared libraries in an Nx monorepo by configuring path mappings and module boundaries. This setup enforces dependency control, allowing teams to build scalable applications with a maintainable and structured development environment.