Platforms · Ecosystems · Agents

Platform designs that
stay consistent.

Human-readable. Agent-writable. Checked against the method.

pdt42 is a CLI and a skill for your coding agent. It walks the agent through the Platform Design Toolkit one step at a time, and your agent works through it with you.

$ npx skills add mrsimpson/pdt42

Get started

You

Give your agent the skill and the CLI

The skill teaches your agent the format and the workflow; the CLI guides it step by step.

npx skills add mrsimpson/pdt42
npm install -g @pdt42/cli

Talk platform design with your agent

"Let's explore a platform for … — use pdt42 and guide me through it"

Then open pdt42 serve to read the design and its canvases while it grows.

AI agent

Use the CLI

pdt42 next names the step to work on, pdt42 guide step gives its brief and a starter template, pdt42 explain a block's attributes, pdt42 validate what is inconsistent. Add --format json for output to parse. Entities, motivations and assumptions come from the people in the ecosystem, so ask your human rather than invent them.

npx @pdt42/cli next
npx @pdt42/cli guide step D1
npx @pdt42/cli validate

pdt42 build --out site writes a static site; --single-file one page to share.

Clear guidance, at every step

Your agent never has to guess what comes next. pdt42 names the step, briefs it and checks the result. Here, an agent starts a platform design from scratch.

agent + pdt42
  • What's next. pdt42 next names the step to work on and why. It reads that from the design itself, so you can stop at any point and pick up where you left off.
  • How to do it. pdt42 guide step briefs the step: the question to answer, what to ask you, which blocks to write, which canvas to place.
  • What's missing. pdt42 validate names each gap and how to close it: a missing canvas, a dangling reference, an incomplete portrait.
  • A sparring partner. Guided by the method, your agent asks its questions: who really produces value here, what do they exchange, what would make them come back?

Innovation stays human. Which relationship is core, which play to make, what the platform promises: the insight is yours. The agent keeps it in order.

Platforms are everywhere. Designing them is not.

Much of how business works today runs through platforms: marketplaces, networks, cooperatives, ecosystems of partners building on each other. We can model the organisation that runs a platform — its teams, roles and decisions, as organisational modelling does. But that describes the business behind the platform, not the platform itself.

Platforms create value in a peculiar way. They do not make the value; they make it easier for others to exchange it — and to learn and grow while they do. Who produces, who consumes, which transactions matter, which services lower their cost, what makes the network more valuable with every new member: that is a design of its own.

The Platform Design Toolkit by Boundaryless gives this design a method and a model: phases, steps and a canvas for each. But on paper and whiteboards, the canvases drift apart as the design evolves — the entity on one canvas is renamed on another, a transaction has no channel, the learning engine forgets a role.

pdt42 lets you ideate and shape everything together with your agent — and keeps it consistent. The design lives in Markdown chapters with small typed blocks; the canvases are drawn from them, so they cannot disagree.

One model, every canvas

Harvest Commons in pdt42 serve: read by a human, extended by an agent.

Every chapter shows its canvas

A chapter is one step of the method. Next to its prose sits the step's canvas — the ecosystem as rings of roles, the transactions board of a relationship, the learning engine of each role — drawn from the elements the chapter defines.

The Ecosystem Canvas of Harvest Commons: the cooperative in the centre, partners, producers and consumers, stakeholders on the outer ring

Prose and model, one click apart

Every element is written as prose for people and a small block for the model. Click the stripe beside the prose and it turns into its model box: the attributes, who refers to it, and every canvas it appears on.

The model box of the entity Small-scale farmers: role, layer, portrait attributes, incoming references and the canvases it appears on

Stickies are links

Every sticky on a canvas is an element of the model. Click one and you land on its section, its model box open — wherever in the design it is defined.

The Transactions Board for farmer and restaurant: transactions with direction, value unit and channel

Consistent by construction

When the agent adds a relationship and its first transaction, pdt42 asks for the chapter's canvas: a warning names the missing Transactions Board and the block to add. Every reference must resolve; every step knows what it still lacks.

Warning W011 at the top of the transactions chapter: no Transactions Board for Artisan and household

What the agent reads

Switch to the agent view and the chapter shows its source: Markdown with typed pdt42 blocks. Plain files in your repository — diffable, reviewable, and easy for an agent to write correctly.

The agent view of the transactions chapter: headings, prose and transaction blocks as source

The method, step by step

The three phases of the Platform Design Toolkit, each step with the canvas its chapter shows. Straight from the model pdt42 guide teaches.