MJ PORTFOLIO — AI_PORTFOLIO_BUILDDO NOT SCALE · ALL DIMENSIONS IN PIXELSLOCATION: MELBOURNE_AU
CS_008 · UX/UI · Web Development · 2026

AI Portfolio Build

UX/UI · Web Development · Agentic AI
RoleDesigner, Content Strategist, AI Orchestrator, Developer
TimelineMarch 2026 · 2 weeks concept to live
ToolsClaude · Claude Code · Copilot · Next.js · Sanity · Vercel · Figma · Git
ScopePortfolio website · 9 case studies · CMS · Live deployment
TL;DR

A fully custom portfolio website designed and built collaboratively with AI agents, from content strategy and UX through to a live Next.js + Sanity CMS deployment. Concept to live site in under 2 weeks.

AI Portfolio Build

This portfolio site is itself a case study, built to demonstrate what a designer with 13+ years of experience can produce when AI agents are used as genuine collaborators across every phase of a project. The challenge was building a high-quality, production-ready portfolio without a development team, a large budget, or weeks of spare time. Using Claude for strategy and content, Claude Code for development, and Copilot for in-editor assistance; the entire site, design system, 8 case studies, CMS integration, and live deployment, was completed in under 2 weeks alongside full-time employment.

< 2 WKS
Concept to live
9
Case studies
10+
Tools & AI agents

Building a portfolio that accurately represents 13+ years of cross-disciplinary design work, UX/UI, industrial design, retail spatial design, and CRO, typically would've required a developer, a designer, a copywriter, and weeks of production time. The constraints here were real: no development team (though I did get help and support from a developer friend), no extended timeline, and a need to present complex, multi-discipline work in a single coherent website. The question was whether AI agents could genuinely replace those missing collaborators, not just generate "Thought Leadership"", but actively contribute to decisions about structure, content, design, and code.

Pain Point 01
13+ years of cross-disciplinary work across 4 design practices needed a single coherent content system, not a generic portfolio template with copy pasted in.
Pain Point 02
No development background, no team, and a 2-week window alongside full-time work, the build had to be highly efficient with zero wasted effort.
Pain Point 03
AI tools needed to function as genuine collaborators, making real decisions about architecture, content, and code, not just autocomplete assistants.

Research focused on two questions, what makes an effective portfolio for senior design roles, and what AI-assisted workflows could genuinely replace traditional production processes. Competitor portfolios across UX, industrial, and CRO disciplines - In conjunction with open bar sessions with my peers - informed the content structure and case study depth. The orthographic drawing aesthetic, sticky left column layout, and modular block system all emerged from this research phase, developed in conversation with Claude across multiple sessions before a single line of code was written.

Research
Claude conversation · Design system and content architecture developed before any code was written

The process was deliberately sequenced, content before code, structure before styling, each phase validated before the next began. Claude acted as the primary collaborator across strategy, content, and design decisions. Claude Code handled all development. A friend (frontend developer) assisted with initial deployment and education on how each system would talk to each other and deploy the website. The entire workflow ran across two platforms, Claude.ai on MacBook for content and design, and Claude Code on PC for development and launch.

01
Design System & HTML Prototypes
Design system established first, Manrope typeface, teal/dark/white palette, orthographic aesthetic, sticky two-column layout. Three HTML files built as pixel-perfect templates, homepage, about, and universal case study template, before any framework was chosen. These became the source of truth for the entire build.
02
Content Architecture
A modular block system designed across 18 optional case study sections, each block activated or deactivated per project via an ACTIVE BLOCKS table. 8 case study content documents produced in a structured PLACEHOLDER to VALUE format, ready for direct CMS population without interpretation. All content written collaboratively with Claude across multiple sessions.
03
Next.js + Sanity Scaffold
Claude Code scaffolded the full Next.js App Router project, Sanity CMS schema, GROQ queries, and component library, reading the HTML templates and .md content documents as source of truth. A seed script auto-populated all 8 case studies and uploaded all image assets to Sanity in a single run.
04
QA, Amendments & Deployment
Local QA across desktop and mobile, layout fixes, content amendments, and conditional rendering logic all applied through Claude Code without manual code editing. Deployed to Vercel via GitHub with Sanity CORS configured. Live in under 2 weeks from first conversation.
Process
Claude Code · Scaffolding the Next.js project and Sanity schema from HTML templates and .md content documents
HTML prototype
HTML prototype · Design system and case study template built before framework selection
Sanity Studio
Sanity Studio · CMS populated automatically via seed script from .md content documents

