vue-architecture-optimizer-framework

What problem does it solve?

This Skill helps teams turn ad-hoc Vue codebases and refactor impulses into repeatable, business-aligned architecture work by clarifying responsibilities, unifying state sources, and producing safe incremental migration plans. It prevents coupling between business rules and UI scaffolding, avoids premature or semantic-mismatched abstractions, and reduces the risk of large, unreviewable rewrites.

Core Features & Use Cases

• Problem classification: Distinguishes business-driven changes, technical debt refactors, and greenfield architecture design and prescribes different workflows for each.
• Evidence-driven diagnosis: Guides collection of business boundaries, module responsibilities, state flow, side effects, and migration risk before prescribing changes.
• Actionable outputs: Produces business confirmations, directory and naming recommendations, composable/store/service extraction plans, stepwise migration with rollback points, and risk/metric assessments.
• Use cases: Extracting composables from duplicated logic, moving shared state into Pinia or domain stores, isolating adapters for unstable APIs, or designing a new Vue architecture from business process maps.

Quick Start

Ask the skill to analyze the repository and produce a business-confirmation checklist plus a three-step, rollback-safe migration plan to move duplicated UI logic into composables and a domain Pinia store.