Documentation · Legacy Resurrection Studio
A necromancer's manual for raising legacy systems into modern architectures.
Overview
Legacy Resurrection Studio is an enterprise-grade modernization platform that transforms outdated technologies into modern, maintainable architectures. The system employs three specialized “resurrection chambers” that analyze legacy code, detect patterns, and generate production-ready migration artifacts.
Each chamber performs deep analysis using pattern detection engines, security scanners, and complexity scoring algorithms. The platform generates comprehensive migration plans with realistic timelines, cross-chamber routing suggestions, and production-ready code output. Built for real-world enterprise modernization projects requiring strategic planning and phased implementation.
Chambers
Legacy Reanimator
Analyzes legacy codebases for anti-patterns, calculates risk scores, and provides strategic modernization recommendations with intelligent routing.
API Necromancer
Transforms SOAP/WSDL services into modern REST APIs with complete OpenAPI 3.0 specifications and 4-phase migration strategies.
Ghost UI Converter
Converts Bootstrap/jQuery UI into modern React + Tailwind components with security analysis and state management migration.
Architecture
Built on Next.js 14 App Router with TypeScript strict mode, the platform employs a modular architecture with specialized analysis libraries, API routes, and chamber-specific pipelines.
Core Libraries
- ▸
src/lib/analysis- Pattern detection, risk scoring, and routing engine - ▸
src/lib/soap- WSDL parsing, REST transformation, OpenAPI generation - ▸
src/lib/ui- jQuery analysis, React generation, security scanning
API Routes
- ▸
/api/analyze- Legacy code analysis and chamber routing - ▸
/api/soap-to-rest- SOAP to REST conversion with OpenAPI output - ▸
/api/convert-ui- UI modernization with security analysis
Each chamber generates modernization artifacts including migration reports, code stubs, OpenAPI specifications, React components, and strategic implementation guidance with realistic timelines.
Kiro Usage
This project leverages Kiro as an engineering partner, not just a code generator. Kiro maintains consistency across the codebase through specs, hooks, and steering rules.
Specs
Formal specifications that define feature requirements, design, and implementation tasks:
- •
analysis-spec.yaml- Pattern detection and risk scoring specifications - •
soap-spec.yaml- SOAP to REST transformation requirements - •
ui-spec.yaml- UI modernization and component generation specs - •
theme-spec.yaml- Dark necromancer theme and design system - •
migration-plan-spec.yaml- Migration strategy templates
Hooks
Automated workflows triggered by events:
- •
doc-sync.yaml- Auto-syncs documentation when code changes - •
test-gen.yaml- Generates tests for new components
Steering
Context and guidelines included in all Kiro interactions:
- •
code-conventions.md- TypeScript standards, naming, file organization - •
migration-voice.md- Professional tone for migration documentation - •
ui-consistency.md- Dark theme, spacing, component patterns
Kiro acts as an engineering partner by maintaining consistency across all chambers, auto-syncing artifacts when specifications change, and ensuring every generated component follows the established design system and coding standards.