A DESIGN.md your coding agent can follow
Tin analyzes your project repository and publishes its DESIGN.md: the tokens, type and patterns the product really uses, written down so agents and people build on brand.
codex mcp add tin --url https://app.tin.computer/mcpWhat 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.
- 01Reads the repository's styles, components and tokens.
- 02Describes the system that is actually in use.
- 03Publishes DESIGN.md to the project.
Generate our DESIGN.md with Tin, then use it for every page you build.
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
Once DESIGN.md exists, every page your agent builds starts from your design system and not its defaults.
All workflows →Workflows that run well with this one
Questions
What is DESIGN.md for?
It is the design counterpart to agent instruction files: a single document that tells a coding agent how your product looks and why.
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.