MCPInstall

ln-720-structure-migrator

Scaffolds new or restructures existing projects to Clean Architecture. Use when setting up project structure.

Installs
378
Last 24h
—
Trending rank
—
Security
Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/levnikolaevich/claude-code-skills --skill ln-720-structure-migrator
  1. 01

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads ln-720-structure-migrator automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

Paths: File paths (references/, ../ln-*) are relative to this skill directory.

ln-720-structure-migrator

Type: L2 Domain Coordinator Category: 7XX Project Bootstrap Parent: ln-700-project-bootstrap

Coordinates project restructuring to Clean Architecture. Mode-aware: delegates to workers with appropriate mode parameters based on CREATE/TRANSFORM pipeline.


Purpose & Scope

AspectDescription
InputCurrent project structure + mode (CREATE/TRANSFORM) from ln-700
OutputRestructured project with Clean Architecture
WorkersSee Workers table below

Workers

WorkerRoleCREATE modeTRANSFORM mode
ln-721Frontend structureSCAFFOLD (generate starter)RESTRUCTURE (migrate monolith)
ln-722Backend generatorRUN (generate backend)RUN (generate backend)
ln-723Seed dataGENERATE (from entities)MIGRATE (from ORM schemas)
ln-724Artifact cleanerSKIP (no artifacts)CONDITIONAL (only if platform detected)

Scope boundaries:

  • Analyzes current project structure (TRANSFORM) or accepts target config (CREATE)
  • Generates migration plan or scaffold plan
  • Delegates to specialized workers via Agent tool
  • Verifies final result

Workflow

PhaseNameCREATE modeTRANSFORM mode
1AnalyzeReceive target stack configScan structure, detect framework, map files
2PlanCalculate scaffold actionsCalculate moves, identify conflicts
3ExecuteDelegate: ln-721 SCAFFOLD → ln-722 → ln-723 GENERATEDelegate: ln-724 (conditional) → ln-721 RESTRUCTURE → ln-722 → ln-723 MIGRATE
4VerifyCheck file structure, validate configsRun builds, check imports, validate structure

Target Structures

Frontend (React)

src/frontend/
├── public/
├── src/
│   ├── components/
│   │   ├── layout/      # AppLayout, Header, Sidebar
│   │   └── ui/          # Reusable UI components
│   ├── contexts/        # React contexts
│   ├── hooks/           # Custom hooks
│   ├── lib/             # Utilities, API clients
│   ├── pages/           # Page components
│   │   └── {Feature}/   # Feature-specific files
│   ├── App.tsx
│   ├── main.tsx
│   └── index.css
├── package.json
├── vite.config.ts
└── tsconfig.json

Backend (.NET Clean Architecture)

src/
├── {Project}.Api/
│   ├── Controllers/
│   ├── DTOs/
│   ├── Middleware/
│   ├── MockData/
│   ├── Extensions/
│   ├── Program.cs
│   └── appsettings.json
├── {Project}.Domain/
│   ├── Entities/
│   ├── Enums/
│   └── Common/
├── {Project}.Services/
│   └── Interfaces/
├── {Project}.Repositories/
│   └── Interfaces/
└── {Project}.Shared/

Delegation Protocol

To ln-724 (Artifact Cleaner)

When to invoke: TRANSFORM mode AND platform artifacts detected (.replit, .stackblitzrc, sandbox.config.json, glitch.json). Skip conditions: CREATE mode OR no platform config files found.

Context:
  projectPath: /project
  skipPreview: false
Options:
  # ln-724 auto-detects platform, no need to specify
  cleanConfigFiles: true
  cleanDirectories: true
  cleanPackages: true
  cleanBuildConfig: true
  cleanCodeComments: true
  cleanGitignore: true

To ln-721 (Frontend)

