Digital Gardendesign-directionaiportfolio

Making-of: An Island Instead of a Project List

My portfolio used to be a list of projects behind a nav bar. Now it's an island you can walk around: my work, a rollercoaster, a cinema and a sauna, built in 28 days with Claude as a small studio. Why, and how it came together.

It started with an anticlimax. My website had just been optimised so that AI agents, AI recruiters and automated CV scanners (ATS) could read it properly. Then came the question: who was all this for? Where's the human in this? Where's the fun?

So the next question went to Claude: could we have some fun with Three.js, a 3D framework that had been on my list for a while, using the same data as the website so we wouldn't build a second silo?

28 days later, my portfolio isn't a list of projects behind a nav bar any more. It's a place you can walk around in, with my work and a lot of what makes me who I am. Nobody scrolls through it. You get a bit lost and stumble on things, which is closer to how people get to know each other anyway.

Why now

The job market is tough right now. There are fewer openings, more people apply for each one, and everyone is racing to have the most machine-readable CV and the most optimised portfolio, written for the applicant tracking system first and for people second. My CV still plays along. My portfolio doesn't have to.

When things are hard, I try to look at them with some humour (the sad clown paradox, if you like). So rejections go into a bonfire and come out as vegetable skewers, and my job search has a sauna.

I also decided to treat the island as a life project, not a campaign. Something I can come back to in ten years, or show my kids one day. Something I'd be happy to have as a QR code on my gravestone. It works as it is and runs on my own server. It can keep growing, but it doesn't have to. And it isn't only about what I've done. It also shows the future I'd like to live in: shuttles, bikes and a train instead of traffic, rejections that turn into something warm, accessibility you can taste.

Why an island

A place I own. It belongs to me. It isn't a profile on someone else's platform with someone else's layout and rules. It's the same reason I avoid vendor lock-in in client work.

Personality. The sauna and the rollercoaster are there on purpose. A CV can't show what it's like to spend time with someone. A place where you can hang out can.

Something to remember. You remember a place you've explored better than a page you've skimmed, and that's what people talk about afterwards.

A filter. It takes a few minutes. That's on purpose. On LinkedIn I put it like this:

The experiment is that I want to find a company that appreciates this – not one that only takes two minutes.

— Phil, on LinkedIn

The result is Visit Phil: a small 3D island with five districts, stalls for my projects, a ring railway, residents who answer back. Rather walk through it than read it.

days, 14 Oct to 10 Nov 2026
28
commits on the island
~820
lines of code (as of 6 Nov)
61k
workshop sections in Figma
74

On the busiest days, 103 commits went in, and almost every one started as a picture in Figma.

The idea in one sentence

It started with a note in Figma: “Explore mode – a calm walk through the portfolio. An inconspicuous entry, the same data as the site, the same components – just as an island.” Five principles were there on day one: entry via a small pill in the footer, a low-poly diorama with industries as districts, walking and a ring railway, generative sound (muted by default), and consideration – if you've turned on reduced motion, you get a calm map from above.

The first concept sketch: “Explore mode”

Figma 17 · 14 Oct 2026
  1. First commit: “a calm Three.js portfolio island”
  2. Arrival by plane, painted in the company's colour
  3. The big component gets taken apart
  4. Empathy Gym, Figma audit and ticket model
  5. Mountains: a volcano, a rock needle, a peak

The website is the foundation

The island didn't start from an empty scene. It started from this website. Every section got a place: About is my loft with the terrace desk, every case study is a stall in one of five districts – its persona explains it –, Services is the Amt (German for a government office), and the garden is the camp, where the newest notes lie on the reading benches. Sit down, and you read the same note that's on this site.

Underneath both sits one source: the Markdown files for case studies and garden notes, the same APIs, the same design tokens and components, the same German and English texts. When I publish a note, it shows up on a bench without anyone touching the island. It works the other way round too: a line like the one below takes you from an article straight to its place on the island.

One source, two ways in: every section of the site has exactly one place on the island

WEB-005 · 9 Nov 2026
See it on the islandCamp & cowork

