UX/UI Design · AI · My own site
Designing a portfolio as a system, with AI as a building partner
My previous portfolio mainly showed what I had designed. It said much less about the work behind it: how I investigate problems, make product decisions and lead designers and teams.
I wanted a portfolio that would help recruiters and hiring managers understand the full range of my work, rather than just see finished screens. I also wanted my CV, case studies and company pages to feel like parts of one experience.
So I treated the portfolio as a product. I designed a shared visual identity, a structure for different kinds of case study and a design system with reusable components. Then I built the website together with Claude.
To work consistently with AI, I documented my positioning, tone of voice, design principles and quality standards. I remain responsible for content, facts, design decisions and publishing. Claude helps me build, translate, visualise and check the work.
The result is a bilingual portfolio with dark and light themes, a CV using the same visual system and a workflow that allows the site to keep evolving without starting from scratch.
- My role
- Designer, product owner and editor of my own site
- Year
- 2026
- Built with
- Claude, HTML and CSS, Git, and Playwright and axe for checks
- Published on
- Netlify
- Languages
- English and Swedish
- Themes
- Dark and light
The short version
The problem
My previous Framer portfolio mainly showcased finished solutions. It made it harder to understand my research, product decisions and leadership. I also needed to bring together many case studies, two languages, two themes and a CV without creating a separate system for each.
My contribution
I owned product direction, information architecture, visual identity, design principles, content and final quality decisions. I designed a shared system and documented the rules Claude would work from. With Claude as a building partner, I developed the site in HTML and CSS, reviewed previews and decided when changes were ready to publish.
The outcome
A connected portfolio showing CX/UX discovery, hands-on UX/UI design, product leadership and design leadership. The site, cases, company pages and CV share one identity. Pages are available in English and Swedish, in dark and light themes. I also established a repeatable way to develop and review content. Accessibility has been checked against WCAG 2.2 AA; that does not guarantee full compliance.
When my portfolio didn’t show the whole of my work
My previous portfolio was built in Framer and focused largely on finished screens. It showed what solutions looked like, but not how I work.
Much of my contribution comes before interface design begins. I research needs, help teams understand problems, prioritise development and enable other designers to succeed. That needed to become visible.
Designing for the person trying to understand my experience
A recruiter or hiring manager should be able to understand my experience without reading every case study from start to finish. They should quickly see the problem, my role and the outcome. Anyone wanting more detail can follow the decisions and explore supporting research, prototypes or service blueprints.
Four goals
- Show the full rangeDiscovery, UX/UI design, product leadership and design leadership, with clear attribution.
- Create one identityThe homepage, case studies, company pages and CV should feel connected.
- Let readers chooseEnglish/Swedish and dark/light preferences should follow people around the site.
- Separate facts from ambitionsReal results, targets, plans and prototypes need distinct descriptions.
The central question was how a portfolio could show how I work, not just what I have designed.
Designing an AI workflow while keeping decisions human
I wanted to develop many pages without writing all the code or rebuilding each component manually, so I used Claude as a building partner. But consistency required me to articulate my standards and decisions more clearly.
Writing down my judgement
I developed shared project documents covering positioning, tone of voice, design principles and a common baseline for every case. A case should lead with its contribution, describe process only when it explains a decision, and distinguish evidence from intended impact. These rules help Claude work consistently, but they cannot decide which facts are true or what matters most from my experience.
Six steps from brief to publication
- 1BriefI explain the problem and requested change, sometimes with screenshots or a review.
- 2ContextClaude works from shared rules, information architecture and design tokens.
- 3DraftChanges appear in a preview, in both languages, without affecting the live site.
- 4CheckAutomated checks cover areas such as accessibility, image sharpness, mobile overflow and A4 layout for the CV.
- 5ReviewI inspect desktop and mobile versions in both languages and themes, and request revisions.
- 6PublishOnly after my approval does the change go live on Netlify.
I own direction, facts, content, design decisions and publication. Claude implements delegated changes in code and content, translates, visualises and supports quality checks.
- What each case should prove, and how it is structured
- What is true, and what is left out
- The visual identity, the principles and every final call
- The written rules: positioning, tone of voice and the case baseline
- Reviewing every change, and saying when it is published
- Writing and changing the code for every page
- Translating every text into Swedish
- Rendering images, diagrams and previews from my direction
- Reviewing cases against my baseline, and running the checks
Nothing ships unseen
A prototype must not be described as a launched service because the wording sounds stronger. Targets must not turn into measured outcomes. AI cannot invent figures to make a story more impressive.
AI made it faster to build and change things. It didn’t make decisions about truth, relevance or quality any less important.
A system for showing different kinds of work
Different case studies need different kinds of evidence. UX/UI work can show prototypes and testing; discovery needs to show how insight changed our understanding; product leadership needs to reveal priorities and dependencies; design leadership needs to demonstrate how people, responsibilities and ways of working developed.
They should not be forced into exactly the same story, but readers should recognise the structure.
Four kinds of work, one foundation
I organised the cases into CX/UX discovery, UX/UI design, product leadership and design leadership. Five selected cases appeared on the homepage, with further work under More problems solved. This provided a quick overview without hiding the detail.
Common questions for every case
What was the problem? What did I contribute? What did the work lead to? Why did we take that approach? What supports the story? A short summary comes first, with detailed diagrams and KPI tables available for people who want to go deeper, including through expandable sections.
- The short versionThe problem, what I did and what it led to, at the top.
- A storyFrom the problem to what changed, with my role made clear.
- Method, then what it boughtEvery method is followed by the risk it removed, the decision it enabled or the result it moved.
- Process at a high levelDeep detail, like KPI tables, sits in closed “More detail” sections.
- Honest outcomesOnly true results. Targets are labelled as targets.
- Proof at the endA short quote from someone I worked with, in a quiet style.
Components that show the thinking
I developed reusable insight cards, decision cards and visualisations connecting user needs, principles, design decisions, product direction and measures of success. These were especially helpful for leadership work where screenshots alone are insufficient.
If the portfolio was going to show how I think, that thinking needed a clear visual form too.
Offers got diners to download the app, loyalty brought them back
From the Leeroy case.
- Discovery insightDiners didn’t know when the order was ready.
- Design principleAlways know the status of the order
- Design decisionOrder status, and a notification when it is ready.
- Product direction“I know when my food is ready”
- Measuring successOrders ready on time
- Decision
- Build ordering first, and loyalty next.
- Why
- Without orders there is nothing to reward.
One visual identity connecting everything
I started from Material 3 and developed my own identity. Colour roles, type scale, shapes, a 4 dp spacing grid and motion principles are captured as tokens, so changes can be carried through the site consistently.
Connecting the CV and the work
Each role in the CV links to a company page and its relevant cases. The same routes are available from the homepage. Readers can move from an overview of a role to the context of a company, and then into the decisions behind an individual case. Tools and Backstage share the same navigation and visual language.
- Designing a portfolio as a system, with AI as a building partner
- My AI design workflow
- Design principles for AI-supported products
Every page: English or Swedish, dark or light, and a sitemap in the footer.


