angular-portal-screen-detail

Generate and refine Angular Portal entity detail components for CREATE, UPDATE, and DETAIL routes.

2|Updated Apr 18, 2026
One-click install
npx skills add https://github.com/sdcorejs/sdcorejs-agent --skill angular-portal-screen-detail
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: angular-portal-screen-detail
Source: https://github.com/sdcorejs/sdcorejs-agent/tree/main/plugin/skills/angular-portal-screen-detail
Command: npx skills add https://github.com/sdcorejs/sdcorejs-agent --skill angular-portal-screen-detail

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill generates and refines an Angular Portal entity detail screen so CREATE, UPDATE, and DETAIL routes share one component file with correct form behavior, permissions, navigation, and robust validation.

Core Features & Use Cases

  • One component for three states: CREATE (/create), UPDATE (/update/:id), DETAIL (/detail/:id) with state-aware UI and route dispatching.
  • Production-grade reactive form refinement: validators, async validators, FormArray support, cross-field rules, and signal-first UI state patterns.
  • Safety and correctness guardrails: file upload ordering (before create/update), stale-id recovery with replaceUrl navigation, and permission-gated header actions.
  • Use case: build or fix a product detail page where CREATE defaults are wrong, DETAIL should be read-only, Edit button missing, file uploads firing after save, or form validation not blocking invalid submits.

Quick Start

Use the angular-portal-screen-detail skill to generate and refine pages/detail/detail.component.ts for a new or broken entity screen across CREATE, UPDATE, and DETAIL routes.

Frequently Asked Questions about angular-portal-screen-detail

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

FAQPage Schema
How do I build an Angular CRUD detail screen that handles CREATE, UPDATE, and DETAIL routes in one component?

To fix Angular reactive form validation not blocking invalid submits, apply required validators, async validators, and cross-field rules to your form. This ensures the form strictly validates inputs before allowing any persistence actions to execute.

Why are my Angular file uploads firing after the entity is saved?

A DETAIL route should be read-only by applying per-state rendering rules to your shared component. This enforces read-only behavior on the reactive form, disabling edits while still displaying the entity data correctly.

How do I fix stale-id failures during Angular route navigation?

To add permission-gated actions in an Angular detail screen, implement permission checks on header actions within your component. This gates actions like Edit or Delete, ensuring only authorized users can trigger state transitions or modifications.

Can I use a single reactive form for an Angular CRUD screen with different state behaviors?

Yes, you can use a single reactive form for an Angular CRUD screen by applying signal-first UI state patterns. This allows the shared form to dynamically adjust its validators and rendering rules based on the current CREATE, UPDATE, or DETAIL route.