TinTinWorkflows
GitHubSign in

Diagrams from a brief, with Mermaid source you keep

Describe a process or a system. Tin turns it into one clear diagram in a consistent style, and the Mermaid source stays editable in project Files.

Find it on GitHub
codex mcp add tin --url https://app.tin.computer/mcp

What the workflow does

A Tin workflow is a repeatable job: declared inputs, a bounded run and a defined output. The steps below are what this one does, every time.

  1. 01Reads your brief and any context you attach.
  2. 02Writes the diagram as Mermaid, in the direction you ask for.
  3. 03Renders it in a consistent style for review.
  4. 04Saves diagrams/{slug}.mmd so the next edit is a text change.
ask your agent

Create a Tin diagram of our ingestion pipeline from the code in services/ingest.

workflow keycontent.diagram
required inputs
briefslug
optional inputs
directioncontext
outputdiagrams/{slug}.mmd
needsNothing beyond a Tin project.
guardrailHuman review.

What every workflow here comes with

Battle tested on real products

These are the workflows we run for real companies. Claw Messenger went from about $45 to $2,105 in monthly revenue in 124 days on them. Each one has declared inputs, bounded execution and tests, and anything public waits for your review.

See the case study →

Open source: read it, fork it, self-host it

Apache 2.0. Every workflow is a folder in the repository: the steps it runs, the data it reads and what it is allowed to do. Change it, or run the whole system on your own machine.

Open the repo →

Runs on the agent that already knows your product

An agent that can read the system draws it correctly. One that only reads your description draws your description.

All workflows →

Using something else for this today?

What this workflow replaces in each product, and what it does not.

Questions

Can I edit the diagram afterwards?

Yes. The source is Mermaid text in your project, so it diffs and versions like code.

Is this a drag-and-drop canvas?

No. It is diagram as code. If your team wants a shared whiteboard, a canvas tool fits better.

Is Tin really open source?

Yes. Tin is licensed under Apache 2.0 and the source is at github.com/tin-computer/tin. You can read every workflow, change it, and self-host the whole system.

Which coding agents can run Tin workflows?

Any agent that speaks MCP, including Claude Code, Codex and Cursor. There is also an API, and the same projects run in the browser at app.tin.computer.

Why run marketing from a coding agent?

Because it already knows your product. It has the repository open, so it fills workflow inputs accurately, reviews output against what the product really does, and can act on the results in the same session.

Add Tin to your coding agent

Run this once in your terminal. It connects Tin to your agent and opens the sign-in. Then ask your agent to grow your project.

Find it on GitHub
codex mcp add tin --url https://app.tin.computer/mcp