Angular ui patterns

Angular UI Patterns

Modern Angular UI patterns for loading states, error handling, and data display. Use when building UI components, handling async data, or managing component states.

When to Use

• This skill is applicable to execute the workflow or actions described in the overview.

Core Workflow

1. Confirm the request matches this skill's trigger, scope, and risk profile.
2. Use the topic map to identify the relevant pattern, checklist, or example before writing detailed guidance or code.
3. Load references/full-guidance.md when implementation details, examples, anti-patterns, validation checks, or edge cases are needed.
4. Apply only the relevant guidance instead of loading or repeating the entire reference by default.
5. Verify the result against any validation checks, limitations, security notes, or platform constraints in the reference.

Topic Map

• Core Principles
• Loading State Patterns
• The Golden Rule
• Loading State Decision Tree
• Skeleton vs Spinner
• Control Flow Patterns
• @if/@else for Conditional Rendering
• @for with Track
• @defer for Progressive Loading
• Error Handling Patterns
• Error Handling Hierarchy
• Always Show Errors
• Error State Component Pattern
• Button State Patterns
• Button Loading State
• Disable During Operations
• Empty States
• Empty State Requirements

Reference Map

• references/full-guidance.md preserves the complete original guidance, including examples and detailed edge cases.

Limitations

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Progressive Loading

Keep this SKILL.md as the compact routing and workflow entrypoint. Load the reference file only when the user task requires the deeper implementation material.