Koto — ​​Meet Koto — a creative studio that partners with brands…

Platform
Websites
Category
Portfolio
Style
Dark, Mono
Type
Gt Kotoheim Mono, Gt Kotoheim
Updated
Sep 2026

Build with AI

An original design in the taste of Koto — structure, tokens, font swaps and an imagery plan (1,549 words).

Paste into any AI tool. Every screenshot in the prompt is a public link the tool can open, and you can attach the screenshot link as a visual reference. It tells the agent to build something original: new copy, your brand, licensed or generated images.

Open in

Long prompts are copied to your clipboard first — paste them in when the tool opens.

Connect via MCP

claude mcp add uidiscovery \
  --env UIDISCOVERY_URL=https://uidiscovery.com \
  -- node /path/to/uidiscovery/mcp/server.mjs

Then ask your agent (it calls get_design_brief({ slug: "koto" }) and get_image_plan({ slug: "koto" })):

Use the uidiscovery MCP server: call get_design_brief({ slug: "koto" }) and get_image_plan({ slug: "koto" }), look at the preview images, then build an original site for [my brand] that follows the brief. Cite https://uidiscovery.com/sites/koto.

Download kit ↓Brief as Markdown ↗API docs
Preview the prompt
# Build brief — an original marketing website in the taste of Koto

> Reference: https://koto.studio · UIDiscovery: https://uidiscovery.com/sites/koto · captured 2026-09-21 at a 1440px desktop viewport (+ 390px iPhone shots) · [full page](https://uidiscovery.com/media/captures/koto/full.webp) · [scroll video](https://uidiscovery.com/media/captures/koto/preview.mp4)

