How to use Gemini to modernize a React frontend
Gemini began a phased Vite and TypeScript migration of ajfisher's React frontend, but quota exhaustion and a fallback loop left the larger task incomplete.
Original prompt
Shared by the source author. See source notes for context.
look at the front end and suggest 3-4 high value improvements
Reach people exploring AI agents
See placements →What happened
A useful partial frontend modernization stopped during phase two when request limits and a model-transition loop interrupted the larger migration.
Reported by ajfisher on BlogHow the agent did it
- ajfisher supplied the Vite, React, TypeScript and CSS-module migration requirements.
- He approved phase one and separately advanced the next phase.
- Useful refactoring stopped when request limits and a model-transition loop interrupted work.
Where a person stepped in
ajfisher supplied the migration brief and explicitly advanced the agent from one phase to the next. He stopped when quota transition caused a persistent loop.
ajfisher tried Gemini CLI on a legacy frontend he had postponed modernizing. After smaller requests to explain files, recommend improvements and refactor a component, he supplied a larger brief: create a new Vite project using React and TypeScript, replace Styled Components with CSS modules and remove react-redux.
Gemini produced a phased plan. The author approved the first phase, which established the new project structure, then explicitly moved it into the second. He describes a methodical conversion approach and useful refactoring before the session encountered service limits.
A too-many-requests response first looked like a brief rate-limit problem. Continuing then exhausted the available Pro allowance. The CLI's transition to Flash became stuck in a persistent loop, leaving the broader migration incomplete. The account distinguishes the solid work already performed from the lack of a graceful recovery mechanism.
The result is a partially completed frontend modernization, not a shipped replacement application. The source also records the author's decision to keep smaller assignments under his orchestration. Its quota observations describe that particular launch-period session; they do not establish present-day Gemini limits or a dependable budget for reproducing the task.
Prompt
Original prompt
Source: Blog · ajfisher
Frequently asked questions
What modernization was requested?
Vite with React and TypeScript, CSS modules and removal of react-redux.
Was the migration finished?
No. The session was interrupted during phase two.
What failed during recovery?
The reported transition from Pro to Flash became stuck in a persistent loop.
More details
About this account
Gemini produced a phased plan. The author approved the first phase, which established the new project structure, then explicitly moved it into the second. He describes a methodical conversion approach and useful refactoring before the session encountered service limits.
Primary firsthand account opened. Migration only partially completed before quota and fallback issues. Original prompt excerpt is a smaller evaluation request shared in the same session, not the full migration brief. Historical limits are not current product guidance. Original prompt excerpt retained from the source.
Credit: ajfisher on Blog
Source published 26 Jun 2025
Source checked 14 Oct 2026
Tools and topics
Gemini CLI · React · Vite · TypeScript
Frontend migration · Quota interruption
Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.