~/frontend070
Anton Kouliavtsev

$ whoami

Anton Kouliavtsev

I design and build for humans and LLMs.

Freelance UI engineer from The Hague.

cat services.mdContact

$ git log --teams-worked-with

∞ commits pushed

$ diff before.md after.md

Every project, same story

The web is shifting under everyone's feet. It used to be the marketeer editing the dev's page. Now it's an LLM. Same problem, faster.

--- WHAT I WALK INTO

  • - Each prompted page invents its own buttons, spacing and shade of blue.
  • - There are no UI rules, so every edit is a matter of taste. The LLM has none.
  • - Your marketing is optimized for Google’s ten blue links. Your customers are asking ChatGPT.
  • - Someone sits there prompting, waiting for the LLM, prompting again. Babysitting is the new bottleneck.

+++ WHAT I LEAVE BEHIND

  • + A design system with conventions both humans and LLMs follow.
  • + Your team prompts new pages, and they come out on-brand.
  • + Content structured for both: ranking on Google, cited by LLMs.
  • + Agents work while you're away. You come back to finished work, ready to review.

$ ls services/ --one-person

What you can actually hand me

Five things I do well. If your project is mostly one of these, we'll get along.

  • 01

    Marketing sites for SaaS teams

    Landing pages, blogs, docs. Built in Astro or Next.js so your marketing team ships pages without filing a dev ticket. This is most of my work, and the part I’m best at.

  • 02

    Sites that LLMs can cite

    Your customers ask ChatGPT, not just Google. I structure your content so it ranks in one and gets cited by the other.

  • 03

    AFK agent workflows

    Stop prompting. I connect Claude Code to your repo and set up agents that draft content, fix papercuts and open PRs while nobody’s at the keyboard. You review and merge.

  • 04

    Product UI in Next.js

    LLMs are still bad at UI: no rules, no taste, and taste is hard to teach. Dashboards, onboarding, forms that don’t lose your input. This is where a human frontend engineer still earns their rate.

  • 05

    Design systems for humans and LLMs

    I set up tokens, components and UI conventions that both your team and your AI tools follow, so prompted pages come out on-brand instead of almost-on-brand.

$ cat stack.json

The stack

Boring where it should be, modern where it pays off.

Build

Astro · Next.js · Tailwind CSS · Storybook · HTML5 · CSS

I wrote SMACSS and BEM before Tailwind. Good times. Still the same goal: CSS that scales.

Content

Markdown · TinaCMS · Mintlify · Headless CMS

Editors get a friendly CMS, the repo stays the source of truth. Already on another headless CMS? That works too.

Ship

Vercel · Netlify · GitHub · Supabase

Preview on every push, deploy on merge. Something off? Rolled back in one click. Need a database, auth or forms behind the site? Supabase.

Design

Paper · Figma

I design in Paper (paper.design), an MCP-first design tool. Figma when your team lives there.

AI workflows

Claude Code · Conductor · Skills & MCP

My favourite part: I set up AFK workflows for my clients. Agents that draft content, fix papercuts and open pull requests while nobody is at the keyboard. You review, you merge, you move on.

$ ./ask --anything

Frequently Asked Questions

$ ./contact --new-project

Let's work together

Don't like forms? Send me an e-mail. The full menu: concept, design, development, or any slice of it.