All proposals
01 / 06Blueprint
4 logo concepts
clankerdocsSee it in action
VISUAL DOCUMENTS FOR CODING AGENTS

Beautiful documents.
Created by your agent.

Give your coding agent the tools to explain systems with rich diagrams, clear writing, and documents you can review.

Agent-authored Human-reviewed Rich visuals
ONE DOCUMENT. MORE WAYS TO EXPLAIN.
ArchitectureSequence diagramsDatabase schemasPseudocodeWireframes
BUILT FOR HOW AGENTS WORK

Your agent has more
to show you.

A Markdown file can describe a system. A rich document lets you follow its connections, inspect the details, and review the design in place.

Give your agent a shared document with expressive visuals, precise comments, and a history of every revision.

Try the example

One system.
Every important detail.

Select a service. Follow a request. Inspect the schema.
Then leave a comment and preview the agent's revision.

EngineeringOrder processingInteractive example
SYSTEM DESIGN / ENGINEERING Revision 01

How an order gets processed.

The API records each order before queuing it. A worker handles fulfillment, so checkout stays fast even when downstream services are slow.

Five services. One order.
Order processing architecture. Storefront to Order API, queue, worker, and Postgres.ORDER PROCESSINGPOST /orderspublishconsumeupdate statusrecord01 — CHECKOUTAn order, fromrequest to result.UIStorefrontThe checkout interfaceAPIOrder APIValidates and records ordersQOrder queueBuffers accepted ordersFNOrder workerProcesses queued ordersDBPostgresStores orders and results
Select a service to inspect it. Every view describes the same system.
FN
SELECTED COMPONENTOrder worker

Processes queued orders. Review the behavior in the connected views.

Design decision · Process orders asynchronously

Persist the order first. Keep fulfillment outside the checkout request.

01

Your agent creates.

The plan becomes a document with clear writing and useful visualizations.

02

You review.

Leave a precise comment on a component, diagram, or explanation.

03

Your agent revises.

The document improves. Every revision stays available in its history.

THE BLUEPRINT IDENTITY

Clear structure. Confident blue. A document at the center.

Blueprint makes the document the most recognizable part of the brand. A compact folded mark, confident cobalt, and a precise grid establish a dependable developer tool. Large, carefully composed diagrams show the quality of the output immediately.

Find the right signature.

Select a mark to see it applied throughout this proposal. Each concept is an original vector drawing.

Folded CRecommended

A folded document opens into a C. The broad edge gives it a strong silhouette at favicon size. Recommended for its immediate link to the name and product.

Page paths

Three nested page edges create a continuous reading path. The open corner gives an otherwise formal mark a distinctive profile.

Connected page

A document contains a branching system. The page and its diagram share the same geometry.

Double fold

Two facing folds form a compact document monogram. It works particularly well as a small, solid application mark.

One color
Reversed
App icon
16px24px32px
Actual sizes

Folded C is currently applied to the wordmark, document, and review interface.

INTER
Aa0123

Understand
the whole system.

BODY / INTERFACE / CODE

Order processing

The API records each order before adding it to the queue. A worker handles fulfillment and updates the order status.

ReviewedRevision 02
POST /orders → queue → worker

Inter keeps the identity crisp and familiar. Tight, substantial headlines sit above open, comfortable body text. Technical labels use a system monospace.

Aa#2455E8
CobaltBrand, primary actions, links
Aa#16233F
InkHeadlines and primary text
Aa#FFFFFF
PaperDocuments and working surfaces
Aa#EEF3FF
MistQuiet backgrounds and selected surfaces
Aa#CBD6EF
RuleDividers and decorative grids
Aa#7F65D6
IrisSecondary diagram emphasis
MESSAGING IN USE

Beautiful documents. Created by your agent.

Give your coding agent the tools to explain systems with rich diagrams, clear writing, and documents you can review.

Explain the architecture.Comment on the details.Keep every revision.
CREATE → EXPLAIN → REVIEW

Motion with a job to do.

Build the document in a clear sequence: title, explanation, architecture, review. A blue trace follows one request through the system, keeping every label still and readable.

Try the interactive example
clankerdocs

Beautiful documents.
Created by your agent.

clankerdocs.com
DOCUMENT VISUAL LANGUAGE
customersordersorder_items

One customer. Many orders.
Every connection, explained.

WHY THIS DIRECTION

The clearest category recognition and the easiest identity to carry into an everyday product.

THE TRADEOFF

Blue is familiar in document software. The folded silhouette and unusually good visual examples need to do the distinctive work.