A production-ready portfolio site built on Next.js App Router with Sanity CMS, deployed to Vercel, fully content-managed, and built entirely through AI-assisted workflows. The site presents 8 case studies across 4 design disciplines in a single coherent design system, with a modular block architecture that adapts to each project's content without custom code per case study.

AI-First Workflow
Claude acted as strategist, copywriter, and design collaborator across the entire project. Claude Code handled all development. No manual code editing, every change was applied through natural language prompts with the HTML templates as source of truth.
Content Before Code
All 8 case studies fully documented in structured .md files before development began. Each file contained an ACTIVE BLOCKS table, exact placeholder-to-value content mappings, and an image manifest, giving Claude Code everything needed to populate Sanity without interpretation.
Modular Block System
18 optional case study blocks, stat strip, insight cards, personas, experiments, materials, product range, tech stack, YouTube embed, and more, each conditionally rendered based on Sanity field population. One template, infinite flexibility across disciplines.
Live CMS Deployment
Next.js App Router + Sanity CMS deployed to Vercel. Content editable through Sanity Studio without touching code. New case studies added via CMS only. Images updated instantly. Site scales indefinitely without a developer.
Solution
Live site · mj-folio-2026.vercel.app · Next.js + Sanity + Vercel
Claude (claude.ai), Strategy · Content · Design · Case study writing · Decision-making
Claude Code, Full Next.js scaffold · Sanity schema · Component library · Seed script · QA fixes
Microsoft Copilot, AI image generation for hero assets · Reference image creation
Next.js (App Router), Frontend framework · Dynamic routing · Server-side rendering
Sanity CMS, Content management · Image pipeline · Studio interface · GROQ queries
Vercel, Deployment · Hosting · GitHub integration · Auto-deploy on push
Git + GitHub, Version control · Source of truth · Vercel deployment trigger
Visual Studio Code, Local development environment · Claude Code interface
Figma, SVG asset creation · Operating model diagrams · Zone overlay graphics
Adobe Creative Suite, Image editing · Export · Optimisation for Sanity upload
HTML · CSS · Markdown · TypeScript · GROQ

A production-ready portfolio website, live at mj-folio-2026.vercel.app, built in under 2 weeks alongside full-time employment, with no development team and no prior Next.js experience. 8 case studies across 4 design disciplines presented in a single coherent system. All content managed through Sanity CMS, deployable without touching code. The build demonstrated that AI agents can genuinely replace traditional production roles when used as structured collaborators rather than autocomplete tools.

Key Outcome
Concept to live deployment in under 2 weeks, a fully custom Next.js + Sanity portfolio built entirely through AI-assisted workflows, with no development team, no manual code editing, and no prior framework experience.

The most important lesson was that AI agents work best when given structure, not open-ended prompts. Every phase that went smoothly had clear inputs: - HTML templates as visual source of truth - Markdown (.md) files as content source of truth - Explicit ACTIVE BLOCKS tables, to exact placeholder mappings. Every phase that needed rework was where those inputs were missing or ambiguous. The second lesson was sequencing, content before code, structure before styling, one validated phase before the next. If I were to do this again I'd invest even more time upfront on the content documents before touching Claude Code. The seed script that auto-populated all 8 case studies in Sanity was the single most time-saving moment of the entire build, and it only worked because the .md files were structured precisely enough for Claude Code to parse without guessing.