--- title: "Beware the spaceships" url: https://daily.dev/posts/beware-the-spaceships-5ohuowfy6 source_url: https://swizec.com/blog/beware-the-spaceships type: article source: "swizec.com" published: 2026-08-09T01:26:14.671Z updated: 2026-08-09T16:42:00.827Z tags: ["tailwind-css", "ai-coding", "claude"] reading_time: 3 upvotes: 0 comments: 0 language: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Beware the spaceships **[swizec.com](https://daily.dev/sources/swizec)** · 3 min read · 0 upvotes · 0 comments ## Summary A developer shares lessons from using AI agents to migrate a design system, coining the 'spaceship problem': AI can rapidly generate large-scale rewrites (22,000-line Bootstrap-to-Tailwind, 12,000-line lint fixes, 11 stacked PRs for a full section rewrite), but the generated code requires significant human cleanup. In one case, generating code took 2 hours while cleanup took 2 engineers 2 days. The core issue is that LLMs excel at mechanical translation but struggle with conceptual leaps — Claude rebuilt custom components instead of using library defaults. The takeaway: AI-generated 'spaceships' are useful for getting something working fast and gathering feedback, but be ready to delete and redo if the approach is fundamentally wrong. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### What are the downsides of using LLMs to do large-scale code migrations or rewrites? LLMs excel at mechanical translation but struggle with conceptual leaps. A common failure mode is that the model rebuilds a custom version of a component using the new library instead of simply using the library's defaults — because it grounds its approach in existing code patterns rather than making the conceptual jump to 'just use what ships out of the box'. In one migration, AI generated code in 2 hours but cleanup took 2 engineers 2 days. _Developers navigating AI-assisted migrations share hard-won patterns like this on daily.dev._ ### How do you structure a large AI-assisted codebase rewrite into reviewable pull requests? Breaking the rewrite page-by-page and generating stacked pull requests is an effective strategy. GitHub's stacked PRs feature supports this workflow, allowing each page or section to be reviewed independently. This approach was used to produce 11 stacked PRs covering a full app section rewrite, making the large changeset manageable for code review. _Teams shipping big rewrites with AI track strategies like stacked PRs on daily.dev._ ## Similar posts on daily.dev - [Agents change the math on big bang migrations](https://daily.dev/posts/agents-change-the-math-on-big-bang-migrations-pac5lf3qj) · swizec.com · 34 upvotes · 8 comments - [The Unbearable Lightness of Coding](https://daily.dev/posts/the-unbearable-lightness-of-coding-vlnmxgw0d) · Towards Data Science · 0 upvotes · 0 comments --- Tags: [#tailwind-css](https://daily.dev/tags/tailwind-css), [#ai-coding](https://daily.dev/tags/ai-coding), [#claude](https://daily.dev/tags/claude) [View this post on daily.dev](https://daily.dev/posts/beware-the-spaceships-5ohuowfy6)