## 1. Goal
Build an original marketing website for **[the user's brand]** that feels as considered as Koto — same structure, rhythm and polish, entirely new identity and content.

## 2. Originality rules
- Build an ORIGINAL design for the user's own brand in the same *taste* as Koto: structure, rhythm, hierarchy, palette mood and type pairing.
- Never reuse Koto's logo, name, product imagery, illustrations, icons, screenshots or copy. Write new copy for the user's product.
- If the user hasn't said what their product is, ask first (or use clearly marked placeholders like [Brand], [Product], [Audience]).
- Reference screenshots are for looking at, not for embedding or tracing.

## 3. The taste, in short
- Koto (koto.studio): Portfolio marketing website, dark, mono.
- 2 sections: Logo cloud → Blog.
- Spacing: long, content-rich sections (median ≈1700px tall at 1440).
- Type: one family (Gt Kotoheim Mono). Imagery: mostly photography.

## 4. Page structure (top to bottom)

### 1. Logo cloud — borrow trust from recognisable customers or partners.
- Layout: a single row or wall of monochrome marks with a one-line lead-in. Tall, ≈1.9 screens (1700px at 1440), own dark band #060606; 40 image elements (photo collage/gallery + small graphics); 10 buttons (tabs, toggles or per-card actions).
- Slots: One-line lead-in (e.g. “Trusted by…”); 6–10 monochrome customer/partner marks (your own, with permission).
- Topic (tone/length only — never reuse): “Our work”
- [Screenshot](https://uidiscovery.com/media/captures/koto/s-02.webp)

### 2. Blog — signal an active, credible team through recent writing.
- Layout: 3-up card grid: image, title, meta. About one full screen (785px at 1440), own dark band #060606; 6 images/icons (a set of cards or a small gallery); 5 text links instead of buttons; 5 headings → ~4 items under a title.
- Slots: Title + “All posts” link; 3 post cards: cover image, title, date/author.
- Topic (tone/length only — never reuse): “Studio news”
- [Screenshot](https://uidiscovery.com/media/captures/koto/s-03.webp) · imagery: slot 1

Inner pages also captured (About, Blog, Careers, Contact, Security): https://uidiscovery.com/sites/koto?view=pages

## 5. Design system
### Colour
| Role | Hex | Use | Contrast on background |
|---|---|---|---|
| background | `#ffffff` | page background | — |
| foreground | `#010000` | body text, headings | 21.0:1 |
| accent | `#010000` | none captured — monochrome. Primary buttons invert (foreground fill, background text); add your brand colour only for small highlights | — |
| surface | `#cccccc` | cards, inputs, alternate bands | text on it 13.1:1 |
| muted | `#989898` | secondary text, borders | 2.9:1 — borders / large text only |

Captured palette: `#ffffff` `#989898` `#060606` `#595959` `#010000` `#cccccc`. Roles are assigned automatically — sanity-check them against the screenshot. Keep the palette's *mood* (dark, neutral, desaturated) and proportions; swap the accent for the user's brand colour.

### Tokens
```css
:root {
  --background: #ffffff;
  --foreground: #010000;
  --accent: #010000;
  --surface: #cccccc;
  --muted: #989898;
  --font-heading: "Inter", ui-sans-serif, system-ui, sans-serif;
  --font-body: "Inter", ui-sans-serif, system-ui, sans-serif;
  --radius: 12px; /* calibrate from the screenshot */
}

/* Tailwind v4 — in globals.css after @import "tailwindcss"; */
@theme {
  --color-background: var(--background);
  --color-foreground: var(--foreground);
  --color-accent: var(--accent);
  --color-surface: var(--surface);
  --color-muted: var(--muted);
  --font-heading: var(--font-heading);
  --font-sans: var(--font-body);
}
```

### Typography
- Headings: **Inter** (Google Fonts) — reference uses Gt Kotoheim Mono. “Gt Kotoheim Mono” is likely a custom or licensed face. Inter is a neutral stand-in — pick a closer free match by eye from the screenshot.
- Body: same family — a single-family system; create contrast with size and weight, not a second face.
- Scale (starting point, sizes weren't measured — calibrate against the 1440px screenshot): display clamp(2.5rem, 5vw, 4.25rem), h2 clamp(1.75rem, 3vw, 2.5rem), h3 1.25rem, body 1rem–1.125rem / 1.6, small 0.875rem. Headings: tight tracking (-0.02em), line-height 1.05–1.15.
- A monospace accent (labels, numbers, code) is part of the tone — use it sparingly.

### Spacing & rhythm
Sections run ≈1700px tall at 1440 (median; range 785–1700px, captures cap at 1700px) — long, content-rich chapters. Start with 96–128px vertical padding per section on desktop and about two-thirds of that on mobile. One continuous background — separate sections with space and type, not colour bands. 8px spacing grid, 1200–1280px max content width, 24px (mobile) / 32–48px (desktop) gutters.

### Shape, depth & theme
On dark, separate layers with 1px borders at ~8–12% white and soft glows instead of drop shadows. Read exact corner radius, border and shadow treatment from the screenshots. Dark-first; for a light mode swap background ↔ foreground, lighten the surface, keep the accent and re-check contrast.

## 6. Imagery plan

Best guess: mostly **photography** (dark, neutral, desaturated, Portfolio). Inferred from element counts, colours and industry — not from the pixels — so open the linked screenshots and match the real style before sourcing anything.

### Slot 1 · 2. Blog → photography
- Photography, seen in the capture (people). (measured from the screenshot) Count: a set of ~6 in one consistent style. Aspect: 3:2. Look first: [ref 1](https://uidiscovery.com/media/captures/koto/s-03.webp)
- **Stock** — “architectural detail shadow editorial dark”: [Unsplash](https://unsplash.com/s/photos/architectural-detail-shadow-editorial-dark?orientation=landscape) · [Pexels](https://www.pexels.com/search/architectural%20detail%20shadow%20editorial%20dark/?orientation=landscape) · [Pixabay](https://pixabay.com/images/search/architectural%20detail%20shadow%20editorial%20dark/?orientation=horizontal)
- **Generate** — `Photograph: architectural detail shadow editorial. Composition: editorial crop with one clear focal point. Lighting: low-key, moody directional light with deep shadows. Neutral, desaturated colour grade that sits on #060606, #010000, #cccccc. Photorealistic, natural textures, shallow depth of field, 35mm lens. Aspect ratio 3:2. No text, no letters, no logos, no watermarks, no brand marks or trademarked products, no recognisable real people.`

- **Logos** — 1. Logo cloud: Never generate or stock-source logos. Use your real customers'/partners' marks with permission (monochrome, equal height), or neutral wordmark placeholders until you have them. Integration icons: each tool's official brand kit (Simple Icons is a quick start; trademarks still apply).

### If the screenshots show a different style
Open the refs first and name what you actually see (photo / product UI / illustration / abstract gradient or 3D / type only). If it differs from the guess, switch routes — UI is built in code, type-only needs no image, otherwise:
- **abstract 3D / gradient** — generate `Abstract 3D render: soft, glossy glass-like shapes and a smooth gradient in #989898 and #cccccc on a #ffffff background. Lighting: low-key, moody directional light with deep shadows; neutral, desaturated tone. Minimal and calm, generous negative space on one side for text. Aspect ratio 16:9. No text, no letters, no logos, no watermarks, no brand marks or trademarked products, no recognisable real people.` · stock: [“abstract dark gradient 3d” on Unsplash](https://unsplash.com/s/photos/abstract-dark-gradient-3d?orientation=landscape) (same query works on Pexels/Pixabay)
- **illustration** — generate `Flat vector illustration: design studio workspace, friendly simplified shapes, limited palette of #060606, #010000, #cccccc plus one soft neutral, plenty of empty background, consistent line weight, neutral, desaturated mood. Aspect ratio 16:9. No text, no letters, no logos, no watermarks, no brand marks or trademarked products, no recognisable real people.` · stock: [“lifestyle flat illustration” on Unsplash](https://unsplash.com/s/photos/lifestyle-flat-illustration?orientation=landscape) (same query works on Pexels/Pixabay)

- **Licences:** Unsplash and Pexels images are free for commercial use under their own licences; Pixabay under the Pixabay Content License. Check each image's page before use, credit the photographer when asked (good practice anyway), and skip images showing logos, trademarks, branded products or identifiable people without a release.
- **AI generation:** the prompts work with any image model (GPT Image, Imagen, Flux, Midjourney, Firefly, SDXL…) — check its commercial-use terms. Never put the reference brand's name or “in the style of <brand>” in a prompt.
- **Never** download, trace or re-host the reference's own images, illustrations, product shots or logos.

## 7. Build steps
1. Confirm brand, product, audience and the primary action with the user.
2. Set up the tokens (CSS variables / Tailwind @theme) and load the fonts.
3. Build the sections in order, mobile-first, with each reference screenshot open.
4. Write original copy for every slot — match length and tone, never the words.
5. Source every image via the imagery plan (stock or generated); compress it and record credits.
6. Run the checklist at 390 / 768 / 1440px and fix what fails.

## 8. Acceptance checklist
- [ ] Responsive at 390px, 768px and 1440px — no horizontal scroll, tap targets ≥ 44px on mobile.
- [ ] Colour contrast WCAG AA: 4.5:1 body text, 3:1 large text and UI; visible focus states; full keyboard navigation.
- [ ] Semantic HTML: one <h1>, ordered headings, landmarks (header/nav/main/footer), labelled form fields, alt text on meaningful images.
- [ ] Performance: modern image formats with width/height set, lazy-load below the fold, ≤ 2 font families with font-display: swap, LCP < 2.5s.
- [ ] prefers-reduced-motion respected; animations under ~300ms and never blocking content.
- [ ] Originality: no copied logos, images, illustrations or copy from the reference; every image licensed or generated; credits recorded.

## 9. If you use Next.js + Tailwind
Paste the @theme block into globals.css, load fonts with next/font/google, make each section a server component in components/sections/, use next/image with explicit sizes, and keep client components for interactive bits only (menus, toggles, accordions).

---
More: tokens https://uidiscovery.com/api/v1/sites/koto/tokens · kit https://uidiscovery.com/api/v1/sites/koto/kit · MCP `get_design_brief({ slug: "koto" })`, `get_image_plan({ slug: "koto" })`. Cite the reference as https://uidiscovery.com/sites/koto.

Visit koto.studio ↗Download kit ↓

Design tokens

Koto’s palette and type, mapped to roles. Drop the rules file into Cursor, Claude Code or Codex so what they build stops looking like a template.

  • background#ffffff
  • foreground#010000
  • accent#010000
  • surface#cccccc
  • muted#989898
/* Tailwind v4 — paste into your globals.css */
@theme {
  --color-background: #ffffff;
  --color-foreground: #010000;
  --color-accent: #010000;
  --color-surface: #cccccc;
  --color-muted: #989898;
  --font-heading: gtKotoheimMono, ui-sans-serif, system-ui, sans-serif;
  --font-sans: gtKotoheim, ui-sans-serif, system-ui, sans-serif;
}

About this design

Written from the capture data for Koto.

Koto (koto.studio) is a website in the Portfolio category. Its homepage is captured as 2 sections, top to bottom: logo cloud and blog. We also captured its about, blog, careers, contact and security pages.

It's a dark design: the page background is #ffffff with #989898 as the main text colour. Headings are set in Gt Kotoheim Mono, body copy in Gt Kotoheim. A monospace face adds a technical tone.

Compared with the 81 other Portfolio sites in the library, Koto is one of the 22% that go dark, and the group's most common heading face is Inter, where Koto uses Gt Kotoheim Mono. The average Portfolio homepage here has 4 sections; this one has 2.

Worth studying here: the logo cloud, for how social proof is placed without shouting, the blog teaser, for card anatomy and metadata and the about section, for how the company story is told. Open any section for its palette, fonts and a build prompt you can hand to Claude, Cursor or v0.

More references: browse all websites.

More portfolio sites

Related searches

Sections captured: Logo cloud, Blog, About, Content, Team, Content, Content, Content, Content, Showcase, Content, Content, Footer, Content, Content, Content, Content, Content, Content, Content, Content, Content