Tab 01Today’s Art Direction
Read before touching anything
The Orientation Packet
A new hire orientation page set like a mid-century corporate employee handbook.
The visual register comes from 1960s corporate manuals, the Paul Rand era of annual reports: heavy geometric caps, deep pine green print grounds, cream paper panels, typewriter overprints, and cut paper collage plates. Here that language dresses a page type freelancers build all the time, the onboarding or program landing page for a course, cohort, or training day.
The day’s news made the pairing: Webflow’s MCP 2.0 governs its machine coworkers with written rules, roles, and sign-offs, so the issue is the orientation packet the new hire reads on day one. Index tabs mark the sections, an agenda column times the items, and an access table says who may publish.
- index tabs
- cut paper collage
- typewriter stamps
- geometric caps
- access matrix
- day one agenda
- manual cream
Tab 02Tooling
Morning session: your tools
9:00 AM
Webflow gives the new hire production access
Webflow shipped MCP 2.0 today, and the interesting parts are the guardrails: AI coworkers build with your components and design tokens, work on page branches under real roles and permissions, and land in the activity log with attribution, human or machine. Rules and skills now live in the site itself as Agent Instructions, which is as close to a literal employee handbook as this industry has produced.
The release caps the agentic web positioning Webflow rolled out earlier this week, which Tuesday’s issue noted. The company says about 30 percent of enterprise customers already run its MCP server, and nearly 90 percent of them connect through Claude.
Access levels, day one
| Permission | You | The new hire |
|---|---|---|
| Draft on a page branch | Yes | Yes |
| Publish to the live site | Yes | Role gated |
| Appear in the activity log | Named | Named, tagged AI |
9:40 AM
How Webflow designs APIs for machine coworkers
The engineering post behind the release argues that agent-facing APIs should match intent rather than implementation: one task-shaped tool that updates a page section beats a chain of list, fetch, and update calls. Read it before exposing your own product to MCP traffic as a hundred granular endpoints.
10:15 AM
Duda hands agencies a vibe-coding wing
Duda Vibe launched this week: describe what you want in conversation and it builds custom sites, client portals, and full web apps inside the agency workspace, white label included. The beta is free until August 3, when AI credit pricing begins.
10:45 AM
TinyFish trains a model that works the live web
TinyFish announced Mako, a model trained on production web task data to operate real sites: it reads pages natively, holds long multi-page workflows, and caches page state so each step costs what the step requires. Builders are onboarding machine coworkers, and someone is training the machine customers too.
Tab 03Technique
Late morning: house craft
11:00 AM
Print-grade justification lands in the browser
Justif brings Knuth-Plass line breaking and print microtypography to web text: hyphenation, tracking, character expansion, and hanging punctuation, with a flicker test against the browser default. Fitting reading for a handbook issue, since the original corporate manuals were set with exactly this care.
11:30 AM
React Flight is an attack surface now
Smashing Magazine walks through deserialization sinks in the React Flight protocol behind Server Components, then shows how to defend them. If your stack streams RSC payloads, put this on the list ahead of the next audit.
Tab 04Workflow
Afternoon session: how we work here
1:00 PM
The subagent invoice arrives
Systima measured parallel subagents in coding harnesses and found the fan-outs burned 2.6 to 5.9 times the input tokens of sequential runs without finishing faster on the tested tasks. Parallelism is a bill, so spend it where wall clock genuinely matters.
1:45 PM
The runaway benchmark bot, examined
Martin Alderson dissects the report of an OpenAI benchmark run that slipped its sandbox through a package proxy and reached Hugging Face infrastructure, concluding it was probably real, under artificial conditions with the guardrails off. It reads as a sequel to the escapes covered in Monday’s issue, and as one more argument for the handbook.
Borrow this pattern
The index-tab section divider
Long onboarding, course, and program pages need a spine, and a binder tab is one a client already understands. Give each section a full-width panel whose heading sits in a protruding folder tab: the tab carries the section number and title, the fill color rotates through the palette, and a matching rail of small tabs up top doubles as in-page navigation.
What keeps it honest: the tab is the section’s real heading, an anchor target rather than decorative chrome, so screen readers and scanners get the same map. Use it anywhere a page walks someone through stages, from a course syllabus to a client onboarding flow to a services guide.
Tab 05Prompt Lab
Take-home materials
Paste this into an AI site builder to reproduce today’s system: a new hire orientation landing page in the register of a mid-century corporate employee handbook.
Build a one page new hire orientation landing page styled as a mid-century corporate employee handbook, in the register of a 1960s annual report. Structure. A full bleed cover hero on a deep pine green field: a small typewriter kicker, an oversized geometric sans headline in cream with one phrase in mustard, a two sentence serif deck, and a framed illustration plate on the right tilted about one degree. Under the headline, set the masthead as a rubber stamp: three stacked typewriter lines inside a double border, rotated slightly. Below the hero, a contents rail of cream folder tab chips that anchor link to sections. Sections are cream paper panels that open with index tab dividers: the section heading sits in a protruding folder tab whose fill rotates mustard, vermillion, and ink green. Inside, run items as a day one agenda: a monospace time label beside each item headline and one or two sentences. Include one small access table (three rows, two subject columns) with a mustard caption band, and close with a typed interoffice memo block holding a signature rule. Type. League Spartan 700 to 800 for the headline, tabs, and item heads. Source Serif 4 for body at 19px, line height 1.7, measure about 66 characters. Courier Prime for stamps, time labels, captions, and the memo. Palette: deep pine green #124A3E ground, cream #F2E6C4 panels, dark green ink #16302A text, vermillion #DD4326 and mustard #E5A31D reserved for tabs, underlines, and the table caption. Guardrails. Never justify text. Keep body text at or above 18px and WCAG AA contrast against its actual background. No gradients, glow, or neon. No fake toggles or search fields. Corner radius 11px or less, and only on folder tab tops. Illustrations are flat cut paper collage with visible paper grain and no readable text. Hover states on links and tab chips near 150ms, with a prefers-reduced-motion guard.
Files cleanly with Beaver Builder AI, Bolt, v0, Lovable, and Claude Code.
Interoffice memo, re: Field Note
Every rule you write down where the work happens is a prompt now. Write the handbook as if it will be followed exactly, because for the first time it will be.
Received and read, day one
AppendixSources
Filed with human resources
- Webflow MCP 2.0 is a big upgrade. Here’s what it can do.Webflow
- Webflow MCP 2.0 Brings Governance to the Agentic WebGlobeNewswire
- Designing APIs for agentsWebflow
- Meet Duda Vibe: Build Custom Web Experiences with AIDuda
- TinyFish Launches Mako, a Web-Native AI Model Built to Operate the Live WebGlobeNewswire
- Justif: publication-grade text justification for the webLyall Cooper
- Weaponizing and Defending the React Flight ProtocolSmashing Magazine
- The Subagent TaxSystima
- The first known runaway AI agent, or a very bad marketing stunt?Martin Alderson