Calibrated examples · finished pages install github

Six finished pages, start to end

The catalog shows one drawing per page type. These are whole pages: the kind of report, review board, explainer, spec sheet, app screen and form a team would share. Each starts with the request that made it and the numbers pasted with it, and lists the skill and parts it is built from.

Each page also chooses its own look from its subject: the palette, the headline face, the frame and the spacing. The drawings follow the same rules on every page.

All figures and instruments are live. Buttons and forms work. Every number is example data.

nopagetype
01Platform · weekly ops reportstatus report
02Release 2.4 · go / no-goreview board
03How a photo upload worksexplainer
04Orders API · v3spec sheet
05Workspace settings, in your brandapp screen
06New supplier sign-upform in steps
1 · Weekly ops reportstatus report · instruments, budget, lanes, roll-upexample 1/6

ask claudeMake this week's platform ops report as a Calibrated artifact. Lead with what needs attention.

pasted with iterror budget 612 of 1000 min on day 19 · CI 41.2k of 50k min · release 2.14 canary: 4 of 6 regions, ap-south rolling · this week's 4 deploys with diffs

skill
calibrated-artifacts
figures
budget · lanes
instruments
<cal-meter> · <cal-progress> · <cal-durations> · <cal-diff>
parts
mast · intro · sections · counts · table · foot
look
control room: cool grey, orange lamp · Chivo bold caps
Platform ops report · week 44 data at fri 31 oct · 17:00

2.14 is rolling out to ap-south. CI minutes are past their alert.

The error budget is fine for now, but at this week's pace it crosses the 80% alert on day 25. CI is at 82% of its allowance with ten days left in the cycle: the e2e suite doubled after the checkout tests landed.

1 · Nowlimits and what is runningsheet 1/3
error budget · 30 days
ci minutes · cycle to 10 nov
release 2.14 · regions
this week
2.14 pipeline · today
2 · Detailwhere the pace lands · the canary per regionsheet 2/3
BudgetMinutes used, both alerts, and where this week's pace lands on day 30.
CanaryMinutes per region on one ruler. ap-south is still going.
3 · Roll-upevery deploy, a week per pagesheet 3/3
noservicechangediffci minstatus
01checkout-apirate-limit login attempts1 840rolling
02paymentsretry with idempotency keys610live
03cartremove legacy coupons420live
04e2e suitecheckout tests, 3 browsers6 900over ci budget
week 44 · 4 deploys
platform · ops-044source: grafana, github actions · fri 17:00
2 · Release go / no-goreview board · cards, sign-off, revisionsexample 2/6

ask claudeTurn the release 2.4 checklist into a Calibrated go / no-go board. One card per gate, with go / hold, and a sign-off I can paste into Slack.

pasted with itgit log of release/2.4 (5 commits, main 1 ahead) · migration log, 10 steps · the 6 PRs and the services each one touches

skill
calibrated-artifacts
figures
merge · timeline · matrix
parts
cards with today / drawn · keep-drop sign-off · revision triangles · note pane · sticky tally
look
the defaults: film / night · Plex Mono caps · desk · cards
Release 2.4 go / no-go board rev B · thu 30 oct

Three gates decide whether 2.4 ships on Monday.

Each card is one gate, drawn from the logs. Mark it go or hold. When all three are signed, copy the sign-off into #release.

1 · Gatestoday · drawnsheet 1/3
01merge planrev A

Lands as a merge commit

main moved on by one commit, so this can't fast-forward. The three commands run in the order drawn.

branch
release/2.4 · 5 commits
files
9 · +212 −38
owner
Priya
today
git status
ahead5 commits
behind1 commit
git merge --no-ff release/2.4
drawn
02orders db migrationrev B

Ten steps in 21 minutes

The dry run on a copy of production. Step 6, the backfill, is a third of the run: it locks the orders table for 4 minutes, so it runs in the 02:00 window.

