angular-architecture

Define scope-based placement rules for Angular project components and files.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/raudyagdel/ai_setup_and_tips --skill angular-architecture-raudyagdel
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: angular-architecture
Source: https://github.com/raudyagdel/ai_setup_and_tips/tree/main/.agents/skills/angular-architecture
Command: npx skills add https://github.com/raudyagdel/ai_setup_and_tips --skill angular-architecture-raudyagdel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a clear framework for organizing Angular projects, reducing confusion about where components live and how to name files.

Core Features & Use Cases

  • Scope Rule: Determine where a component should reside based on usage.
  • Project Structure: Guidelines for features/, shared/, core/, and app-wide folders.
  • File Naming: Enforce concise, suffix-free names that reflect purpose.

Quick Start

Describe how to apply the Scope Rule to restructure an existing Angular app.

Frequently Asked Questions about angular-architecture

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

FAQPage Schema
How do I structure a large Angular project to keep components organized?

Structure large Angular projects using scope-based placement rules that define where components, modules, and shared versus feature-specific code reside across features/, shared/, and core/ folders.

What is the Scope Rule in Angular architecture?

The Scope Rule in Angular architecture determines where a component should reside based on its usage, ensuring feature-specific code stays separated from app-wide shared code.

What naming conventions should I use for Angular component files?

Use concise, suffix-free file names that reflect the component's purpose to enforce a consistent Angular style guide across medium and large applications.

Where should shared code go versus feature-specific code in an Angular app?

Place shared code in the shared/ folder and feature-specific code in the features/ folder, applying scope-based placement rules to determine the correct location for each component.

Is this Angular architecture guide suitable for restructuring an existing app?

Yes, you can apply the Scope Rule to restructure an existing Angular app by reorganizing components, modules, and files into the recommended project structure.