angular-conventions

Enforce Angular component structure, naming, error handling, and lazy loading conventions.

291|38|Updated Mar 16, 2026

Search Tags:#frontend #angular #conventions #lazy-loading #standalone-components #feature-based #error-capture

Ready to run

npx skills add https://github.com/J-Pster/Psters_AI_Workflow --skill angular-conventions

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: angular-conventions
Source: https://github.com/J-Pster/Psters_AI_Workflow/tree/main/plugins/psters-ai-workflow/skills/angular-conventions
Command: npx skills add https://github.com/J-Pster/Psters_AI_Workflow --skill angular-conventions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Angular frontend teams struggle with inconsistent structure and error handling across projects.

Core Features & Use Cases

Standalone components and feature-based structure to improve maintainability.
Centralized error capture and consistent validation patterns to reduce bugs.
Lazy loading recommendations and English text guidelines to enhance performance and accessibility.

Quick Start

Follow these conventions when creating or reviewing Angular frontends to ensure consistency and reliability.

Frequently Asked Questions about angular-conventions

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

FAQPage Schema

How do I structure an Angular frontend for scalable and maintainable apps?▼

Structure an Angular frontend using feature-based folders and standalone components to improve maintainability. This approach organizes code by domain features, reducing bugs and ensuring consistent structure across new apps and refactors.

What is the best way to implement centralized error capture in Angular?▼

Implement centralized error capture in Angular by applying consistent validation patterns across your project. This reduces bugs by funneling exceptions and validation failures into a single, unified handling workflow rather than scattered component-level logic.

When should I use lazy loading in Angular standalone components?▼

Use lazy loading in Angular standalone components when building scalable apps to enhance performance. Apply lazy loading recommendations during project setup or refactoring to split feature modules, reducing initial bundle size and improving load times.

Does the angular-conventions workflow support refactoring existing projects?▼

Yes, the angular-conventions workflow supports refactoring existing projects. It guides component structure, naming conventions, and error capture to enforce consistent frontend structure during both new app creation and project refactors.

What naming conventions should I follow for Angular feature-based folders?▼

Follow English UI text guidelines and standardized naming conventions for Angular feature-based folders. Enforcing consistent naming across standalone components and centralized error capture ensures a build-ready workflow and improves accessibility.