window
mon 02:00–03:00
lock
orders · 4m 10s
owner
Tomás
today
migrate · dry run
steps10 / 10 ok
total21m 46s
slowest6 · backfill 4m 10s
drawn
03blast radiusrev A

Checkout is touched three times

Six PRs across six services. Three of them change checkout, so its smoke tests run together, after the merge.

prs
#471 – #488
test
checkout smoke, all three
owner
Lena
today
services by pr
#471gateway, auth
#474checkout
#479checkout, payments
…3 more
drawn
2 · Revisionswhat changed since the first roundsheet 2/3
revchangedate
First round: three gates.28 oct
Gate 02: backfill moved to the 02:00 window after the dry run.30 oct
3 · Notegoes out with the sign-offsheet 3/3
Slack cuts the preview at 280 characters.
0 of 3 signed
release 2.4 · rel-024 · rev Bsource: git, migrate --dry-run, github prs
3 · How a photo upload worksexplainer · one worked example, measuredexample 3/6

ask claudeExplain what happens after a customer taps upload, for the support team, as a Calibrated explainer. Use one real photo as the example.

pasted with ittrace of one 12 MB photo through the pipeline · the resizer's job list · the account's storage breakdown

skill
calibrated-artifacts
figures
timeline · fanout · measured
parts
cards without compare · key/value facts · tiers
look
darkroom: graphite, violet lamp · Space Grotesk · paper · open
Photos how it works · for support drawing set · 3 sheets

One 12 MB photo, from the upload button to every screen.

A customer on a phone uploads one photo. It takes 15 seconds before it shows in their library, and most of that is the resizer making six copies. Here is where the time goes, who does the work and where the photo ends up.

1 · The triphow long each step takessheet 1/3
01upload pipeline

Six steps, 15 seconds

If a customer says “it's stuck”, it is almost always step 3. Anything past 30 seconds is worth a ticket.

input
IMG_4471.heic · 12 MB
output
6 sizes · 14 MB
slowest
resize · 6 s
2 · The workone job per size, in parallelsheet 2/3
02resizer

Six copies at once

The small sizes finish first, so the library shows a thumbnail before the full-size copy is ready.

workers
6 per photo
shows first
thumbnail · 0.4 s
last
original, re-encoded
3 · Where it landsthe customer's storage, and this photo in itsheet 3/3
03storage

26 MB of a 100 GB plan

The photo and its copies are a sliver of the plan. Copies count toward storage, which is the most common billing question.

plan
100 GB
used
4.4 GB
this photo
12 MB + 14 MB copies
Tell the customer

Keep the app open until the thumbnail shows. After that the upload is safe even if they close it.

Escalate

An upload past 30 seconds, or a photo that shows only as a thumbnail an hour later: send the photo id to #photos-oncall.

photos · exp-007source: trace 9f2c · 31 oct
4 · Orders API · v3spec sheet · drawing frame, title block, stampexample 4/6

ask claudeWrite the spec sheet for Orders API v3 in the Calibrated style, as an engineering drawing with a title block. Partners read this.

pasted with itthe OpenAPI file · network diagram notes · rate limits and timeouts · key rotation runbook · change log

skill
calibrated-artifacts
figures
section · loop
instruments
<cal-ruler> · <cal-meter>
parts
sheet with zones · title block · stamp · code block · revision table · parameters table
look
blueprint · Barlow Condensed · drawing sheet
Orders API spec sheet · v3 approved for use

Create, read and refund orders over HTTPS.

v3 adds refunds and drops the XML responses. Everything a partner can reach goes through the gateway; card data never leaves the vault.

1 · Boundarywhat a partner can reach · hatched means closedsheet 1/4
SectionInside the API boundary, open and closed.
2 · Limitsper partner keysheet 2/4
request timeout

Requests are cut at 10 s. Refunds can take up to 8 s.

payload

2 MB per request. Batch creates take up to 100 orders.

rate · acme today

600 per minute per key. Past 480 the response carries a warning header.