Context:
  mode: SCAFFOLD | RESTRUCTURE          # From pipeline mode
  # SCAFFOLD mode:
  targetPath: /project/src/frontend
  projectName: MyApp
  # RESTRUCTURE mode:
  sourcePath: /project/client
  targetPath: /project/src/frontend
  framework: react
  features:
    - Dashboard
    - Settings
    - Profile
Options:
  # RESTRUCTURE only:
  splitMonolithicFiles: true
  extractConstants: true
  extractTypes: true
  createComponentLibrary: true

To ln-722 (Backend)

Context:
  projectName: MyApp
  targetPath: /project/src
  targetFramework: net10.0
  features:
    - Dashboard
    - Users
Options:
  createMockData: true
  addSwagger: true
  addHealthChecks: true

To ln-723 (Seed Data)

Context:
  mode: MIGRATE | GENERATE              # From pipeline mode
  targetFormat: csharp | typescript | python | json | sql
  # MIGRATE mode:
  sourceORM: auto                        # Auto-detect (drizzle/prisma/typeorm/efcore/sqlalchemy/django)
  sourcePath: /project/references/schema.ts
  # GENERATE mode:
  entities:                              # Optional — if empty, starter template used
    - name: User
      fields: [id, name, email, role, createdAt]
    - name: Role
      fields: [id, name, description]
  targetPath: /project/src/MyApp.Api/MockData

Critical Rules

  • Orchestrator Pattern: Analyze and delegate via Skill tool, do not execute transformations directly
  • Mode Awareness: Pass correct mode to all workers — CREATE vs TRANSFORM determines worker behavior
  • Conditional Workers: ln-724 runs ONLY in TRANSFORM mode when platform artifacts detected; SKIP otherwise
  • Sequential Workers: Execute in order (ln-724 conditional → ln-721 → ln-722 → ln-723)
  • Pre-flight Checks: Verify git status clean, target paths available
  • No Data Loss: Copy before delete, verify before removing source (TRANSFORM mode)
  • Build Verification: All builds must pass (npm run build, dotnet build)
  • Rollback Ready: Keep backup branch until verification complete (TRANSFORM mode)

Invocations:

Skill(skill: "ln-724-artifact-cleaner", args: "{projectPath}")  # TRANSFORM only, conditional
Skill(skill: "ln-721-frontend-restructure", args: "{projectPath} --mode {SCAFFOLD|RESTRUCTURE}")
Skill(skill: "ln-722-backend-generator", args: "{projectPath}")
Skill(skill: "ln-723-seed-data-generator", args: "{projectPath} --mode {GENERATE|MIGRATE}")

TodoWrite format (mandatory):

- Invoke ln-724-artifact-cleaner (conditional TRANSFORM) (pending)
- Invoke ln-721-frontend-restructure (pending)
- Invoke ln-722-backend-generator (pending)
- Invoke ln-723-seed-data-generator (pending)
- Verify structure and builds (pending)

Worker Invocation (MANDATORY)

Host Skill Invocation: Skill(skill: "...", args: "...") is mandatory delegation.

  • Claude: call the Skill tool exactly as shown.
  • Codex: if no Skill tool exists, locate the named skill in available skills, read its SKILL.md, treat args as $ARGUMENTS, execute that skill workflow, then return here with its result/artifact.
  • Do not inline worker logic or mark the worker complete without executing the target skill.
PhaseWorkerContext
3aln-724-artifact-cleanerShared (Skill tool) — remove platform artifacts (TRANSFORM only, conditional)
3bln-721-frontend-restructureShared (Skill tool) — scaffold or restructure frontend
3cln-722-backend-generatorShared (Skill tool) — generate backend project structure
3dln-723-seed-data-generatorShared (Skill tool) — generate or migrate seed data

All workers: Invoke via Skill tool — workers see coordinator context.

Definition of Done

CREATE mode:

  • Target stack config received from ln-700
  • ln-721 completed: Frontend scaffolded (SCAFFOLD mode)
  • ln-722 completed: Backend generated
  • ln-723 completed: Seed data generated (GENERATE mode)
  • File structure matches target templates
  • All configs valid (package.json, tsconfig.json, .csproj)