The camp on the quiet west side – sit on a bench and read.

3D · sound off · 2 min.

The frame and the arrival

The first big decision was the frame around the 3D world. Out of four variants I picked the one where the glass bar at the top is the menu: it drops down and shows the website's sections as places on the island, the island pass and the map. One bar instead of buttons in every corner.

HUD and game menu, variant D: “The bar is the menu” – picked and built

Figma 30.D · 21 Oct 2026

Then came a backlog of 50 small concepts, sorted by MoSCoW (must, should, could, won't), with a one-line brief:

Weapons, loot boxes and open chats with strangers ended up under Won't. Maté instead of beer.

When I invite a company, I want them to arrive somewhere instead of landing on a list. Of three ways to get there, we built the offshore runway: the plane is painted in the company's colour, and I pick you up with the camper. The invitation itself is a boarding pass with a view out of the window, “Seat 1A – Window” for flights and “Deck – Porthole” for the ferry. The island also got one picture language in three directions (diorama, travel poster, hiking map) for the banner, the menu, the boarding pass and the share images.

Invitation and picture language

  • Boarding pass with a window view
  • One island- three picture languages

The letter comes first

The first feedback that really changed something came from former managers. Their point: the people who decide about a hire often have two minutes, not twenty. If the first thing they see is a loading 3D world, many of them are gone before the island stands.

So now a letter comes first. Before the island starts, a message in a bottle opens on the start screen. For an invited company it's written for them: why I'm interested in exactly this role, which projects to look at first, and a tour that starts with those. An AI drafts it from the job listing, and nothing goes out before I've read and approved it. Right in the letter you can download my CV and my portfolio as a PDF. You can stop there and have everything you need. The island is an invitation, not a gate.

Getting there took a while, because I kept trying to squeeze the essentials into the 3D world: signs, a desk, a menu. The bottle letter already existed for invitations, so it only had to show up before the world instead of inside it. Public visitors now get one too, from me, explaining what the island is.

People who answer back

The stalls don't explain themselves with text panels. Every project has the people it was built for standing around it, and you can talk to them. They answer from the case study, in their own voice. Mini-Phil, the island's guide, can take you on a tour, and the camera frames each stall straight on when you stop.

The voices went through a few rounds: from one text-to-speech service to another and, as a fallback, the browser's own voices. Some characters got very specific: Gianna on the ice-cream bike has a clearly Italian accent. My own voice is cloned, and the island says so before you hear it.

Every one of these characters wears an "AI" badge. If a portfolio uses AI to talk to you, you should know when it does.

The tour changed most. At first Mini-Phil cycled you down the whole pier, only to stop at its foot and ask whether you'd like a tour or to wander. Now he waits where you step off, the choice comes right there, and the tour hands out shared bikes for the way between stops.

Two ways to play, and a phone

There are two kinds of visitors, and they need opposite things.

The first group are recruiters and hiring managers, many without any gaming background. They should get the whole experience without touching anything. So the island has a guided tour that runs on its own: Mini-Phil walks you to three stalls (for an invited company, the projects that fit their role come first), and for longer distances you both get on shared bikes. At every stop he reads out a short card, and at the end you get my CV and a way to contact me (plus the portfolio PDF, if you were invited). You can lean back and watch.

The second group want to explore. For them it's the controls everyone already knows from games: WASD or the arrow keys to move, E to interact, Space to jump. No tutorial needed.

Most recruiters will probably never open it on a phone. It still has to work well there, presentations at the stalls included, because links get forwarded and opened on the train. On a touch screen a joystick and a few buttons appear, the bar at the top shrinks to icons, and the island's phone sits on the visible screen above the controls. The island also measures itself and turns its quality down on weaker devices. Claude can't test on real phones, so a small measuring overlay (frame rate, draw calls, quality level) lets me check on my own devices and send the numbers back.

How we worked

I worked as the design director. I set the direction, picked from variants, combined them and cut a lot. Claude worked like a small studio: three variants in Figma and a recommendation, then building, testing and documenting.

This is how it went for one small feature, from the first sentence to the commit. Almost everything on the island went through the same four steps.

1 · A sentence, not a spec

Four beach towels east of the pier had my services printed on them: accessibility, human-centred AI, sustainable web, collaboration. Nobody found them. You saw them flat from above and read fragments. My whole brief was this:

The beach towels don't get enough attention. Maybe we need someone who sells them at the beach – make 3 variants.

— Phil, the brief

2 · Current state, three variants – and a pick

Claude put the current state and three directions into Figma, each with a top view (north up), the in-game view, how it would feel, pros and cons, and the effort. I rarely took a variant as it was. Here I took two of them. Tap a picture to see it full size.

Decision

How do the beach towels get attention?

Why

The vendor gets a stand with a washing line (B, readable) and calls out from there when you're on the beach (A, attention) – without chasing you. C stays an idea for invitations, as a one-off moment.

ISL-083 · 4 Nov 2026

3 · Build, look, adjust

Then it got built: a stand with a washing line and a kiosk – “Beach towels, on offer today” – and a vendor with his own voice. He calls out when you're within 16 m, every 11 seconds, four times at most, and never while a card is open. Talking to him opens the towel as an ad, with a close-up and “Next towel →”.

The first look in the game always brought a second round. “On arrival the stand shouldn't be there yet” – so it appears 20 seconds after you're free to walk. “Now it collides with the intro scene – maybe move it a bit further away from the pier” – so it moved east, behind the flags.

4 · Write it down

After every feature, the notes get updated, the tests run, and the ticket in Figma gets its “as built” section. It felt like overhead at first. Three weeks in, after the first context resets (Claude's long sessions get summarised and details drop out), it was what kept the whole thing together.

When none of the variants is it

Sometimes the answer wasn't one of the variants at all. For the rollercoaster I wanted a corkscrew through the mountain; every variant came with a top view, a cross-section, “what happens in the code” and effort / impact / risk. In the end we didn't drill through – we put karst mountains next to it.

Rollercoaster – the corkscrew through the mountain. Replaced by ISL-080, the karst mountains

ISL-079

Short messages, open questions

My messages were often just a few words, German and English mixed, and liked to end with “what do you think?”. I did that on purpose. A question gets you a counter-proposal. An instruction just gets carried out.

From the conversation · shortened, translated
  1. Phil

    It could also be an ice-cream stand … because several colours.

  2. Claude AI replyAbout this replyThis message was written by an AI (Claude) in a conversation with Phil and is quoted, shortened, as part of the story. It is labelled to be transparent about AI-generated content, in line with the EU AI Act's transparency obligations.Learn more

    Every flavour a perspective – and a waffle pass as a stamp card.

  3. Phil

    Or once you've been to the ice-cream stand, you have the app on your phone.

That's how the Empathy Gym came about. Why an ice-cream stand, of all things, is below.

Empathy Gym, round 3: the ice-cream stand is the entrance

ISL-084

Why an ice-cream stand

I sell accessibility audits, and I've seen what changes people's minds. A list of WCAG criteria rarely does; five minutes of not being able to read a sign usually does. You can describe a barrier, but people take it seriously once they've run into it themselves. That's what a 3D world is good for: you're inside it, walking to the next stall while your field of view narrows, or crossing a square while a crowd slowly closes in.

The ice cream is the way in. Nine flavours, nine perspectives: colour blindness, tunnel vision, hearing loss, tremor, dyslexia, cognitive load, motion sensitivity, glare and agoraphobia. A colourful cargo bike is easy to walk up to, and nobody feels lectured by an ice-cream seller. Every flavour ends with "what helps" and the WCAG criterion behind it, so the feeling turns into something a team can fix.

There are guardrails. A simulation isn't someone's life, and the island says so before the first scoop. One perspective at a time, you can stop whenever you like, nothing flashes, and reduced motion is respected.

It also found a real barrier on my own island: the containers at the harbour could only be told apart by colour. They now carry a symbol and a word, and the rule it left behind applies everywhere: never colour alone. The whole story has its own post, the next one in this series.

DesignOps: the same page every time

With dozens of tickets in flight, the format turned out to be the most useful design tool. Every ticket in Figma looks the same, and it's complete before I look at it:

  • a header with the ticket ID, the status (in progress, built, parked) and the area it touches
  • what it's about, in my own words and with the date, for example “the notifications are covered by the small video player – what would be more elegant?”
  • the current state: screenshots from the real build, what happens there, and the guardrails no variant may break
  • three or four variants, each with pros, cons and the effort
  • a recommendation with its design rationale, and the questions only I can answer

So I never review a picture without the reasoning behind it. I can disagree with the rationale, but I don't have to reconstruct it. And when none of the variants fits, my own idea goes onto the same page as one more variant, with the same pros and cons. For the mini player that's what happened: my idea came in as V6 and became the recommendation.

One ticket, always the same order: brief, current state, variants with pros and cons, recommendation and questions

ISL-107 · 10 Nov 2026

The page list in Figma doubles as the backlog, with a status in front of every ticket. After the build, a ticket gets an “as built” note with the commit, and a ticket index in the project documents keeps track of all of them. That way the next session, or Claude after a context reset, can pick up where the last one stopped.

Director's cut: what I decided by

Looking back, I kept deciding by a few rules, mostly without saying them out loud.

One thing at a time. When you arrive, the beach vendor's stand isn't there yet. The arrival is about the pier and the welcome. Everything else comes later.

Space like a landscape architect. “Let the canal meander a bit, less straight”, “a tree is blocking the Double Diamond sign here” – I treated paths, sightlines and squares like in a real city.

Combine and be pragmatic. “B is easier to build, right?” The variant with the most effect for the least effort wins. The more spectacular one stays in Figma as an option.

Iterate until it's right. “A few more variants that are more sleek, maybe light/dark too.” The first version that works is rarely the best one.

Cut things. More features don't automatically make more island. There's a whole section on that below.

An example of the whole process in miniature: the ice-cream selection was a list at first. I wanted something with flying waffles. Of three variants I took the floating carousel in the card – the effect at half the effort, and it works on every phone. Halfway through building it came the idea of turning the stand into a cargo bike.

From Figma to build

  • Figma three variants
  • Built ice-cream cargo bike with Gianna
  • Built waffle carousel

Diverge, converge, cut

At some point my partner looked over my shoulder and said: “Phil, it's getting too much.” She's not wrong about what you can see. What you can't see is everything that went out again.

The process diverges twice and converges twice. In Figma it goes wide first: three or four variants per ticket, over 120 tickets, so for almost everything on the island there are two or three versions that never got built. Then I pick or combine. After the build it converges again, because some things only look wrong once you stand next to them in the game.

Some of what got kicked:

  • A Scrum poker casino, built and removed.
  • A pastel promenade with art-deco kiosks east of the pier. Too developed and touristy for the island. Reverted the same day.
  • A natural sea arch the seaplane flew through on arrival. It looked unnatural. Sea stacks and three small islets took its place.
  • Everything with alcohol, including a fridge of alcohol-free beer and a seagull drone that stole it from you. Maté stayed.
  • A cinematic arrival with letterbox bars and a location card, and a big “stall visited!” banner. Both too much.
  • A minimap in the corner, a sandbank, the first home hero, a whole neighbourhood called Ocean Drive. Built or planned, then gone.
  • A mountain ridge that would have buried the slide and the stream. It became a rock needle with two hanging bridges.

In numbers: since mid-October about 230,000 lines went into the site and island, and about 85,000 came out again. The island's central component went from around 14,000 lines to under 7,000.

Small on purpose

On GTA VI's release day (19 Nov 2026), people are clearing space for a download of reportedly around 210 GB. My island needs about 2.2 MB until you're standing on the pier, measured on the live site, website included. The island has no 3D models and no textures. Everything is built in code from simple shapes: the houses, the trees, the volcano, the people. That keeps it small, it loads on a phone, and every change is a commit instead of an export from a modelling tool.

One person, many roles

I worked as a UX designer for years. On this project I was creative director, DesignOps, DevOps and developer at once, with Claude doing the studio work in between.

That leaves me with a question I can't answer yet: what happens to highly specialised roles that only cover one step of the chain? Handovers were always where things got lost, between research and design, design and code, code and operations. If one person can now hold the whole chain, the handover becomes the bottleneck rather than the craft. I don't think specialists will disappear. My guess is that the ones who also understand the steps around them will have an easier time than the ones who only work inside their own.

Since then

After the first 24 days I kept working the same way, but the questions changed. Where does a cave fit under a cliff that already has a bunker and a rollercoaster tube inside it? How much room do two sailboats need? What's beyond the buoys? That became spatial planning, and it has its own post in this series: Planning space.

What got stuck

Quite a lot, to be honest.

Placing things without eyes. Most of my feedback was spatial – “the loungers a bit to the left”, “it collides with the intro scene”, “the stand needs to move forward a bit”. Claude places objects via coordinates in code and only sees the result through screenshots from a headless browser. That cost extra rounds. What helped: plans in Figma before building, and fixed screenshots from the player's perspective.

Mistakes. Once Claude claimed a map only distinguished red and green – it didn't. Characters faced the wrong way. Code accessed the world before it existed, and the island fell back to the calm map. Claude also once shrank the site address in the HUD to “Website” and generated a share image of me that looked like AI slop – both went straight back out. Nothing serious, but it all cost time.

Going back. Some things were reverted: the first home hero, an Android viewport lock, a half-finished commit.

The monolith. The central island component grew to around 14,000 lines before it was taken apart. Every new idea landed there first, because that was where everything was within reach. It was split in two rounds (27 October and 3 November) into around fifty small composables (reusable code modules), one per system like arrival, rides or the phone, and is now under half its size. Since then, a new feature starts as its own building block.

Tool limits. Claude can't hear the voices and can't test on real devices. The dev server dies after time limits, Figma images can't be downloaded from the sandbox, GitHub rejected a push once. Long sessions run past the context limit and get summarised, and details get lost. What helped was keeping project documents: a design system, a ticket index, decisions in Figma.

What shaped the island

Most of the rules are in the sections above. A few more:

  • Accessibility: the website to WCAG 2.2 AA, the island's interface to AA, the 3D world following the Game Accessibility Guidelines, and the website as an equivalent alternative.
  • Real photos instead of illustrations in the share cards, and one accent colour for everything.
  • Icons instead of emojis on buttons: emojis look different on every phone and can't take on the interface's colours. They stay where they are content: reactions, stamps, the residents' homes.

The island also has its own flag, a fifth mast next to DE, NL, ES and the EU, and a constitution you can read and sign on the beach. Every design for it had to work without colour, the rule from the Empathy Gym. Article 4: A rejection is not a verdict on you.

The island's flag: three designs, each checked in greyscale

ISL-086 · 6 Nov 2026
See it on the islandThe island · Constitution

Read the constitution on the beach – and, once you've moved in, sign it.

3D · sound off · 2 min.

Favourite details

  • The rejection bonfire: you throw a rejection into it; every five turn into a vegetable skewer.
  • The bunker gallery under the cliff: twelve lit display cases full of UX and product fails, with a Mini-Phil tour if you like.
  • The boarding pass in the portfolio PDF with a window view of the island.
  • Agoraphobia in the Empathy Gym: a crowd that slowly closes in around you – but a way ahead always stays open.

What I'll do differently next time

  1. For spatial work, a plan in Figma early on and a fixed screenshot path from the player's view.
  2. New features as their own building blocks right away, not in the monolith first.
  3. Record decisions as a ticket with a decision record from the start – that only came after three weeks.
  4. Keep project documents up to date continuously, so knowledge doesn't disappear into the conversation history.
  5. Voices and devices as a fixed sign-off by a human.

Walk there yourself

The island is open: Visit Phil. If you'd rather read, stay here. The website is always one click away. Next in this series: the Empathy Gym, then how the island learned to plan space.