Repository navigation
Add "We built our own Claude Design", the first OAP story, and the messagingbot example - #42
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
josephschorr
force-pushed
the
case-study-claude-design
branch
from
October 28, 2026 16:56
764a37f to
7022e60
Compare
A resourceList answer bound to Kind/name#path[?] keeps only the list elements whose discriminator the answer names, in the CR's own order. It lets a bundle offer a menu (every candidate declared, the installer picks which stay). An answer naming no element fails the install rather than being silently dropped, and re-applying the same answer is a no-op.
Turns a brief into an on-brand HTML artifact grounded in the design and messaging repositories chosen at install, and revises it from annotations left on the rendered page. GitHub access is read-only and limited to the approved repositories; the design skills are a menu the installer picks from.
The slacksim can now open an artifact's live view over the client, pin annotations to its elements, send them, and show the revision that answers them. The messagingbot-design story uses it for the narrated demo.
Docs tables had no styling at all. A manifest clip entry can now carry a title, upload date, duration and transcript, for pages that publish video structured data.
A standalone story page at /stories/claude-design walking through how messagingbot reproduces the Claude Design workflow on OAP, with the narrated demo, a before/after of an annotated revision, and a docs index page for the case-study series.
The story page now emits one graph with the site's organization, website and project nodes, plus its article, FAQ, demo video and breadcrumb, the same way docs pages do.
Keep the original story's narrative and fix what the critiques found: - Claims: drop the "sandbox can only reach GitHub" overclaim (allowed hosts are recorded, not enforced), scope the reviewer check to what the interact handler does, and disclose that the bundle ships per-call checks in permissive mode. - Narrative: define OAP in the hero, show the toolspec's own refusal message under the gate diagram, cut repeated copy, frame the Why grid as the reasons we chose OAP, and end on a two-step "Try it" (install OAP, then install messagingbot). - Design language: render inside the landing's ruled frame on its tokens, share its nav (SiteNav, extracted from Landing.tsx) and footer, drop the story numbering, kickers, per-item hues and teal hover states. - Layout: a list fallback for the gate diagram on phones, wrapping prose code blocks, tabs above the revision shots, and no horizontal page scroll at 390px. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
samkim
force-pushed
the
case-study-claude-design
branch
from
November 7, 2026 08:47
1b608f2 to
8b8974e
Compare
samkim
approved these changes
Nov 7, 2026
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Starts a new series of stories showing how OAP can reproduce the features of other AI platforms. The first one, "We built our own Claude Design", walks through messagingbot: a brand-designer agent that turns a brief into an on-brand page and revises it from notes pinned directly onto the design, built entirely from primitives OAP already has.
/stories/claude-design, with a narrated demo, a before/after of an annotated revision, the ingredients that map Claude Design's features to OAP, and a FAQ. It carries the same kind of search metadata as the docs pages, plus FAQ and video data. A "Case studies" page in the docs introduces the series.examples/messagingbot): an open-source version of the agent we use internally. It reads your design-system and messaging repositories read-only, and the installer picks which design skills it loads.Test plan
oap agent lint examples/messagingbot