TRANSFORM mode:

  • Current structure analyzed and documented
  • Migration plan generated
  • ln-724 completed: Platform artifacts removed (if applicable)
  • ln-721 completed: Frontend restructured (RESTRUCTURE mode)
  • ln-722 completed: Backend generated
  • ln-723 completed: Seed data migrated (MIGRATE mode)
  • Frontend builds successfully (npm run build)
  • Backend builds successfully (dotnet build)
  • No orphan files in old locations
  • All imports resolve correctly
  • Migration report generated

Risk Mitigation

RiskDetectionMitigation
Uncommitted changesgit status not cleanRequire clean working directory
Build failure (frontend)npm run build failsRollback, delegate to ln-721 for fix
Build failure (backend)dotnet build failsRollback, delegate to ln-722 for fix
Lost filesFiles missing after migrationRestore from backup branch
Import errorsModule not foundRe-run import update phase
Partial migrationWorker fails mid-executionAtomic: complete all or rollback all
Wrong worker modeMode mismatchValidate mode parameter before delegation

Reference Files

FilePurpose
references/clean_architecture_dotnet.md.NET project structure template
references/frontend_structure.mdReact project structure template

Meta-Analysis

Optional reference: load references/meta_analysis_protocol.md only when the user asks for post-run meta-analysis or protocol-formatted run reflection.

Skill type: execution-orchestrator. When requested, run after all phases complete. Output to chat using the execution-orchestrator format.


Version: 3.0.0 Last Updated: 2026-02-07

FAQ

What does the ln-720-structure-migrator skill do?

Scaffolds new or restructures existing projects to Clean Architecture. Use when setting up project structure.

How do I install ln-720-structure-migrator?

Run npx skills add https://github.com/levnikolaevich/claude-code-skills --skill ln-720-structure-migrator in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/ln-720-structure-migrator/ (personal) or .claude/skills/ln-720-structure-migrator/ (project).

Which AI agents can use ln-720-structure-migrator?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is ln-720-structure-migrator safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains ln-720-structure-migrator?

It is published by levnikolaevich in levnikolaevich/claude-code-skills. It has 378 recorded installs.

More from levnikolaevich/claude-code-skills

View all →

ln-100-documents-pipeline

levnikolaevich/claude-code-skills

Creates complete project documentation system (project docs, reference, tasks, tests). Use when bootstrapping docs from scratch or regenerating all.

Docs & Writing479 installs

ln-620-codebase-auditor

levnikolaevich/claude-code-skills

Use when auditing the codebase through the evaluation platform with mandatory research, coordinated domain audit workers, and structured summaries.

ln-775-api-docs-generator

levnikolaevich/claude-code-skills

Configures Swagger/OpenAPI documentation for backend APIs. Use when adding interactive API docs to a project.

Backend & APIs432 installs

ln-624-code-quality-auditor

levnikolaevich/claude-code-skills

Checks cyclomatic complexity, nesting, long methods, god classes, O(n2), N+1 queries, constants management. Use when auditing code quality.

413 installs

ln-782-test-runner

levnikolaevich/claude-code-skills

Executes all test suites and reports results with coverage. Use when verifying that test infrastructure works after bootstrap.

Testing & QA412 installs

ln-634-test-coverage-auditor

levnikolaevich/claude-code-skills

Open the skill to read its SKILL.md instructions.

Testing & QA401 installs

Popular code quality & workflow skills

View category →

grill-me

mattpocock/skills

A relentless interview to sharpen a plan or design.

Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

handoff

mattpocock/skills

Compact the current conversation into a handoff document for another agent to pick up.

domain-modeling

mattpocock/skills

Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.

codebase-design

mattpocock/skills

Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.

diagnosing-bugs

mattpocock/skills

Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.