Primacode
Skill: new-website
A guided build of a website for someone who does not write code, in six phases, one question at a time.
Live Built and working today on the surface this card describes.
What it does
Its own description: use when a person asks to build them a website, make a landing page, or create an online shop, or describes a business they want a site for, and they are not asking for a specific technical change.
Six phases: interview, say the plan back in their own words, choose the stack without asking them, build, review on their behalf, hand over.
It says what it can and cannot do first, in plain words, before asking anything, so that nobody discovers the limits after an hour of work.
The interview asks one question at a time. The skill is written as phases rather than as a list for exactly that reason.
The review phase runs the compliance and security skills on what was built, on the person's behalf, because they cannot ask for that themselves.
Inputs and outputs
| Input | A person describing what they want, not a specification. |
|---|---|
| Output | A running frontend and backend they can look at locally, plus a review. |
| Can | Interview, agree a plan, generate a real frontend and backend, run it locally, review it. |
| Cannot, today | Connect to a design tool, read a screenshot or a design image, copy an existing website, or deploy anywhere. |
Configuration
| How it is chosen | By name, or by the model matching the description this card opens with. That description is the routing rule, and it is what decides which of the nine runs. |
|---|---|
| Where it lives | Embedded in the binary as <name>/SKILL.md, on the branch that ships it. The same file is what the published catalog serves, so there is one copy in one layout. The catalog itself is built and verified and not yet uploaded to the portal. |
PRIMACODE_SKILLS_URL | Points the tool at a catalog of skills. Leave it alone unless you are serving a separate catalog. The nine that ship in the binary are already loaded without it. |
Limits
- It cannot deploy. The hand-over phase hands over a working local build, not a live site.
- It cannot read a design file or a screenshot. Someone with a design is asked to describe it, or to copy the colours and the text out of it.
- Not for editing an existing codebase, and not for a developer who already knows what they want built.
- Do not point the tool at the published catalog for these nine. The binary already embeds them, and the loader keys skills by name: a duplicate logs a warning and silently replaces rather than merging.
Example
what it says before it asks anything
Can: interview, agree a plan, generate a real frontend and backend,
run it locally so you can look at it, review it
Cannot: connect to Figma, read a screenshot, copy an existing website,
deploy anywhereSource of truth
primacode/.opencode/skills/new-website/SKILL.md (the checked-out copy; on branch `claim-event-model` the same file is embedded at packages/core/src/plugin/skill/primacode/new-website/SKILL.md, which is what a released binary carries)philosophers_stone/platform/primacode.md § Status (the nine skills ship in the binary, 2026-08-27)