DocsBuilding

Project instructions

Standing instructions that apply to every build in a project — brand voice, design rules, things opix should always or never do.

Instructions that persist

Open the project menu and choose Project instructions. Whatever you write there is injected into every build turn of that project as standing instructions — you set it once instead of repeating it in every message.

Good uses:

  • Brand facts — company name, address, opening hours, links that must be correct everywhere.
  • Design rules — "primary color is #0E4F3A", "never use stock-photo-style imagery", "German copy, formal Sie".
  • Behavioral guardrails — "never change the pricing section without being asked", "all forms must have a privacy checkbox".
  • Domain context — what the product is, who the audience is, terminology to use.

How it behaves

  • Instructions apply to every subsequent build turn in that project (up to 4,000 characters).
  • They guide the build like your prompt does — your explicit message always stays in charge for the turn at hand.
  • Editing them takes effect on the next turn; there's no rebuild needed just for changing instructions.

Project instructions are per-project. For steering a single message, magic words or plain prompt text are the lighter tool.

Next upImages & uploads

Build something with opix

Start free