I built my portfolio with Claude Code. Here is what I decided myself
I rebuilt my portfolio with Claude Code. The AI wrote a good part of the code. Every decision that mattered was mine. I am sharing this for anyone who thinks AI tools do everything on their own. They do not. Someone still has to know what to build, what to measure and when to say no. The stack TypeScript, React 19, Next.js 16 (App Router), Tailwind CSS 4 and Framer Motion, deployed on Vercel with…
The author rebuilt their portfolio using Claude Code, but emphasized that every important decision was made by the human. They used a stack of TypeScript, React 19, Next.js 16 (App Router), Tailwind CSS 4 and Framer Motion, deploying on Vercel with their own domain. Key aspects the author decided on were a clean design with minimal widgets, a rigorous audit process focusing on SEO, accessibility and performance, and implementing features like a pause control for auto-rotating carousels and proper SEO metadata.
The author highlighted the importance of measuring the impact of changes before implementing them. After trying a CSS-only speed-up for the hero, they found no significant improvement according to Lighthouse, so they reverted the change. This illustrates the principle that while AI tools can suggest modifications, the human must evaluate their effectiveness.
In terms of performance metrics, the author reported that desktop and mobile versions of the site scored 99 and 89 respectively in Lighthouse production tests, with 100s in accessibility and best practices categories. They stressed the importance of adhering to best practices and keeping the design simple.
The author concludes by sharing their own live site and other work, implicitly encouraging readers to consider these principles when creating their own portfolios.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
This story
This is one outlet's version. Read the fullest account.
