The agent kit in Strict One
Four blocks for an agent's side of a conversation, in Strict One's spacing, type and colors. The page below is built from the same files the command installs. The shop and the order in it are made up.
npx shadcn@latest add https://strictthemes.com/r/strict-one.json https://strictthemes.com/r/strict-one-agent-kit.jsonOne block at a time
Tool call
One call an agent made to a tool: its name, whether it is running, done or failed, and on demand what went in and what came back.
Add the tool call block and the themenpx shadcn@latest add https://strictthemes.com/r/strict-one.json https://strictthemes.com/r/strict-one-agent-tool-call.jsonApproval
A request to do something the agent may not do on its own: what will happen, the exact command, and buttons to allow or deny it. The answer stays on screen.
Add the approval block and the themenpx shadcn@latest add https://strictthemes.com/r/strict-one.json https://strictthemes.com/r/strict-one-agent-approval.jsonStream
An answer that is still being written: the text so far with a caret, a line that says the agent is working, and a button to stop it.
Add the stream block and the themenpx shadcn@latest add https://strictthemes.com/r/strict-one.json https://strictthemes.com/r/strict-one-agent-stream.jsonCitations
A numbered marker for running text and the list of sources it points at, each with its title, where it is from and the passage that was used.
Add the citations block and the themenpx shadcn@latest add https://strictthemes.com/r/strict-one.json https://strictthemes.com/r/strict-one-agent-citations.json
In a project that already has Strict One, the second address in a command is enough. The files land in components/agent, and they are yours to change.