---
title: "Designing for whatever my agents and I build next"
url: "https://sarthakmishra.com/library/blog/designing-for-whatever-my-agents-and-i-build-next"
description: "How I made sure my next idea would feel at home alongside the rest of my work. The trick was deciding which design choices my agents could carry forward."
image: "https://sarthakmishra.com/og-images/blog/designing-for-whatever-my-agents-and-i-build-next.webp"
---

[View HTML](https://sarthakmishra.com/library/blog/designing-for-whatever-my-agents-and-i-build-next) · [Site index](https://sarthakmishra.com/llms.txt)

# Designing for whatever my agents and I build next

How I made sure my next idea would feel at home alongside the rest of my work. The trick was deciding which design choices my agents could carry forward.

![Split-screen article page about replacing Tailwind with plain CSS, shown in light and dark themes.](https://sarthakmishra.com/assets/designing-for-whatever-my-agents-and-i-build-next-hero-D-xUq4X2.jpeg)

I want the tools I build with coding agents to feel related, even when they look quite different. I also want the freedom to try a weird layout if it suits the tool.

So how much do they actually need to share?

My portfolio was a good place to find out. I still like the old site. It worked well for a few static pages about me and my work. But I’m starting out as an indie hacker, and I’d like someone who finds one thing I’ve made to have an easy way to find the others.

![The original Home page, with a blue robot beside a large serif heading, monochrome navigation icons down the left edge, and venture cards below the introduction.](https://sarthakmishra.com/assets/home-original-DUCsC7Or.jpeg)

The old Home page, before I started experimenting with the dock.

## Give the dock a job

The dock gives each page or tool a place in the navigation. An icon can open a page on my portfolio or a whole other site. Search and the theme switch can live there too.

I started building it in OpenCode. With those controls in the dock, I could design each page around what you’d do on it.

![Home inside a desktop-style workspace, with a black frame, a top bar containing navigation and a clock, and colorful app icons down the left.](https://sarthakmishra.com/assets/home-workspace-Dko0rt7D.jpeg)

![The same Home page with the window frame and title bar removed, leaving a narrow dock of colorful icons down the left edge.](https://sarthakmishra.com/assets/home-dock-562UdKUw.jpeg)

I kept the dock and removed the window frame and title bar. Both screenshots use the same viewport.

## Keep the useful part

For the Library, I borrowed Notion’s folder tree. My posts, work and services fit neatly into it, and you could browse them while keeping a document open.

Claude and I got it looking close enough that **I started confusing the Library with the actual Notion tab I had open.**

I asked Codex to try Linear’s colors on a separate branch, then eventually settled on a palette inspired by Cron Calendar.

![The Notion-inspired Library in light mode, with the Blog folder expanded beside the post Why I replaced Tailwind with plain old CSS.](https://sarthakmishra.com/assets/library-notion-light-Czf9ufRC.jpeg)

Notion-inspired palette, light mode.

![The same post and expanded Blog folder in light mode with the Linear-inspired palette.](https://sarthakmishra.com/assets/library-linear-light-BCbk59d2.jpeg)

Linear-inspired palette, light mode.

![The same post and expanded Blog folder in light mode with the Cron Calendar-inspired palette.](https://sarthakmishra.com/assets/library-cron-light-A0_Igc9B.jpeg)

Cron Calendar-inspired palette, light mode.

![The Notion-inspired Library in dark mode, with the Blog folder expanded beside the post Why I replaced Tailwind with plain old CSS.](https://sarthakmishra.com/assets/library-notion-dark-C6b775u5.jpeg)

Notion-inspired palette, dark mode.

![The same post and expanded Blog folder in dark mode with the Linear-inspired palette.](https://sarthakmishra.com/assets/library-linear-dark-DheysYV5.jpeg)

Linear-inspired palette, dark mode.

![The same post and expanded Blog folder in dark mode with the Cron Calendar-inspired palette.](https://sarthakmishra.com/assets/library-cron-dark-BnfeyHZz.jpeg)

Cron Calendar-inspired palette, dark mode.

The folders stayed through both changes. They let you open another piece of writing without going back to an index. That was the part I wanted to keep.

## Match the ordinary things

For Home, I tried a FigJam board with torn paper notes. I had Claude curl the bottom edges so they’d cast a shadow. We got the paper looking right. I went with a grid of tiles instead.

The grid gave me room for a robot, recent posts and the ventures I’ve worked on. But next to the Library, it looked like a different site.

I asked Claude to keep the grid and match the Library’s type, buttons and corner radii. **The pages felt related without sharing a layout.** Home could keep its blinking robot.

[Home changes from torn paper notes to a grid of tiles. The robot blinks, then the Library opens and a post is selected.](https://sarthakmishra.com/videos/designing-for-whatever-my-agents-and-i-build-next/home-to-library/native.m3u8)

The paper layout is a still, followed by a recording of the grid and Library. Different layouts, with the same type and controls.

### On a phone

The old site was designed around a larger screen. I made it work on phones, but I was mostly squeezing that design into less space.

This time, I compared the alternatives with mobile use in mind. That shaped how the dock and sidebar open, the transitions between pages, and how Home’s tiles stack. I kept the designs that looked and felt right on both screen sizes.

![Four original mobile pages in light mode. Home has a blue robot and a large serif introduction. The post has a serif title and separate action buttons. About has a large portrait. Contact opens with a two-step inquiry form. Each page has a hamburger menu.](https://sarthakmishra.com/assets/mobile-before-light-D0ljCd_m.jpeg)

![The same four mobile pages after the redesign, in light mode. Home uses an orange intro tile and a grid of venture icons. The post has a compact toolbar and sans-serif title. About has a small profile and timeline. Contact shows a calendar above the inquiry form. Each page has a dock trigger.](https://sarthakmishra.com/assets/mobile-after-light-Bdwz2HXs.jpeg)

Light mode. From left to right, Home, a post, About and Contact. Each screen is 390 × 844.

![Four original mobile pages in dark mode. Home has a blue robot and a large serif introduction. The post has a serif title and separate action buttons. About has a large portrait. Contact opens with a two-step inquiry form. Each page has a hamburger menu.](https://sarthakmishra.com/assets/mobile-before-dark-PrYc14SK.jpeg)

![The same four mobile pages after the redesign, in dark mode. Home uses an orange intro tile and a grid of venture icons. The post has a compact toolbar and sans-serif title. About has a small profile and timeline. Contact shows a calendar above the inquiry form. Each page has an orange dock trigger.](https://sarthakmishra.com/assets/mobile-after-dark-Cs4_4JDb.jpeg)

The same comparison in dark mode, with Home, a post, About and Contact from left to right.

## Give agents a starting point

I don’t want to spend an afternoon explaining how a menu should work every time I ask an agent to try a new idea. So I adopted vercel’s new [UI SDK](https://ui-sdk.dev/) and gave the agents a small set of shared controls, with rules for when to use them. I can ask for a different layout and still know what I’m getting when I ask for a button.

Comparing whole layouts took a little more setup. While Claude worked on the dock’s click bounce, I had Codex fix the dev servers so I could open two versions at once. I could keep a version I liked and judge an alternative in the browser.

That made it easier to throw out a layout, even one I’d just spent time getting the paper shadows right on. Working this way helped me finish the migration in about a week.

## The next site

The dock is the part I want to take with me. A future tool can reuse the portfolio’s controls and colors where they fit, or have a look of its own. With a spot in the dock, someone reading one of my posts has a way to find it. With the dock on the tool too, someone who finds the tool first can discover the rest of my work.

That’s about as much cross-promotion as I want when I’m halfway through reading something. An icon at the edge of the page, and the option to hide it.

## Structured data

```json
{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "WebSite",
      "@id": "https://sarthakmishra.com/#website",
      "url": "https://sarthakmishra.com/",
      "name": "Sarthak Mishra",
      "publisher": {
        "@id": "https://sarthakmishra.com/#person"
      },
      "inLanguage": "en"
    },
    {
      "@type": "Person",
      "@id": "https://sarthakmishra.com/#person",
      "name": "Sarthak Mishra",
      "url": "https://sarthakmishra.com/about",
      "jobTitle": "Design Engineer",
      "image": "https://sarthakmishra.com/og-images/sarthak-mishra.webp",
      "sameAs": [
        "https://github.com/SarthakMishra",
        "https://www.linkedin.com/in/itssarthakmishra/",
        "https://x.com/MishraMishry"
      ]
    },
    {
      "@type": "WebPage",
      "@id": "https://sarthakmishra.com/library/blog/designing-for-whatever-my-agents-and-i-build-next#webpage",
      "url": "https://sarthakmishra.com/library/blog/designing-for-whatever-my-agents-and-i-build-next",
      "name": "Designing for whatever my agents and I build next",
      "description": "How I made sure my next idea would feel at home alongside the rest of my work. The trick was deciding which design choices my agents could carry forward.",
      "inLanguage": "en",
      "isPartOf": {
        "@id": "https://sarthakmishra.com/#website"
      },
      "mainEntity": {
        "@id": "https://sarthakmishra.com/library/blog/designing-for-whatever-my-agents-and-i-build-next#content"
      },
      "breadcrumb": {
        "@id": "https://sarthakmishra.com/library/blog/designing-for-whatever-my-agents-and-i-build-next#breadcrumb"
      }
    },
    {
      "@id": "https://sarthakmishra.com/library/blog/designing-for-whatever-my-agents-and-i-build-next#content",
      "url": "https://sarthakmishra.com/library/blog/designing-for-whatever-my-agents-and-i-build-next",
      "name": "Designing for whatever my agents and I build next",
      "description": "How I made sure my next idea would feel at home alongside the rest of my work. The trick was deciding which design choices my agents could carry forward.",
      "mainEntityOfPage": {
        "@id": "https://sarthakmishra.com/library/blog/designing-for-whatever-my-agents-and-i-build-next#webpage"
      },
      "author": {
        "@id": "https://sarthakmishra.com/#person"
      },
      "datePublished": "2026-11-21T00:00:00.000Z",
      "inLanguage": "en",
      "keywords": [
        "portfolio",
        "design-systems",
        "building-in-public"
      ],
      "@type": "BlogPosting",
      "headline": "Designing for whatever my agents and I build next",
      "publisher": {
        "@id": "https://sarthakmishra.com/#person"
      },
      "image": "https://sarthakmishra.com/og-images/blog/designing-for-whatever-my-agents-and-i-build-next.webp"
    },
    {
      "@type": "BreadcrumbList",
      "@id": "https://sarthakmishra.com/library/blog/designing-for-whatever-my-agents-and-i-build-next#breadcrumb",
      "itemListElement": [
        {
          "@type": "ListItem",
          "position": 1,
          "name": "Home",
          "item": "https://sarthakmishra.com/"
        },
        {
          "@type": "ListItem",
          "position": 2,
          "name": "Blog",
          "item": "https://sarthakmishra.com/library/blog"
        },
        {
          "@type": "ListItem",
          "position": 3,
          "name": "Designing for whatever my agents and I build next",
          "item": "https://sarthakmishra.com/library/blog/designing-for-whatever-my-agents-and-i-build-next"
        }
      ]
    }
  ]
}
```
