skills.rest
JNZader
JNZaderCOMMUNITY
Explore all skills by this author →
GitHub

angular-architecture

Enforce scope-based placement, file naming, and structure for Angular projects.

Updated Mar 15, 2026
Search Tags:#architecture#angular#naming-conventions#style-guide#project-structure#scope-rule#file-naming
One-click install
npx skills add https://github.com/JNZader/javi-ai --skill angular-architecture-jnzader
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: angular-architecture
Source: https://github.com/JNZader/javi-ai/tree/main/upstream/gentleman-skills/curated/angular/architecture
Command: npx skills add https://github.com/JNZader/javi-ai --skill angular-architecture-jnzader

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Angular architecture guidance to standardize scope-based placement, project structure, and file naming for maintainable apps.

Core Features & Use Cases

  • Scope Rule enforcement: determine where a component lives (feature-based vs shared) based on usage.
  • Project Structure guidance: recommended layout (src/app with features/, shared/, core/ folders) to improve navigation and collaboration.
  • File Naming: enforce consistent naming (no misleading suffixes; folder context indicates type) to reduce confusion.
  • Style Guide: provide consistent coding style and naming practices across the codebase.

Quick Start

Apply the scope rule and naming conventions when organizing an Angular project.

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 for scalability?▼

The Angular scope rule determines where a component lives based on usage. It enforces feature-based versus shared placement, ensuring components reside in the correct directories for predictable organization and easier collaboration.

What are the best file naming conventions for Angular components?▼

Angular file naming conventions enforce consistent naming without misleading suffixes. Relying on folder context to indicate component type reduces confusion and maintains consistent coding style across the codebase.

When should I use shared versus feature-based folders in Angular?▼

Use shared versus feature-based folders by applying the scope rule to determine component placement based on usage. Shared folders house reusable elements while feature folders isolate specific application capabilities.

Does a centralized Angular style guide improve project maintainability?▼

A centralized Angular style guide improves maintainability by providing consistent coding style and naming practices across the codebase. This standardization reduces confusion and shapes the overall layout of large applications.

Related Skills

Explore More Software Engineering Skills→
yu13130122297yu13130122297

scout

Identify uncertainties in research framing, datasets, metrics, and baselines.

Community
Intermediate
Faouzi91Faouzi91

angular-feature

Generate Angular feature modules with routes, components, services, and models.

Community
Intermediate
nguyenthienthanhnguyenthienthanh
24

angular-expert

Optimize Angular 17+ components and state management with signals and RxJS.

Community
Advanced
guilhermemarketingguilhermemarketing
59

nx-workspace

Configure Nx workspace structure, boundaries, and build caching.

Community
Advanced