CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

migration-migrate-component

Use when a component needs migration to the target architecture or framework version.

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./packs/angular/skills/migration-migrate-component/SKILL.md
SKILL.md
Quality
Evals
Security

Migrate an Angular component to standalone with signals following docs/ARCHITECTURE.md section 5.

Component: $ARGUMENTS

Steps

  1. Read docs/ARCHITECTURE.md section 5.

  2. Analyze the component:

    • Count lines (template, class)
    • List: @Input, @Output, constructor deps, lifecycle hooks, NgModule membership
    • Map who imports this component
  3. Convert to modern Angular:

    • @NgModule membership -> standalone: true
    • @Input() prop -> readonly prop = input<T>()
    • @Output() event = new EventEmitter() -> readonly event = output<T>()
    • constructor(private svc: Service) -> private readonly svc = inject(Service)
    • ngOnInit() -> constructor or afterNextRender()
    • ngOnChanges() -> effect() watching input signals
    • *ngIf -> @if () { }
    • *ngFor -> @for (item of items; track item.id) { }
    • Add ChangeDetectionStrategy.OnPush
  4. Apply composition pattern if there is prop drilling.

  5. Decompose if > 200 lines.

  6. Validate:

npx tsc --noEmit
ng build
ng test --watch=false
Repository

fernandezbaptiste/specialist-agent

Path

packs/angular/skills/migration-migrate-component/SKILL.md

Last updated
First committed

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.