The gallery
40 documents, written by an agent
Each page below started as one sentence given to an AI agent with the Chiltepin skill installed and no block type named. The agent picked the blocks, wrote the document, ran chiltepin check, and fixed what it reported. The renderer drew every diagram. Nothing was edited afterwards — 13 September 2026.
Login flow
“How the login flow works across the SPA, the auth service, and Google.”
Flows & statec4+5 moreOrder lifecycle
“Show how an order moves from cart to delivered and what can go wrong at each stage.”
Flows & statestate+4 moreCheckout API latency — where one request spends its time
“Our checkout API got slow last week. Show where the time actually goes inside one request.”
Flows & statespans+3 moreBilling data model
“Explain the data model behind subscriptions, plans, invoices, and payments.”
Data modelerd+4 morePlatform shape
“Explain the shape of the platform to a new backend engineer: services, databases, third parties.”
Architecturec4+4 moreOrders service — regions, zones, and replicas
“Show how the service is laid out across regions and availability zones, with how many copies of each part run.”
Architectureblock+3 morePII data flow
“Where do PII fields flow through the system, from ingestion to the warehouse?”
Flows & statedfd+4 moreCache options for the Catalog API
“Compare the three caching options we discussed: Redis, Memcached, and an in-process LRU.”
Business & decisionsoptions+3 moreAdmin app visibility
“Explain who can see what in the admin app — the roles against the screens.”
Business & decisionsmatrix+4 moreQ3 delivery plan — mobile app 4.0
“Show the Q3 delivery plan for the mobile app with dates and dependencies.”
Planning & backlogsgantt+5 moreWhy deploys fail on Fridays
“Why do deploys keep failing on Fridays? Lay out the possible causes.”
Charts & overviewschart+5 moreAugust infra bill — where the +40% went
“The monthly infra bill grew 40% — break down where the money goes.”
Charts & overviewschart+5 moreOrders REST API
“Document the public REST API for the orders service.”
APIendpoint+4 moreRefund run — "refund my order"
“Show a real run of the agent handling "refund my order", turn by turn.”
AI & agentsagentloop+4 moreContainer With Most Water
“Explain the two-pointer approach for the "container with most water" problem.”
Algorithmsflow+5 moreCheckout outage — 14 Aug
“Postmortem for the outage on 14 Aug: what happened, in what order, and why.”
Planning & backlogstimeline+4 moreOrder events fan-out
“When an order is placed, five other services have to react to it without the order service knowing about any of them. Show how that works.”
Architectureblock+4 moreFeed fan-out
“Explain how a new post reaches every follower's feed quickly, and what we do differently for accounts with millions of followers.”
Architectureblock+5 moreOutbox for order events
“We lose events when the database commit succeeds but the publish to the broker fails. Document the fix we agreed on.”
Flows & statesequence+4 moreRead model for the product page
“Reads outnumber writes fifty to one and the product page query joins nine tables. Document the read-model approach we agreed on.”
Architecturestats+6 morePoison messages on the fulfillment queue
“A malformed message keeps crashing the consumer and blocks the whole queue behind it. Document how we handle that.”
Flows & stateblock+5 moreOrder stream partitioning and consumer group rebalance
“Show how the order stream is partitioned and what happens to the consumer group when we add or remove instances.”
Architectureblock+5 moreorder.placed event
“Document the order.placed event so other teams can consume it safely.”
APIeventcontract+4 moreShelfNet v3 — the shape of the image classifier
“Explain the shape of the image classifier we ship — what each layer does and how wide it is.”
AI & agentsstats+3 moreTicket-routing model — handoff
“Write the one-page handoff for the ticket-routing model so another team can decide whether to reuse it.”
AI & agentsmodelcard+4 moreOnboarding v2 — brainstorm
“Lay out everything we brainstormed for onboarding v2, grouped around the main idea.”
Charts & overviewsmindmap+2 morePentest findings — payments service
“Write up what the pentest found on the payments service, worst first, with what we do about each.”
Quality & auditsaudit+3 moreProduction readiness — search-indexer
“Go through the production-readiness standard for the search indexer and show what passes and what doesn't, with proof.”
Quality & auditschecklist+3 moreProduct page — web performance budgets
“Show how the product page does against our web performance budgets.”
Quality & auditsperfbudget+4 moreCheckout latency — the tail per endpoint
“The median looks fine but people complain checkout is slow — show the latency picture per endpoint.”
Quality & auditsstats+3 moreLogin path — threat model
“Threat-model the login path — where can it be attacked and what stops each attack?”
Quality & auditssequence+4 moreTicketing system — actors and feature dependencies
“Who does what with the ticketing system — customers, agents, the payment provider — and which features depend on others?”
Architectureusecase+3 moreBackend module dependency rules
“Document which backend modules are allowed to depend on which, so reviewers can enforce it.”
Architecturepkg+4 morePricing breaker — the 60 seconds of the 8 Sep outage
“Show what the circuit breaker and the downstream are doing over the sixty seconds of last week's outage.”
Flows & statetiming+4 moreThe incident process
“Deck opener for the incident process — the phases, and which one we are improving this quarter.”
Planning & backlogschevrons+4 morePlatform roadmap 2026
“The 2026 platform roadmap by theme and quarter, with where we are now.”
Planning & backlogschevrons+4 moreWhat breaks deploys
“Of the 140 failed deploys this year, show which few causes account for most of them.”
Charts & overviewschart+4 moreRequest latency across the fleet
“Show how request latency is distributed across the fleet and where our 250 ms alert threshold sits on that curve.”
Charts & overviewschart+3 moreRefund handoffs
“Document how a refund moves between support, finance, and the warehouse, and who owns each step.”
Flows & stateswimlane+4 moreRetry helper — what moved
“Explain the change we made to the retry helper so reviewers can see exactly what moved, with the new function they should call.”
Tables & codecode+4 more
The requests come from the generation eval in the product repo; the numbers behind it are on the homepage. To make your own, install the skill: npx skills add jdiejim/chiltepin -g.