A plugin for Claude Code and Cowork
Most AI tools help you build faster. This one slows you down where speed is expensive.
A staged process for web projects — landing page to bespoke portal — where every stage ends in a gate that a person has to pass. Built for small organizations, where the real risks aren't technical.
The idea
A gate is passed by a person, never by the model
Twenty-five skills run a project from intake to post-launch. Each one produces something, then stops: it states what it made, checks its exit criteria one by one, names what becomes expensive to reverse — and waits.
It won't pass a gate on your behalf, and it won't start the next stage in the same breath as asking for sign-off.
Why this matters. A wrong colour costs an afternoon. A wrong content model is discovered at launch and costs a migration. The gates sit where the second kind of mistake gets made.
When a later stage finds a problem that belongs to an earlier one, it says so and asks whether to reopen it — rather than patching a content-model defect inside a build, which is how projects become unmaintainable without anyone noticing.
Sizing
A ten-stage pipeline over a landing page is ceremony, not rigour
Projects are sized onto a track first, on structure rather than page count. Three pages backed by a model that grows to three hundred items is still a Portal.
Page
One page, one action. Discovery in fifteen minutes, a one-page scope, no content model, one screen with its states.
Site
Five to twenty pages of largely fixed content. Compressed throughout; a sitemap and a content type or two.
Portal
Structured content at volume, or an application. Search, contribution, moderation. The full pipeline.
Five gates never collapse, at any size: accessibility, data protection, account ownership, running cost and end-of-life, and where form data goes. A one-page site with an email capture form carries the same legal obligation as a portal — and usually gets less scrutiny.
The pipeline
Fifteen staged skills, each with an exit gate
Plus ten skills outside the sequence — site audit, content strategy, content rights, risk register, licensing, scaffold, documentation, stakeholder review, funder reporting — and three agents, including a gate reviewer that runs on a strong model and checks a deliverable against its exit criteria before you sign it off.
What binds every stage
Never guess. Always verify. Say when you didn't.
- Never guess, never assumeAn assumption labelled as one is legitimate work. An assumption presented as a finding is a defect — and the kind that survives review, because it reads like knowledge.
- Always verifyOpen the file. Read the section. Run the check. Never describe behaviour inferred from a filename.
- Read the codeWhere a codebase exists it is the authority on current behaviour — above documentation, above recollection. When they disagree, that disagreement is itself a finding.
- Check the docsOfficial documentation for the version actually in use. Not training data. Library APIs, pricing and free tiers all change.
- Cite referencesFile and line. Document and section. URL and date checked. A claim with no citation is marked unverified.
- The right solution, not the easiestRight is not the same as elaborate. For a small organisation it is usually simpler. What it excludes is the shortcut chosen because it's quicker to produce.
- Say when you didn't do somethingA check that couldn't run, a stage that was skipped, a specialist pass that was unavailable — stated in the deliverable. Silence reads as completion.
Install
Two commands
/plugin marketplace add Domexo-Digital/Domexo-Web-Studio /plugin install domexo-web-studio@domexo-web-studio
In Cowork, the same thing is available through the plugin browser. Then ask it to run your project, or invoke any stage on its own — domexo-web-studio:prd gives you the requirements stage without the rest of the pipeline.
Two optional MCP servers (Playwright, GitHub) are declared but never block installation. Both need a local runtime, so they work in Claude Code and not in Cowork.