vesper-monolith-refactor

Decompose oversized Vesper owner seams into adjacent modules via facade-first extraction.

1|Updated Jan 26, 2026
One-click install
npx skills add https://github.com/AskTinNguyen/vesper-team-skills --skill vesper-monolith-refactor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vesper-monolith-refactor
Source: https://github.com/AskTinNguyen/vesper-team-skills/tree/main/vesper-monolith-refactor
Command: npx skills add https://github.com/AskTinNguyen/vesper-team-skills --skill vesper-monolith-refactor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Decompose an oversized Vesper owner seam into adjacent modules without changing behavior.

Core Features & Use Cases

  • Facade-first seam extraction to shrink monoliths while preserving behavior
  • Move one seam at a time into an adjacent job-named module
  • Preserve facade boundaries, guards, and orchestration to minimize risk
  • Enable safe resumption with clear verification trails

Quick Start

Begin by selecting a stable seam in the oversized owner and extract it into an adjacent module following the facade-first pattern.

Frequently Asked Questions about vesper-monolith-refactor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I decompose a monolith without changing existing behavior?

To decompose a monolith without changing behavior, use a facade-first seam extraction approach. This shrinks the oversized owner by moving one seam at a time into an adjacent module while preserving the original orchestration and guards.

What is facade-first modularization in monolith architecture?

Facade-first modularization is an architecture technique that keeps the original owner as a stable facade. It extracts seams into adjacent job-named modules, minimizing risk by preserving boundaries and guards during monolith decomposition.

When do I need seam-by-seam extraction for a monolith?

You need seam-by-seam extraction when targeting large monoliths that require gradual modularization. This process moves individual seams into adjacent modules one by one, enabling safe resumption with clear verification trails.

What's the best way to extract a stable seam from an oversized owner module?

The best way to extract a stable seam is to select it from the oversized owner and move it into an adjacent job-named module. This facade-first pattern ensures the original owner remains stable while enabling targeted verification.

Can I resume monolith modularization if a seam extraction is interrupted?

Yes, seam-by-seam monolith modularization enables safe resumption through clear verification trails. Each seam extraction into an adjacent module is verified independently, ensuring the facade boundaries remain intact.

Does seam extraction require moving the entire monolith at once?

No, seam extraction targets one seam at a time rather than moving the entire monolith. This facade-first approach keeps the original owner as a stable facade while gradually decomposing the architecture into adjacent modules.