Chatbox & prompts
How to ask
The chatbox takes plain language. You don't need keywords or a syntax — describe the outcome and let it work out the steps.
What actually improves results is specificity about the business, not instructions about layout:
| Weak | Better |
|---|---|
| "Make a hero section" | "A hero for a solo accountant who works with freelancers" |
| "Add testimonials" | "Testimonials from small business owners, focused on saving time" |
| "Make it better" | "Make the tone warmer and less corporate" |
Selection matters
Most requests apply to whatever you have selected on the canvas. Select a section and ask for a change, and that section is what changes. Select nothing and you're talking about the page as a whole.
If a result lands somewhere unexpected, selection is usually why.
The @css agent
Type @css in the chatbox and it becomes a chip in front of your message. It's a dedicated agent: anything after it is treated as a CSS change to the selected section or element.
@cssgive this a subtle top border and more breathing room underneath
It writes real CSS using your project's design tokens rather than hardcoded values, so the result still responds to your brand settings.
@css only appears while you're in the page view — it needs a section or element to apply to.
It remembers
Brickser builds up context about your project as you work: facts it's learned about the business, and outputs you rejected. Later requests are shaped by both, so you shouldn't have to re-explain the brief every time.
If you rejected a direction once, it tries not to hand you the same thing again.
When you don't like the result
Just say so, in the same thread — "too formal", "shorter", "try a different angle". Iterating is cheaper and usually better than regenerating from scratch.
Undo works normally, too. Bricks' own history covers anything Brickser inserted.