Build for Plicine
These pages are for developers and their agents: making your own blocks and themes. A block is a small TypeScript and React package; a theme is CSS and a few HTML templates. If you or your agent can write those, you can make anything a page needs.
Every step works with nothing but the app installed. The plicine command comes inside it: Plicine > Install Command-Line Tool… puts it in your terminal (where it goes). The one extra is Bun, and only when a block has npm dependencies of its own.
What you make is a file in your own folder. A .block or a .theme sits in your vault, travels with it, and works for everyone who opens it, with no registry and no account.
| Page | What it's for |
|---|---|
| Writing a block | From create-block to a packed, approved block, and what makes a block pleasant to use |
| Writing a theme | From an empty folder to tokens, fonts, a cover and a running footer |
| Building with an AI agent | Briefing an agent, the tools Plicine gives it, and AGENTS.md |
| The .block package | Layout, manifest, the module contract, capabilities and what the compiler refuses |
| The .theme package | Layout, every token, the CSS hooks and the template variables |
It helps to have read Documents and How blocks work first. The built-in blocks a document can already use are in Core blocks, and the commands are in the CLI reference.