clean-branch

Rebase the boilerplate branch onto the dev branch, then strip all domain-specific code while keeping generic infrastructure. This skill guides the process: delete domain contexts, clean DI registrations and barrel exports, regenerate the route tree and migrations, then verify with type checks and tests.

Delete the context directory, then remove its router imports from the routers map and CONTEXTS manifest, unregister its repositories and use cases from the DI container, and clean its schemas, enums, events, and error mapper entries. All references must be fixed atomically or the build fails.

Skip the sync when dev changes are purely domain-specific with no architectural value, when the clean branch does not exist yet, or when you only need a small bug fix on clean. In those cases, fix clean directly or create it with a full initial strip.

Failures usually come from dangling imports in the DI container, missing entries in the exhaustive GlobalErrorMapper, stale route tree references, or empty files that are not modules. Run the route tree generator, add export statements to empty files, and fix all references before committing.

Keep shared infrastructure like the DI container, error handling, and OpenAPI setup, plus auth, ui contexts, generic enums, landing and auth pages, and base components. Strip all domain contexts, events, domain routes, and project-specific documentation.