Migrate React components from MUI to Tailwind

Lumos used Devin for a straightforward style-system migration and relied on tests to reduce back-and-forth fixes.

Done with Devin· Intermediate

What they did
Lumos engineers asked Devin to rework React components that used MUI so they matched the team’s Tailwind styling instead. They gave it a brief set of instructions, added codebase-specific context through Devin’s Knowledge feature, and had it check its own work by running unit tests. After that, engineers looked over the pull request Devin produced.
How it went
The migration turned out well, but the pull request still needed more cleanup before it could be merged. The team believed extra checks during development would likely have caught the remaining issues. In 48 days, Devin created 44 pull requests, and 19 of them were merged.
Tips
For repeatable UI updates, front-load the agent with project rules and let tests steer the changes. Add pre-submit checks so obvious problems are caught before a human review.

Try it yourself with Devin

You are working in [repo name]. Update the React files in [folder path] so they use [current styling library] replaced with [target styling system], while preserving the existing look and behavior. Use the project guidance I give you, and after each component or small group of edits, run the unit tests and fix any failures before continuing. When the change set is ready, open a pull request that summarizes the files touched and any areas that still deserve manual review. Before any irreversible action such as sending, submitting, deleting, or merging, stop and ask for my approval first.

Fill in the [brackets]. Agents can make mistakes, so review anything before it is sent, paid or deleted.

Read the original on lumos.com ↗

Get 3 agent uses like this every morning

With the day's top AI news. Free, and one click to unsubscribe.