Feature Library

How it was built

An agent built the ferry duty desk from the library alone, through the store’s agent feed. This is what it asked for, in order, and what we learned from watching it.

Agent
Claude Code 2.1.325
Model
Claude Opus 5.5
Calls to the library
42
From first call to last
20 min
Kit
dashboard, strict
Look
Paper and inkliveliness 0 · fidelity 30 · density 30
Level
tunedchecked: “Paper and ink, tuned”Only the accent and the text on it, per mode: #1f5a73 by day, #8fc3d6 by night

The brief it was given

Build the duty desk for a small archipelago ferry line (fictional): the screen the duty officer keeps open all day. The day and the crossings left; each route on time, late or paused; where every boat is on a sea chart, with how many are aboard; today's crossings on a timeline from 06:00 to 23:00 that can be dragged to look ahead; a few numbers that answer "do I need to act?"; and one sentence that says what needs attention first. Calm and exact. One of the library's looks at the Tuned level, with the line's own sea-blue accent. Vite and TypeScript, no framework. Keyboard, screen reader and reduced motion all work.

A fresh session in an empty folder on the owner's machine. Its only way into the library was the store's agent feed (MCP), with a test licence for the whole library; it was told not to open the library's own folder. Every call it made was recorded, and that record is what this page is made from.

What it did

  1. Read the rules5 calls · 17:34:09

    The agent protocol first: how to plan, read, install and check.

    • rules.md
  2. Planned the build1 call · 17:34:36

    A kit for this kind of build, with a tone applied.

    • dashboard, strict
  3. Looked for parts5 calls · 17:34:55

    Searched by the job, not by a name.

    • “simple sea chart map showing vessel positions with labels, keyboard and screen r”
    • “horizontal day timeline of scheduled trips per lane with a now marker that can b”
    • “forecast line chart over 12 hours with a threshold limit line and the time it cr”
    • “KPI number with percentage of capacity used, like a car deck fill bar”
    • “announce live status changes to screen readers once without repeating”
  4. Read the playbooks6 calls · 17:35:02

    How the parts are placed, moved and made accessible, and why.

    • Placement and layout
    • Accessibility baseline
    • Motion and feel
    • Performance budgets
    • Layouts that never break
    • the list
  5. Planned the build1 call · 17:35:16

    A kit for this kind of build, with a tone applied.

    • dashboard, strict
  6. Read the cards5 calls · 17:35:28

    Each part’s card and every pitfall before using it.

    • Appearance: themes, contrast, text size, density, motion
    • Quiet SVG charts
    • Keyboard shortcuts: registry, help, rebinding
    • Charts everyone can read
    • Loading, empty and error states
  7. Read the rules1 call · 17:35:35

    The agent protocol first: how to plan, read, install and check.

    • SCHEMA.md
  8. Installed6 calls · 17:35:40

    The module files, each marked with the licence.

    • Appearance: themes, contrast, text size, density, motion@1.0.1
    • Quiet SVG charts@1.0.1
    • Charts everyone can read@1.0.0
    • Loading, empty and error states@1.0.1
    • Keyboard shortcuts: registry, help, rebinding@1.0.2
    • install: refused
  9. Checked1 call · 17:36:25

    Versions, licences and the checklist before calling it done.

    • ink, tuned: Paper and ink, tuned
  10. Installed1 call · 17:36:36

    The module files, each marked with the licence.

    • install: refused
  11. Looked for parts1 call · 17:36:36

    Searched by the job, not by a name.

    • “the Paper and ink look stylesheet and shared tokens.css and dials.css to restyle”
  12. Checked1 call · 17:50:04

    Versions, licences and the checklist before calling it done.

  13. Installed1 call · 17:52:49

    The module files, each marked with the licence.

    • ink@library-5dbf68e
  14. Read the playbooks5 calls · 17:53:05

    How the parts are placed, moved and made accessible, and why.

    • Placement and layout
    • Performance budgets
    • Accessibility baseline
    • Motion and feel
    • Layouts that never break
  15. Checked1 call · 17:53:43

    Versions, licences and the checklist before calling it done.

    • ink, tuned: Paper and ink, tuned

The parts it took