3 · Key rotationevery 90 days · the step in progress is litsheet 3/4
CycleOld keys work for 14 days after a new one is issued.
rotate a key
# once every 90 days · about 10 minorders keys create --partner acmeorders keys deploy --partner acme --to prod# wait 14 days, thenorders keys revoke --partner acme --older-than 14dorders audit --partner acme --since 90d
4 · Endpointsparameters and statussheet 4/4
nomethodpathlimit / mintimeoutstatus
01POST/v3/orders60010 sstable
02GET/v3/orders/{id}1 2005 sstable
03POST/v3/orders/{id}/refunds 12010 sbeta
04GET/v2/orders.xml605 sremoved 1 jan
title
Orders API · v3
doc no.
API-031
sheet
1 / 1
rev
C
date
2026-10-29
owner
orders team
approved
M. Okafor
revchangedate
First release of v3.2026-08-04
Payload limit raised to 2 MB.2026-09-15
Refunds endpoint, in beta.2026-10-29
orders api · api-031 · rev Cpartner copy · public
5 · Workspace settingsapp screen · your colours · the form worksexample 5/6

ask claudeBuild the usage and limits screen for our app with the Calibrated components, in our brand: navy page, white ink, cyan lamp.

pasted with itbrand colours · the current settings page · the usage API response

skill
calibrated-tokens · calibrated-components
instruments
<cal-meter> · <cal-position> · <cal-durations>
parts
tabs with counts · rows · number with units · range · tag input · a field with an error · checkbox · search with an empty state · dialog with radio and date · toasts
theme
three seed colours: --bg --fg --live
look
the brand’s colours (pick below) · IBM Plex Sans Condensed
Northwind workspace · acme
mobile app · this month
events
seats
storage
scheduled exports · last run
limits
events / mo
Events past the cap are dropped, not billed.
050%100%
Enter a full address, like ops@acme.com.
also tell
#mobile#ops
api keys04keys
nonamekeylast usedstatus
01ios releasenw_live_…8f2c2 min agoactive
02android releasenw_live_…a71ejust nowsending
03ci · read onlynw_read_…5d10yesterdayactive
04old sdknw_live_…03b941 days agorevoked
Danger zonecan't be undone

Delete the Mobile app project.

Events, exports and its 3 active keys go with it.

delete mobile appesc

The project, its events and its exports are removed. Its API keys stop working at once.

events
2.3M
api keys
3 active
members
6 lose access
new api keyesc
can
90 days is the default. Rotate before then.
northwind · settingsseats are full · add one in billing
6 · New supplier sign-upform in steps · every field worksexample 6/6

ask claudeMake the sign-up form for new suppliers as a Calibrated page, in steps: company, documents, terms, then a review before they send it.

pasted with itthe paper form suppliers fill in today · the payment terms we offer · the documents food safety asks for

skill
calibrated-components
parts
steps · fields with an error · select · tag input · file drop · radio · date and time · note pane · key/value review · checkbox · stamp · status badge · node row while sending
look
ledger: warm paper, ink-blue lamp · Archivo wide caps
Harbourline suppliers · sign-up draft

Supply Harbourline kitchens in four short steps.

Tell us who you are, add two documents and pick your payment terms. It takes about six minutes. Procurement replies within two working days.

  1. 01company
  2. 02documents
  3. 03terms
  4. 04review
1 · Companyas on your invoices
you supply
dairyeggs
Kitchens search suppliers by these words.
harbourline · supplier sign-upform sup-01 · 4 steps
Make your owninstall once, then ask in plain wordsemdmed/calibrated
1 · Install

Paste both lines into Claude Code.

/plugin marketplace add emdmed/calibrated
/plugin install calibrated@calibrated
2 · Ask

Copy any request above, paste your own numbers after it, and say “in the Calibrated style”.

3 · Look closer

The catalog flips every page type between plain and calibrated. The reference has every part and its code.

catalog reference