Ask Brajko like you mean it.

This playbook shows the safest, fastest way to turn a Slack message into useful website work: clear goals, visible constraints, no secrets, and enough context for Brajko to ship without babysitting.

Back to Brajko Read the case study

Good prompt

Add a new FAQ section to Brajko with one clear CTA.

Missing context

“Make it better” without a page, goal, or audience.

Rule

Be specific, stay public-safe, and name the page you want changed.

Prompt ingredients

What makes a Slack request actually shippable

Clear outcome

Say what should change and why it matters so Brajko can act instead of guessing.

Page name

Reference the exact page or feature so the request lands in the right file and flow.

Public-safe scope

Keep private details, secrets, and client-specific data out of the prompt and the output.

Acceptance check

State what “done” looks like so the result is easier to verify after the build.

Ready-made prompts

Three prompts that are worth sending

Short, concrete, and safe. These are designed to get Brajko to do work, not write back a thesis.

1. Content

Add a new section

“Update /brajko.html with one new section that explains how to ask for safe, production-ready edits, then link it from the final CTA.”

Why it works: one page, one change, one clear link target.

2. Workflow

Ship a small helper

“Create a Brajko helper page with sample prompts, then connect it back to the main Brajko page and the website-building case study.”

Why it works: it asks for a useful asset, not a vague redesign.

3. Safety

Keep it public-safe

“Make the copy public-safe, avoid private details, and keep the design consistent with the existing Brajko hub.”

Why it works: it sets a hard boundary without slowing the work down.

"The best Slack prompt is the one that leaves almost nothing to interpret."

Brajko Prompt Rule

Need the main Brajko page?

This playbook is the how. The Brajko page is the who. The case study is the proof.

Open Brajko Read Case Study