Angular Refactor
Soking511/angular-refactor
Refatora Angular para clean code, best practices e arquitetura escalável
Ver no GitHubSkill que refatora código Angular existente seguindo as melhores práticas atuais, clean code e arquitetura escalável com base no guia de estilo oficial do Angular. Executa um fluxo estruturado de avaliação, planejamento e execução, priorizando segurança e preservação de comportamento.
Instalação
npx convez-ai Soking511/angular-refactor1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Modernizar projetos Angular legado mantendo comportamento funcional
- Reorganizar estrutura de pastas e arquitetura de um app Angular
- Aplicar convenções de nomenclatura e import hygiene
- Planejar upgrade seguro do Angular com aprovação antes da execução
- Desentangling de RxJS e migração para signals com análise de risco
Veredito

Skill sólida e bem estruturada para refatoração Angular em produção. Destaca-se pelo fluxo assess→plan→execute que separa diagnóstico de execução, e pela abordagem conservadora que surfaça modernizações arriscadas (Reactive→Signal Forms, zoneless) como decisões explícitas do desenvolvedor. Excelente para times que precisam modernizar sem quebrar o que funciona.
README
A tradução para o português deste README ainda está na fila.
angular-refactor
A Claude skill that refactors existing Angular code toward clean code, current best practices, and a scalable folder/architecture — grounded in the latest Angular style guide resolved at run time (via the Context7 MCP, with a web fallback) rather than from the model's training data.
It is for improving code that already exists, not greenfield generation — though the same principles apply when writing new code.
What it does
- Triggers on phrases like "clean up this Angular project," "modernize this service," "how should I organize my Angular app," "this component is a mess," or any request to apply Angular best practices — the word "refactor" is not required.
- Runs assess → plan → (approval) → execute. Assessment emits a structured, dependency-ordered refactor plan and stops; execution is a separate, approved phase. The plan is a finalized artifact a human or an autonomous agent can parse and orchestrate.
- Is behavior-preserving and safe by default: it does not bump versions or swap risky APIs (e.g. Reactive Forms → Signal Forms, Zone.js → zoneless) unless you explicitly ask. High-value-but-risky modernizations are surfaced in the plan for you to decide.
- Targets the latest Angular. If a project is behind, Phase 0 of the plan is an approval-gated
ng update; if you decline, only version-agnostic work runs (structure, imports, dead code, naming, typing).
Contents
| File | Purpose |
|---|---|
SKILL.md | Entry point: operating principles, the assess → plan → execute workflow, and routing to the references. |
references/architecture.md | Folder structure and architectural boundaries. |
references/paths-and-imports.md | Barrel/alias policy, import hygiene, and dependency governance. |
references/components-and-state.md | Components, signals, and state management. |
references/templates-and-rxjs.md | Templates, native control flow, and untangling RxJS. |
references/conventions-and-checklist.md | Naming conventions and the refactor checklist. |
Installation
Copy the angular-refactor folder into your Claude skills directory (e.g. ~/.claude/skills/angular-refactor), or install it as part of a skills plugin. Claude will load it automatically when a matching request comes in.
License
MIT