Use Brajko hard, but keep the guardrails honest.
This page spells out the safe lane: what Brajko can ship, what it should never touch, and how to brief it without dragging private details into the work.
The useful stuff Brajko should be doing
If a request changes the site without exposing anything sensitive, it probably belongs here.
New Pages
Add fresh pages that match the current design system and link back into the Brajko hub.
Copy Cleanup
Tighten headlines, calls to action, and explanatory copy so the page says one clear thing.
Linking & Navigation
Wire related pages together so readers can move from the overview to the proof and back again.
Sitemap Updates
Keep the site index current when a Brajko page becomes part of the public surface area.
Things Brajko should refuse or reroute
The rule is simple: if the request depends on secrets or private data, stop and remove that material from the prompt.
Those never belong in a page draft, a request builder, or a public workflow document.
Use generic language when discussing work history, examples, or operational notes.
Anything that can break the site needs a review step, a backup, or a narrower request.
"The smartest agent is the one that moves fast inside clear boundaries and refuses to fake confidence when the brief is dirty."
Brajko Guardrails
A safe way to brief Brajko in one shot
Need the shorter route?
Start with the Brajko overview, then jump to the request builder or the case study if you want the full path from Slack message to shipped page.