The building blocks
The next five pages describe the parts the builder is made of. They are easier to read once it is clear what each part is for, so this page introduces all five in one place - what each one does, and why we chose to work this way.
The five parts
| Part | What it is | Why we use it |
|---|---|---|
| Tools | The actions the agent can take: look at the project, save the design, write the payment code, build the app, start it. | The payment code is the part that must be exactly right. Tools write it the same way every time, from Nuvei's own integration, instead of letting the agent improvise it. |
| Skills | Short guides that tell the agent how to carry out one task, and which tools that task needs. | Having the right tools is not enough - they have to be used in the right order. Skills are the instructions for that. |
| Rules | The things that must always be true, plus the reference material: what the SDK's methods actually look like, where secrets are allowed to live. | This is what stops the agent from guessing. When it needs a fact about Nuvei, it reads it rather than inventing it. |
| Commands | Shortcuts typed into the chat, like /design-app. | So the whole process can be started with one phrase, without knowing any of the names on this page. |
| Hooks | An optional safety net that runs beside the agent and can stop an action before it happens. | The parts above only cover what the builder itself does. Hooks cover the rest - a stray command, an edited file, something pasted into the chat. |
How they fit together
What the agent knows. Rules and skills are written into the project as plain files. The rules are the facts and the limits; the skills are the procedures. The agent reads them the way a new developer would read a handbook before starting.
What the agent does. Tools are the actions themselves. Anything that has to be correct rather than creative - the payment code, the backend, the build - happens through a tool, so it is generated rather than hand-written.
What protects the user. Hooks sit outside all of that. If something is about to put Nuvei account details somewhere they don't belong, the hook stops it and explains why.
Commands are simply the way in: the user types one, and the layers above do the rest.
Why it is split up this way
Designing the app - the screens, the look, the flow - is the part where the agent is genuinely useful, and it is left completely free there. Connecting to a payment provider is the opposite: there is one correct way to do it, mistakes are expensive, and account details must never end up in the wrong place. So that half is not left to the agent's judgement at all. It is written by tools, bounded by rules, and watched by hooks.