workflow-clean-code-angular

1. Nothing unnecessary — no defensive checks for impossible scenarios, no abstractions with one consumer, no comments that restate the code
2. Right responsibility in the right place — stores own data transformations, components coordinate UI, templates just bind
3. Consistent patterns — every store follows the same anatomy, every component follows the same structure, no surprise conventions </philosophy>

/clean-code-angular feature/budget/          # Standard audit
/clean-code-angular -a --deep feature/       # Deep audit, auto mode
/clean-code-angular --quick core/            # Quick surface scan
/clean-code-angular --slop --vm feature/     # Focus: AI slop + ViewModel
/clean-code-angular diff main                # Audit changes vs main
/clean-code-angular pending                  # Audit uncommitted changes

-a

-e

-s

.claude/output/clean-code-angular/

-r

--quick

--deep

--arch

--signals

--styling

--testing

--slop

--vm

--adv

--ultra

--deep

Agent Architecture

-e

--deep

--deep --adv

--ultra

Standard/Deep Mode — Flat Architecture

The 10 Domains

effect()

computed()

linkedSignal()

input()

output()

inject()

any

#

::ng-deep

!important

@defer

--testing

--deep

--ultra

.spec.ts

references/testing-patterns.md

Ultra Mode — Multi-Tier Cluster Architecture

references/angular-architecture.md

references/angular-clean-code.md

@defer

references/angular-anti-patterns.md

references/angular-clean-code.md

references/angular-clean-code.md

references/angular-anti-patterns.md

references/angular-anti-patterns.md

references/ai-slop-detection.md

references/angular-clean-code.md

references/angular-clean-code.md

references/angular-anti-patterns.md

references/viewmodel-patterns.md

references/angular-clean-code.md

references/testing-patterns.md

references/angular-anti-patterns.md

references/angular-clean-code.md

15 specialists (parallel) → 5 cluster leads (parallel) → Grand Tech Lead → Adversarial

Team Lead (Standard/Deep)

• Merges all specialist reports into one deduplicated list
• Removes false positives by reading the actual code
• Resolves contradictions between specialists
• Adds cross-cutting observations no single specialist caught
• Prioritizes the final issue list
• Verifies fix coherence in step-02
• Does final craftsman review in step-03

Cluster Leads (Ultra)

• Deduplicate within their domain
• Resolve contradictions between their specialists
• Add domain-specific cross-cutting observations
• Output a focused domain report (max 10 issues per cluster)

Grand Tech Lead (Ultra)

• Merges all cluster reports into one unified list
• Resolves cross-cluster contradictions (e.g., Architecture says "move to core" but Quality says "inline it")
• Identifies systemic patterns across clusters (e.g., "every file has the same DI problem")
• Prioritizes by business impact, not just technical severity
• Caps at 30 issues, notes total if more
• Adds a "systemic diagnosis" section: what's the ROOT CAUSE behind the pattern of issues?

Adversarial Reviewer (--adv or --ultra)

• Challenges each finding: "Is this really wrong? Could there be a valid architectural reason?"
• Hunts false positives: reads the actual code for each flagged issue and checks if context was missed
• Hunts missed issues: reads ALL files in scope looking for issues that ALL specialists + leads missed
• Questions severity: "Is this really Critical or just Important? Would a production user notice?"
• Checks RxJS false flags: verifies that valid RxJS patterns aren't flagged as signal anti-patterns
• Checks Angular version assumptions: verifies recommendations match Angular 21+
• Checks against project profile: verifies that no finding contradicts the project's documented conventions from {project_profile}

{task_description}

{task_id}

{auto_mode}

{economy_mode}

{save_mode}

{depth}

{force_*}

{scoped_files}

{issues}

{workspace_path}

{agent_count}

{adversarial_mode}

{ultra_mode}

{project_profile}

references/angular-anti-patterns.md

references/angular-clean-code.md

references/angular-style-guide.md

references/angular-architecture.md

--arch

references/ai-slop-detection.md

--slop

references/viewmodel-patterns.md

--vm

references/testing-patterns.md

--testing

steps/step-01-scan.md

step-01-scan.md

step-02-apply.md

step-03-verify.md

• Discover project context BEFORE scanning — read CLAUDE.md, package.json, angular.json, eslint config to build {project_profile}
• Filter ALL findings through {project_profile} — never flag patterns that match documented project conventions
• Load one step at a time
• Scale agent count to scope size (economy mode = 0 agents, direct tools only)
• Use the Grep tool for pattern detection (not bash grep)
• Scope-aware: only touch files within the specified scope
• Every finding:

  file:line

  reference required
• Every fix: source citation required
• Team lead reviews after scan AND after apply </execution_rules>

• Zero architecture violations
• Modern signal patterns throughout
• Stores follow 6-section anatomy with proper ViewModel selectors
• No AI slop — no unnecessary comments, abstractions, or defensive code
• Clean ViewModel separation — stores transform, components bind, templates stay simple
• Consistent patterns across all files in scope
• Quality check passes (lint + type-check + format)
• Tests pass
• If --adv: adversarial review found no missed issues or false positives </success_criteria>