Experts
An expert is a folder of plain text files. Workpen knows nothing about websites, books or any other kind of content. Everything it needs to do a job well lives in the expert, so a new kind of work is a new folder.
webdev/
expert.json settings: version, programs, actions, MCP endpoints
overview.md what the expert is for, shown to you and to other experts
rules.md short core rules, always sent to the model
resources/ reference notes, one topic each
outputs/ the files the work must produce
prompts/ questionnaires and reusable snippets
examples/ complete worked results
What each part does
- Overview is one sentence and a few lines. It is what you see when you choose an expert.
- Rules are short and always in front of the model. They describe the work in order: interview, plan, build, check.
- Resources are reference notes the model opens when it needs them. Each starts with a name and a line saying when to use it, and Workpen builds an index from those lines.
- Outputs list the files the work must produce, so Workpen can tell you when one is missing.
- Prompts hold the questions to ask and snippets to reuse.
- Actions are the only way an expert runs a program, such as a checker. Each runs one program from your Programs list, without a shell, and you are asked the first time an expert uses a program.
- Learned rules are the only thing the model can add, and only after you accept it. They are kept apart from the expert, in your own folder.
An expert reads its own folder and never changes it.
In development
These experts are being written and tested. Nothing is included with the app yet.
- webdev builds and changes websites, from a small static site to a project with a build step or a backend.
- expert-expert writes and revises experts, so you can make your own.
Your own
An expert is a folder in the experts folder in your Workpen documents. Copy one, edit its files in any text editor, and it shows up in the /experts command the next time you type it. You can also ask expert-expert to write one with you.