[IMPORTANT] Use TaskCreate to break ALL work into small tasks BEFORE starting — including tasks for each file read. This prevents context loss from long files. For simple tasks, AI MUST ask user whether to skip.

Prerequisites: MUST READ before executing:

• .claude/skills/shared/understand-code-first-protocol.md

• .claude/skills/shared/evidence-based-reasoning-protocol.md

Quick Summary

Goal: Scaffold a new full-stack feature with backend (entities, CQRS, controllers) and frontend (Angular components, services).

Workflow:

• Analyze — Break down requirements, identify scope (backend/frontend/full-stack)

• Identify — Determine target microservice and Angular app/module

• Plan — Map out entities, commands/queries, endpoints, components, DTOs

• Approve — Present plan, wait for explicit user approval before creating files

• Create — Scaffold files in order: entities → application → DTOs → controllers → frontend

Key Rules:

• DO NOT proceed without explicit user approval

• Follow platform patterns from CLAUDE.md and .github/prompts/ templates

• Build order: Domain → Application → API → Frontend

• Verify with dotnet build and nx build after creation

Be skeptical. Apply critical thinking, sequential thinking. Every claim needs traced proof, confidence percentages (Idea should be more than 80%).

Create a new feature: $ARGUMENTS

Steps:

Analyze Requirements

• Break down the feature requirements

• Identify the scope (backend only, frontend only, or full-stack)

Identify Service Location

• Determine the appropriate microservice for backend

• Identify the Angular app/module for frontend

Plan Implementation

• Domain entities needed

• CQRS Commands/Queries

• API endpoints (controllers)

• Angular components and services

• DTOs and validation

Use Project Patterns

• Reference patterns from CLAUDE.md

• Use .github/prompts/ templates for scaffolding:

• create-cqrs-command.prompt.md

• create-cqrs-query.prompt.md

• create-entity-event.prompt.md

• create-angular-component.prompt.md

• create-api-service.prompt.md

Wait for Approval

• Present the implementation plan

• DO NOT proceed without explicit approval

Create Files (After Approval) Execute in this order:

• Domain entities (.Domain/Entities/ )

• Application layer (.Application/UseCaseCommands/ , .Application/UseCaseQueries/ )

• Entity DTOs (.Application/EntityDtos/ )

• API controllers (.Api/Controllers/ )

• Frontend components and services

Verify

• Build backend: dotnet build

• Build frontend: nx build <app-name>

IMPORTANT Task Planning Notes (MUST FOLLOW)

• Always plan and break work into many small todo tasks

• Always add a final review todo task to verify work quality and identify fixes/enhancements