angular-portal-onboarding

Onboarding — Angular Portal SDLC Agent

Purpose

Welcome the developer and help them pick the right next skill. This is the entry point when the developer is new to this agent or unsure where to start.

When to use

• First interaction in a session
• User asks "agent này làm được gì", "list skill", "help", "how do I use this"
• User describes work but is unsure how to proceed
• User opens the project after a long pause and needs orientation

Response template

1. One-sentence intro

"This agent helps you build Angular portal apps using @sd-angular/core (Core UI), following SDCoreJS conventions across the full SDLC — from requirement clarification to code, tests, review, and documentation."

2. SDLC workflow at a glance

Design phase is cross-track (skills/shared/sdlc/); each skill detects the target as angular-portal and loads _refs/angular-portal.md. Code-writing + tests + reviews are track-specific.

Request
  ↓
shared/sdlc/01-brainstorm        (sdcorejs-brainstorm)
  ← only if scope is open-ended
  ↓
shared/sdlc/02-clarify-requirements  (sdcorejs-clarify-requirements)
  ← blocking questions: module / entity / fields / layout / workflow / coverage
  ↓
shared/sdlc/03-write-spec        (sdcorejs-write-spec)
  ← spec written to <target>/.sdcorejs/docs/angular-portal/*-spec.md
  ↓
shared/sdlc/04-review-spec       (sdcorejs-review-spec) — APPROVAL GATE
  ↓
orchestration/auto-specs         ← MANDATORY on approval; snapshot to .sdcorejs/specs/angular-portal/
  ↓
shared/sdlc/05-plan              (sdcorejs-plan)
  ← numbered file-by-file plan
  ↓
shared/sdlc/06-review-plan       (sdcorejs-review-plan) — APPROVAL GATE
  ↓
orchestration/auto-plans         ← MANDATORY on approval; snapshot to .sdcorejs/plans/angular-portal/
  ↓
tracks/angular-portal/07-write-code  (angular-portal-write-code)
  ← orchestrator, picks sub-skills based on plan:
   ├─ 10-init-portal       (new portal repo)
   ├─ 11-init-module       (new feature module)
   ├─ 12-init-entity       (new entity CRUD pages — templates in _refs/templates/)
   ├─ 20-screen-list       (list page)
   ├─ 21-screen-detail     (detail.component.ts — CREATE / UPDATE / DETAIL + form refinement)
   └─ 31-actions           (action buttons — workflow / bulk / custom side-effects)
  ↓
testing/e2e/angular-portal       (sdcorejs-testing-e2e-angular-portal)
  ← happy-path E2E for what was just built
  ↓
review/code/angular-portal       (sdcorejs-review-code-angular-portal)
  ← convention check; Critical / Important / Minor findings
  ↓
orchestration/repair-loop        ← apply findings + iterate until Critical+Important resolved
  ↓
orchestration/comment-code       ← MANDATORY ASK gate: skip / simple / medium / full
   └─ rules applied inline (cross-track baseline + per-track addenda live in this skill)
  ↓
orchestration/verify-before-done ← MANDATORY acceptance-criteria gate; blocks "done" until ✅ / deferred
  ↓
orchestration/auto-docs ← MANDATORY summary to <target>/.sdcorejs/docs/angular-portal/
orchestration/auto-task-tracker  ← MANDATORY; tick `[x]` done + append new in .sdcorejs/tasks/angular-portal.md
orchestration/memories           ← durable knowledge (when surfaced) to .sdcorejs/memories/angular-portal/

3. How to invoke skills

You don't need to memorize skill names. Just describe what you want — the agent matches your request against each skill's description and picks the right one. Examples:

User says	Skill picked
"Khởi tạo portal-shop với dev/qc/uat/prod"	10-init-portal
"Thêm entity product, fields code/name/price"	sdcorejs-clarify-requirements (cross-track) → 12-init-entity
"Tạo màn list cho user"	20-screen-list
"Review module catalog"	sdcorejs-review-code-angular-portal
"Test cho entity product"	sdcorejs-testing-e2e-angular-portal
"Brainstorm cho module sales"	sdcorejs-brainstorm (cross-track)
"Viết spec cho module catalog"	sdcorejs-write-spec (cross-track)

4. Mandatory rules (always apply)

• Auto-docs: every code-writing task ends with a summary at <target-project>/.sdcorejs/docs/angular-portal/<YYYY-MM-DD-HH-mm>-<topic>.md. The agent reads this folder at session start to recall prior work.
• Memories: durable knowledge (corrections, stakeholder constraints, project decisions) lives at <target-project>/.sdcorejs/memories/angular-portal/. Agent reads frontmatter at session start; bodies on demand.
• Bilingual: Vietnamese request → Vietnamese output (full diacritics). English request → English output. Permission codes and route paths stay English in both cases.
• Clarify-before-code: agent will not generate code when module ownership, entity name, or key fields are unspecified.
• Test after generation: npm run test -- --watch=false --include=src/libs/<module>/**/*.spec.ts. Report summary and failing spec names.
• Core UI first: use @sd-angular/core components when one fits; otherwise generate skeleton + alert('TODO: ...') stubs and mark for developer.

5. Reference docs (loaded on demand)

The agent only reads these when relevant — don't load upfront:

• _refs/architecture-principles.md — the WHY: 16 principles governing what generated code looks like (feature-first, signal-first, no cross-module imports, OnPush default, 4 canonical layouts, mock-first, …). Load when explaining a decision, reviewing a deviation, or onboarding a new contributor.
• _refs/core-version.md — pinned @sd-angular/core version
• _refs/sd-angular-core-catalog.md — Core UI components and patterns
• _refs/entity-field-types.md — field type → form control mapping
• _refs/templates/entity-{skeleton,tests,example-product}.md — canonical code templates emitted by 12-init-entity

6. What to do next

• New project: invoke sdcorejs-clarify-requirements (cross-track) to define portal name + environments + first module — or sdcorejs-brainstorm first if scope is still open-ended.
• Existing project: describe what to add (module / entity / screen). Agent dispatches the right sub-skill.
• Resuming work: agent reads <target>/.sdcorejs/docs/angular-portal/ first to recall what's been built. Skim the latest entry yourself if you want a quick status — or invoke sdcorejs-recovery for a one-screen handoff.

Output guidelines for this skill

• Keep replies short. Skip preamble like "I am an AI assistant...".
• One bullet per skill, max 1 line each.
• Always end with one concrete next step the user can take ("Tell me X to proceed").
• Match the user's language (VI ↔ EN).

Anti-patterns

• ❌ Don't repeat full rules from other skill files. Link to them.
• ❌ Don't generate code from this skill. Defer to 07-write-code and its sub-skills.
• ❌ Don't ask clarifying questions about scope here — that's sdcorejs-clarify-requirements's job (cross-track).