Using Templates
Invoker ships with built-in templates so you can go from zero to a live page in one message. Templates are full HTML files that Claude can customize before deploying.
Available templates
There are two built-in templates:
| Template | Description |
|---|---|
waitlist | Email capture page with a gradient background, social proof counter, and a single email field |
contact | Multi-field contact form with floating labels, client-side validation, and a clean layout |
To see all available templates, ask Claude:
"List the available Invoker templates"
Claude calls list_templates and shows you what's available.
Getting a template's HTML
To retrieve the full source of a template:
"Show me the waitlist template"
Claude calls use_template with the template ID (e.g. waitlist) and gets back the complete HTML source. This is the raw HTML -- you can read through it, ask Claude to explain it, or deploy it as-is.
Customizing before deploy
The real power is modifying templates before they go live. You can ask Claude to change anything:
"Use the waitlist template but change the headline to 'Join the Acme Beta', make the background dark blue, and add a subtitle"
"Start from the contact template, remove the phone field, and add a dropdown for department"
Claude fetches the template source, makes the changes to the HTML, then deploys the modified version.
Deploying
Once Claude has the final HTML (original or modified), it calls deploy to push it live. You can optionally specify a slug:
"Deploy the waitlist template to acme-beta"
This creates the page at acme-beta.invoker.page. If you don't specify a slug, one is generated automatically.
Example workflow
A typical conversation might look like:
- You: "Create a waitlist page for my app called Nimbus. Use the waitlist template, change the colors to purple, and deploy it to nimbus-waitlist."
- Claude: Fetches the template, modifies colors and branding, deploys it.
- Claude: Returns the live URL:
nimbus-waitlist.invoker.page
Template source is just HTML
Templates are plain HTML files with inline CSS and JavaScript. There's nothing proprietary about them -- once Claude fetches the source, it can restructure, restyle, or rewrite any part of it.