Run any Skill in Manus with one click

refactor-plan

Stars2

Forks0

UpdatedFebruary 27, 2026 at 11:26

Incremental refactor playbook for moving legacy LifeOS code toward Clean Architecture/DDD. Use when splitting monolithic services/controllers, introducing ports/adapters, or migrating features without breaking current behavior.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

pvidaal07

pvidaal07/LifeOS

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

2 files

SKILL.md

readonly

name	refactor-plan
description	Incremental refactor playbook for moving legacy LifeOS code toward Clean Architecture/DDD. Use when splitting monolithic services/controllers, introducing ports/adapters, or migrating features without breaking current behavior.

Refactor Plan

Objetivo

Refactorizar por slices de funcionalidad sin detener entregas ni romper contratos.

Estrategia incremental

Aislar una feature concreta (ej. reviews).
Congelar comportamiento actual con tests de caracterización.
Extraer reglas a dominio/aplicación (casos de uso + puertos).
Implementar adapters en infraestructura.
Conectar controller actual al nuevo caso de uso.
Eliminar código legacy solo cuando pruebas y contratos estén verdes.

REQUIRED

Migrar un flujo de negocio cada vez.
Mantener compatibilidad de API durante la transición.
Documentar decisiones de corte (qué quedó migrado y qué no).

NEVER

No hacer big-bang rewrite.
No mezclar reglas nuevas y legacy sin límites claros.
No borrar código antiguo sin cobertura mínima del nuevo camino.

More from this repository

same repository

nestjs-best-practices

pvidaal07/LifeOS

NestJS best practices and architecture patterns for building production-ready applications. This skill should be used when writing, reviewing, or refactoring NestJS code to ensure proper patterns for modules, dependency injection, security, and performance.

2026-02-272

api-contracts

pvidaal07/LifeOS

API DTO and response contract rules for LifeOS backend/frontend compatibility. Use when adding or changing endpoints, request/response DTOs, error payloads, versioning decisions, or Swagger/OpenAPI documentation.

2026-02-272

auth-and-ownership

pvidaal07/LifeOS

Authentication and ownership enforcement rules for LifeOS multi-user isolation. Use when creating or changing auth flows, guarded endpoints, user-scoped queries, or nested resource access checks.

2026-02-272

clean-architecture-ddd

pvidaal07/LifeOS

Clean Architecture + DDD rules for this repo. Triggers: adding/refactoring code across src/domain|application|infrastructure, moving files between layers, creating ports/adapters/use-cases.

2026-02-272

docker-selfhost

pvidaal07/LifeOS

Docker Compose self-hosting conventions for LifeOS development and production. Use when editing compose files, environment variables, service networking, persistent volumes, health checks, or deployment workflows.

2026-02-272

docs

pvidaal07/LifeOS

Repository documentation conventions for LifeOS. Use when creating or updating README, docs/*, architecture notes, API behavior notes, or implementation decisions that must remain clear for future contributors and agents.

2026-02-272

name	refactor-plan
description	Incremental refactor playbook for moving legacy LifeOS code toward Clean Architecture/DDD. Use when splitting monolithic services/controllers, introducing ports/adapters, or migrating features without breaking current behavior.

Refactor Plan

Objetivo

Refactorizar por slices de funcionalidad sin detener entregas ni romper contratos.

Estrategia incremental

Aislar una feature concreta (ej. reviews).
Congelar comportamiento actual con tests de caracterización.
Extraer reglas a dominio/aplicación (casos de uso + puertos).
Implementar adapters en infraestructura.
Conectar controller actual al nuevo caso de uso.
Eliminar código legacy solo cuando pruebas y contratos estén verdes.

REQUIRED

Migrar un flujo de negocio cada vez.
Mantener compatibilidad de API durante la transición.
Documentar decisiones de corte (qué quedó migrado y qué no).

NEVER

No hacer big-bang rewrite.
No mezclar reglas nuevas y legacy sin límites claros.
No borrar código antiguo sin cobertura mínima del nuevo camino.