monorepo

Organize code placement and dependency boundaries in an Angular CLI monorepo.

Updated Apr 20, 2026
One-click install
npx skills add https://github.com/Suriya-Kodehode/Angular --skill monorepo-suriya-kodehode
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: monorepo
Source: https://github.com/Suriya-Kodehode/Angular/tree/main/.github/skills/monorepo
Command: npx skills add https://github.com/Suriya-Kodehode/Angular --skill monorepo-suriya-kodehode

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you place code in the right project, avoid broken cross-project imports, and keep Angular app, library, and server boundaries clean in a multi-project workspace.

Core Features & Use Cases

  • Project Placement Guidance: Decide whether new code belongs in the Angular app, shared library, backend server, or utility scripts.
  • Shared Type Strategy: Understand how to share DTOs and models safely between Angular and Bun using the library models entry point.
  • Workspace Conventions: Follow the repo’s folder structure, alias rules, build order, and dependency direction to prevent architecture drift.
  • Use Case: When adding a new feature that needs both UI and API types, this Skill tells you where each file should live and how the projects should import from one another.

Quick Start

Ask the monorepo skill where to place a new feature, shared type, or backend module in this Angular workspace.

Frequently Asked Questions about monorepo

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

FAQPage Schema
How do I organize shared types between Angular and a Bun Express backend?

To share types between Angular and a Bun Express backend, place pure TypeScript models in a shared library's secondary entry point. This ensures safe cross-project imports without circular dependencies.

How do I decide where to place new code in an Angular CLI monorepo?

Placing code in an Angular CLI monorepo requires checking dependency boundaries. New code belongs in the Angular app for UI, the shared library for reusable components, or the server for backend modules.

Can I import directly from another project's source files in a monorepo workspace?

Directly importing source files across monorepo projects breaks workspace conventions. You must use configured path aliases and designated entry points to maintain proper build order and clean dependency boundaries.

What is the best way to structure feature routing in a multi-project Angular workspace?

Structuring feature routing in an Angular workspace involves keeping feature modules within the main app while extracting shared DTOs and reusable components into a dedicated library to prevent architecture drift.

Why does my Angular monorepo build fail when importing shared models?

Angular monorepo builds fail when shared models are imported incorrectly due to violated dependency direction. You must adhere to workspace folder conventions and use safe secondary-entry sharing for pure TypeScript models.

Do I need a specific build order for Angular app, library, and server projects?

A specific build order is required for Angular app, library, and server projects. You must build the shared library first so the app and server can safely import types and components without errors.