Built a single-page IBM Carbon bento-grid portfolio with Claude Code
Takeaway: Next time I'd give the exact copy (song, project URLs, email, usernames) up front instead of patching them in one by one at the end — that ate a lot of turns.
Takeaway: Next time I'd give the exact copy (song, project URLs, email, usernames) up front instead of patching them in one by one at the end — that ate a lot of turns.
Takeaway: Next time I'd just ask it to check whether the project even needs a build step before touching vercel.json — that's the fix that actually mattered, not the plugin install.
Takeaway: Next time I'd specify target screen sizes and content lengths up front, since the ABOUT overflow only showed up once I actually looked at the rendered page.
Takeaway: Next time I'd give the full spec plus real breakpoint screenshots up front instead of discovering overflow and mobile issues one screenshot at a time — that back-and-forth on the projects grid alone took five different layout attempts before landing on the paginated 3-column version.
Takeaway: Next time I'd just tell it upfront that the site is a static root-level app with no bundler dependency, so it doesn't waste time inspecting main.js and package.json to figure that out.
Takeaway: Next time I'd point the agent straight at the correct working directory path up front — it burned a lot of turns just figuring out where the project actually lived across Bash and PowerShell.
Takeaway: Next time I'd say upfront whether I want an interactive prototype or actual drawn sketches — the back-and-forth over 'нарисуй эскизы' vs the HTML mockup cost real time.