angular-portal-write-code

Generating Angular CRUD code requires an orchestrator skill that transforms an approved plan into entity models, services, lazy-loaded routes, and list and detail screens. It dispatches sub-skills for portal and module initialization, then generates the entity code with stateful detail UI.

Handling CREATE, UPDATE, and DETAIL states in Angular form validation involves generating stateful detail UI components with form refinement, including validators, form arrays, and async validators when needed. This is part of orchestrated CRUD generation after the plan is approved.

Quality gates for Angular portal CRUD generation include mandatory tail-calls for E2E tests, code review, ASK-gated inline comments, acceptance verification, auto-docs, task tracking, and conditional memories. These steps enforce a repair loop and create an audit trail.

No, this Angular code generation workflow requires a reviewed and approved CRUD plan for an entity within an Angular Portal module. The orchestrator applies specifically when a user confirms the 06-review-plan step and asks to proceed with implementing the planned entity.

Yes, Angular portal CRUD generation produces bilingual output in Vietnamese and English aligned with the portal conventions. This ensures the generated entity code, list screens, and detail screens support both VI and EN languages.

The best way to structure lazy-loaded routes for Angular CRUD entities is through an orchestrated generation process that creates the entity model, service with mock CRUD store, and list and detail screens. This ensures fully wired entity pages with correct state handling.