The playbooks it followed

  • Placement and layout Checked at 1440, 375 and 320 pixels wide: the sea chart owns the middle, the attention sentence is the one thing top left.
  • Accessibility baseline One focus ring per control: found a doubled frame in the shortcut help, caused by its own base styles outranking the part's fix, and made its base styles zero specificity.
  • Motion and feel "Changes animate, arrivals don't": the boats used to glide in from a corner on the first reading; now they are placed at once and only glide between readings.
  • Performance budgets Nothing runs between updates: a full update of routes, figures, chart and timeline measured 1.4 to 3.2 ms.
  • Layouts that never break "Live text never moves the layout": the attention sentence and the figures reserve their room. The playbook's restyle check measured 0 of 710 boxes moving when the theme switched.

Named by its kit but not read: Office and desktop companions, Ingest that never double-counts, Layout studio.

What it built itself

The glue between the parts, which the rules ask to be clean modules of its own.

  • The sea chart: islands, routes, ports and boats with heading and people aboard; late and paused boats shown by ring style and words, never colour alone; arrow keys step from boat to boat, each read out.
  • The day timeline: a lane per route, late crossings hatched, a now line, and a look-ahead handle (a slider, moved by dragging or the arrow keys) that the sea chart follows.
  • The made-up line and its live feed: a seeded timetable, lateness that drifts, bookings that fill, a paused route and a wind front that firms up.
  • The attention ranking and its sentence: wind within three hours, then a late boat, a paused route, a full car deck.

What we found to improve

  • A look couldn't be fetchedFixed

    At the Tuned level the agent had no way to get the look it was tuning: install knew only parts, and the planning tools gave the look's path and the overrides, never its stylesheet. It asked whether to wait or fall back to Inspired.

    install now takes a look id and returns its files, licence-marked like a part's, with the order to load them in.

  • Playbooks arrived without their textFixed

    The agent's client read only the structured part of each answer, which held the playbook's title and a link; the markdown was elsewhere in the reply. The rules came through the same way.

    get_playbook and get_brief carry the markdown in the structured result too.

  • Search mixes 3D parts into interface jobsFixed

    Asked for a day timeline with a now marker, find_parts ranked an animation editor, a camera director and a material designer first; asked for a capacity figure, it offered a race car. The agent read past them, but each wrong result costs a card read.

    Fixed after the run: for an interface job, 3D, simulation and effects parts rank lower and are marked, and find_parts takes a kit to search within. Rerun on the agent's own searches, the race car and the camera director are gone.

  • Search doesn't know looksFixed

    Searching for the Paper and ink stylesheet and its tokens returned five unrelated parts.

    Fixed after the run: when the words name a look or ask for one, find_parts returns the matching looks with how to install them. The agent's search now finds Paper and ink first.

  • Large installs overflow the agent's clientFixed

    Most install answers were bigger than the client shows inline and were saved to files; two came back as text only and had to be recovered from the session record.

    Fixed after the run: install(id, { path }) returns one file as plain text, and every file listed carries its SHA-256, so a copy can be checked byte for byte.

  • A failed refresh moved the whole deskFixed

    The owner's review: when the feed dropped, the loading part put its banner above the desk and pushed everything down about 78 px, and back up when the feed returned. The agent moved the feed's state into a reserved place in the masthead; nothing moves now.

    Taken by the library: loading-states 1.1.0 lets the app say where that line goes, or keep its room; measured, the content moves 0 px instead of 75. The default now has a pitfall saying it moves the content.

  • A row of figures at three sizesFixed

    The owner's review: the date, crossings left, time and feed state sat at three different sizes and did not line up, and the time was cut down in one place and rounded in another.

    Taken by the library: a placement rule, "a row of figures lines up" (one size, one line, extras on a reserved detail line), and "one quantity, one way" now says a clock truncates.

  • A toggle that changed its own labelFixed

    The owner's review: the lost-feed toggle said its state twice, in its label and its pressed state, and changed size as it switched.

    Taken by the library: an accessibility rule, "a toggle keeps its label".

  • Several facts crammed into one sentenceFixed

    The owner's review: the timeline's "happening now" summary ran each route's sign, state and every boat's doing into one bulleted sentence with details in brackets, and the signs' different widths started each line at a different place. Hard to read. The agent made it a real table, one fact per column, the signs in a fixed slot, turning into stacked blocks on a narrow screen.

    Taken by the library: a placement rule, "several facts per row: a table, not a sentence", and an accessibility rule, "signs never set where the text starts". An aligned status table part is now a listed gap in the dashboard kit.

  • A table whose columns moved as it changedFixed

    The owner's review: the "now" table under the timeline let the browser size its columns, so every look-ahead step brought new text and moved the column edges, which made it dizzying to read. The agent gave it fixed columns sized for their longest text; over all 205 steps of the day, no column edge moves.

    Taken by the library: a resilient-layout rule, "a table that updates while it is read has fixed columns", with a way to check it: step the view through its states and require one position per column edge.

  • An alert that ran across the whole screenFixed

    The owner's review: the attention box was one 110-character sentence across the full width. The agent made it a short headline and label/value facts (When, Limit, Decide), the longest line now 39 characters; the screen reader still hears the full sentence.

    Taken by the library: a placement rule, "status is a headline and short facts, not a sentence", with lines kept under about 60 characters and columns for a wide box.

  • A button that pushed the page as it came and wentFixed

    The owner's review: the timeline's "Back to now" button was removed at now and shown while looking ahead; it is taller than the line beside it, so the timeline, the table and the footer moved on every click. The agent kept its room and only hid it from view; nothing moves now.

    Taken by the library: a resilient-layout rule, "a control that comes and goes keeps its room" (hidden from view, never removed from the layout), with a way to check it: toggle each such state and confirm nothing else moves.

  • What the library doesn't have yetOpen

    Built here instead: a flat sea chart with moving markers, a day timeline with a scrub handle, a live "what needs attention" sentence, a number tile, and a slider field.

    Three are now library parts, built from this run: the day timeline (day-timeline), the slider and stepper (range-fields) and the number tile (kpi-tiles, a row of figures that lines up). The live map with moving markers and the "needs attention" line are listed as gaps in the dashboard kit.

  • A scrolling box clipped the handle’s focus ringFixed

    The timeline scrolls sideways at narrow widths, and a box that scrolls on one axis clips on both: the look-ahead handle’s focus ring was cut by 6 px, and at 23:00 half the handle hung past the end. The owner spotted it in a screenshot. No playbook rule covered it, and the agent fixed it with padding inside the box and end margins on the track.

    Taken by the library: a resilient-layout rule (a box that scrolls on one axis clips on both: pad it by the ring's reach, and give a track's ends half the thumb plus the ring), a matching accessibility line, and an audit check that reports a focus ring cut by the box around it. A day timeline part is now a listed gap in the dashboard kit.

  • App styles can undo a part's fixesFixed

    The app's own focus rule had the same specificity as a part's fix and loaded later, so it brought back a doubled focus frame.

    Taken by the library: the token guide, the accessibility playbook and the agents' rules now say an app's own base rules go in :where(), at zero specificity, so they never undo a part's fix.

