Builder stack

Paper + Codex + Storybook

Design in Paper, keep the component library in sync via MCP, and ship Storybook components agents can reuse.

Marvin Kennis's production loop: Paper + Codex closes the design-to-production gap, with Storybook as the shared component surface. A follow-up notes Paper Desktop + MCP + Codex as the setup.

Design in Paper. MCP to keep it in sync with our component library. Storybook components now usable by other engineers + agents.

In this recipe

  1. PaperApp

    Where the design happens.

    DocsHome

  2. Paper MCPMCP

    Keeps Paper in sync with the component library.

    Docs

  3. CodexAgent

    The agent driving the loop.

    DocsHome

  4. StorybookApp

    Makes the components usable by other engineers and agents.

    DocsHome

Cited from

@marvinkennis · Marvin Kennis

https://x.com/marvinkennis/status/2094542243789185234

14,897 impressions204 likes244 bookmarks10 replies6 reposts · captured 2026-09-15