The same identity for the CV
Roboto Flex brings clarity and readability; Instrument Serif provides a personal accent in greetings, keywords and quotes. The palette combines a misty blue with muted rose. The CV and site share the system, and the bilingual CV is checked for A4 layout.
Colour
- Primary
--primary - Primary container
--primary-container - Secondary container
--secondary-container - Tertiary
--tertiary - Tertiary container
--tertiary-container - Surface
--surface - Surface container
--surface-container - Outline
--outline
Type
Language and theme are system requirements
Visitors choose English or Swedish and dark or light. Their preferences persist during navigation. Diagrams, cards and components must work in all four combinations.
Dark · English
Light · SwedishText that remains text
Headings and labels in the hero and other visualisations use actual HTML text instead of being baked into images. They can translate, scale sharply, respond to themes and remain accessible to assistive technology.
Real reusable components
Buttons, chips, tabs, case cards, insight cards, decision diagrams and expandable details use the same code as the live pages. The demonstrations are both examples of the design decisions and tests of the system itself.
The problem
Many users didn’t know they could create a match profile, and those who did struggled with the criteria.
What I did
Research, a clearer five-step flow with personal suggestions, and development-ready design.
What it led to
The share of users with a match profile rose from 30 to 50 percent.
of users have a match profile. From the TRR case.
The service journey
- Hand-inThe consumer leaves the parcel in a locker
- First mileThe driver picks it up
- TerminalIdentified and sorted
More detail: the KPIs we steered by
Deep detail, like KPI tables and dependencies, waits here until the reader asks for it. Try opening it.
“Mikaela made us explore different possibilities quickly, going from an idea to something we can discuss or ship.”
Mattias Björklund · CEO and Co-owner at Bilwebben
Eight principles guiding the work
Show the thinking, not just the screens
Every case shows the problem, my role and the decisions, not only the result.
AskCan readers understand the decisions and why they mattered?
True, or not at all
No invented facts or figures. What was delivered is kept apart from what we aimed for.
AskCould I defend each statement?
One identity everywhere
The site, the cases and the CV share colours, type and components.
AskDo the site, cases and CV belong together?
Let readers choose
Language and theme are the reader’s choice, and the choice is remembered.
AskDo language and theme work for the user?
Built for every screen
Checked down to 320 px, in both languages and both themes.
AskDoes the layout work down to 320 px?
Respect the people involved
Names and personal data in screenshots are blurred, and credit goes where it belongs.
AskIs personal information protected and credit given fairly?
Lead with what it achieved
Every method is followed by what it achieved, for readers who don’t speak design.
AskCan a non-designer understand why it mattered?
Nothing ships unseen
Every change is previewed and checked before it goes live.
AskHave I reviewed both languages and mobile?
Accessibility as part of quality assurance
I use checks including Playwright and axe alongside visual review at different sizes. I check against WCAG 2.2 AA, without claiming formal certification or complete verification of every criterion.
The system’s value goes beyond visual consistency. It makes new work easier to build, understand, review and improve.
What I built and what the system made possible
When documented in 2026, the portfolio included ten case studies across four kinds of work, eight company pages and more than 350 published preview versions during development. Every page had both languages and themes. These figures are a historical snapshot, not a permanent live count as the site grows.
When documented in 2026
case studies, across four kinds of work
company pages, each linked from the CV
languages and themes for every page
preview versions published along the way
The more important outcome is a working system: I can add case studies, visualisations and pages within shared identity and quality standards. I can show research, decisions and leadership, rather than only screens, and examine changes across languages, themes and screen sizes.
I have not reported figures showing that the portfolio led to more interviews, assignments or higher conversion. Those outcomes should not be invented.
What I took away
A portfolio is a product too.
It has users, needs, information architecture and quality to manage.
Rules make AI-assisted work consistent.
I made my quality standards explicit and reusable instead of writing fresh instructions from scratch each time.
Previewing is part of design.
A change can work in one language and theme but break on a phone in another.
AI changes where I spend my time.
When execution gets faster, understanding users, setting priorities and exercising judgement matter even more.
I used AI to build a more comprehensive portfolio, but my design principles and judgement made it a coherent system.
