looks
See the designed looks. The six designed looks, as pictures for the owner to choose from: each look's landing page on a desktop and a phone, with one line on its feel and who it suits. Use it when a company has no look yet, or the owner wants a new one; every site, email and invoice starts from a look, never freehand. code: true gives the code for a build on your own machine.
Where it is
In the online area (your website: pages, forms, sign-ups, the member area, selling, classes and calls, going live; its look; payment links; course progress; giving or taking away member access): open it with tools_for { area: "online" }, then call it with read_tool { name: "looks", args }.
Does it need a yes?
Reads only: it changes nothing. Here: the designed looks.
Inputs
| Input | Type | Needed | About |
|---|---|---|---|
run_id | string | no | The run_id from start. Pass it on every call: it keeps your task held. · 1 to 100 characters |
look | "journal" | "signal" | "hearth" | "gallery" | "onyx" | "market" | no | One look: its pictures and email. Left out: all six, two pictures each. |
code | boolean | no | true: code for building on your own machine (with look: its stylesheet; without: the shared kit). |
Example
{
"name": "looks",
"arguments": {}
}When it is refused
invalid: The input isn't right. The sentence names the field and the fix; nothing was done. Fix it and call again.not_found: No such thing in this company (a task, file, person, record). Check the number or name, or list first.not_allowed: Not without another step: the owner's yes, your own task held with pick_up, or a setting the owner turns on. The sentence says which.taken: Someone else holds it (another AI on that task). Pick another task.stale: It changed since you read it. Read it again and use the new version.failed: On our side or a service's, never your input. Try again in a minute; if it keeps failing, call report_problem.