Every call, in order (42)
TimeAskedWithAnswerms
17:34:09server/discoverNo method server/discover.0
17:34:09initialize{"protocolVersion":"2025-11-25"}0
17:34:10tools/list{"tools":9}0
17:34:10resources/list0
17:34:23get_brief{}{"rules":"a998805d366f"}2
17:34:26resources/read{"uri":"feature-store://rules.md"}1
17:34:36get_kit{"purpose":"a calm operations dashboard for a ferry duty officer: routes status, sea chart with boats, timeline of cross{"kit":"dashboard","tone":"strict","parts":["appearance-theme","accessible-dialog","menu-skins","tabs-tooltips","steady-fields","data-table"24
17:34:55find_parts{"job":"simple sea chart map showing vessel positions with labels, keyboard and screen reader accessible","limit":6}{"platform":"reference","total":132,"parts":["connectors-layouts","world-pinned-labels","chart-access","site-plan","pure-css-interactions","52
17:34:55find_parts{"job":"horizontal day timeline of scheduled trips per lane with a now marker that can be dragged or scrubbed to look ah{"platform":"reference","total":85,"parts":["keyframe-timeline","camera-director","material-designer","road-network","meeting-scheduler","at45
17:34:55find_parts{"job":"forecast line chart over 12 hours with a threshold limit line and the time it crosses","limit":6}{"platform":"reference","total":139,"parts":["sand-charts","meeting-scheduler","quiet-charts","sheet-chart-suggest","more-chart-types","pris82
17:34:55find_parts{"job":"KPI number with percentage of capacity used, like a car deck fill bar","limit":6}{"platform":"reference","total":69,"parts":["steady-fields","race-car","gpu-crossfilter","intent-bar","sand-charts","hold-to-confirm"],"fits114
17:34:55find_parts{"job":"announce live status changes to screen readers once without repeating","limit":6}{"platform":"reference","total":120,"parts":["chart-access","connectors-layouts","cell-membranes","colour-vision","video-textures","read-rev145
17:35:02get_playbook{"id":"placement"}{"id":"placement","title":"Placement and layout"}1
17:35:02get_playbook{"id":"accessibility"}{"id":"accessibility","title":"Accessibility baseline"}1
17:35:02get_playbook{"id":"motion"}{"id":"motion","title":"Motion and feel"}1
17:35:02get_playbook{"id":"performance"}{"id":"performance","title":"Performance budgets"}2
17:35:02get_playbook{"id":"resilient-layout"}{"id":"resilient-layout","title":"Layouts that never break"}2
17:35:16get_playbook{}{"listed":12}2
17:35:16get_recipe{"scenario":"a calm ferry duty desk dashboard: route status list, a hand-built SVG sea chart of boat positions, a dragga{"kit":"dashboard","tone":"strict","steps":11,"parts":["appearance-theme","accessible-dialog","menu-skins","tabs-tooltips","steady-fields","87
17:35:28get_part{"id":"appearance-theme"}{"id":"appearance-theme","licensed":true,"version":"1.0.1","pitfalls":14}7
17:35:28get_part{"id":"quiet-charts"}{"id":"quiet-charts","licensed":true,"version":"1.0.1","pitfalls":11}4
17:35:28get_part{"id":"keyboard-shortcuts"}{"id":"keyboard-shortcuts","licensed":true,"version":"1.0.2","pitfalls":10}11
17:35:28get_part{"id":"chart-access"}{"id":"chart-access","licensed":true,"version":"1.0.0","pitfalls":8}11
17:35:28get_part{"id":"loading-states"}{"id":"loading-states","licensed":true,"version":"1.0.1","pitfalls":9}11
17:35:35resources/read{"uri":"feature-store://SCHEMA.md"}2
17:35:40install{"id":"appearance-theme","version":"1.0.1"}{"id":"appearance-theme","version":"1.0.1","files":9,"left":0}23
17:35:57install{"id":"quiet-charts","version":"1.0.1"}{"id":"quiet-charts","version":"1.0.1","files":6,"left":0}6
17:35:57install{"id":"chart-access","version":"1.0.0"}{"id":"chart-access","version":"1.0.0","files":6,"left":0}11
17:35:57install{"id":"loading-states","version":"1.0.1"}{"id":"loading-states","version":"1.0.1","files":6,"left":0}12
17:35:57install{"id":"keyboard-shortcuts","version":"1.0.2"}{"id":"keyboard-shortcuts","version":"1.0.2","files":8,"left":0}13
17:36:22install{"id":"ink"}No part called ink. find_parts finds parts by the job.2
17:36:25check_look{"look":"ink","level":"tuned","dials":{"liveliness":0,"fidelity":30,"density":70},"overrides":{"light":{"--accent":"#1f5{"look":"ink","level":"tuned","ok":true,"label":"Paper and ink, tuned","problems":0,"knobs":["--accent","--on-accent","--accent","--on-accen7
17:36:36install{"id":"looks/ink"}No part called looks/ink. find_parts finds parts by the job.1
17:36:36find_parts{"job":"the Paper and ink look stylesheet and shared tokens.css and dials.css to restyle every part","limit":5}{"platform":"reference","total":156,"parts":["accessible-dialog","hold-to-confirm","noren-banners","gpu-page-runtime","voxel-dissolve"],"fit41
17:50:04check{}{"rules":"a998805d366f","catalogue":"2026-11-16T17:10:27.488Z","licensed":true}15
17:52:49install{"id":"ink"}{"id":"ink","version":"library-5dbf68e","files":7,"left":0}13
17:53:05get_playbook{"id":"placement"}{"id":"placement","title":"Placement and layout"}2
17:53:05get_playbook{"id":"performance"}{"id":"performance","title":"Performance budgets"}3
17:53:05get_playbook{"id":"accessibility"}{"id":"accessibility","title":"Accessibility baseline"}4
17:53:05get_playbook{"id":"motion"}{"id":"motion","title":"Motion and feel"}3
17:53:05get_playbook{"id":"resilient-layout"}{"id":"resilient-layout","title":"Layouts that never break"}3
17:53:43check_look{"look":"ink","level":"tuned","dials":{"liveliness":0,"fidelity":30,"density":30},"overrides":{"light":{"--accent":"#1f5{"look":"ink","level":"tuned","ok":true,"label":"Paper and ink, tuned","problems":0,"knobs":["--accent","--on-accent","--accent","--on-accen7