Project Instructions

The assistant reads your setup exactly as it is stored. It can see that a campaign only shows when the cookie seg_vip equals true, but it cannot know that seg_vip marks a signed-in loyalty member. A few lines explaining your own setup are the difference between a technically correct answer and a useful one. Write them once and save them where your assistant reads them at the start of every conversation.

Where to save them

App	Where the instructions go
Claude (web, desktop)	Create a Project and add them as the project instructions, then chat inside it
ChatGPT	A Project’s instructions, or Settings → Personalization → Custom instructions
Claude Code	A `CLAUDE.md` file in the folder you work from
Cursor	Cursor Settings → Rules, or a rule file in `.cursor/rules`
Windsurf	Windsurf Settings → Rules, or a rule file in `.windsurf/rules`
Visual Studio Code	A `.github/copilot-instructions.md` file in the workspace
Gemini CLI	A `GEMINI.md` file in the folder you work from

If your app has none of these, paste the instructions as the first message of a conversation.

A starting point

Copy this, replace every line with your own, and delete what does not apply.

About our Fluentos setup

Business
- We sell outdoor equipment in Sweden, Norway, Denmark and Finland.
- Peak season is May to August, plus Black Week in November.
- A campaign is working if its engagement rate is above 8% and it collects
  signups. Impressions on their own are not a success measure.

Naming
- Anything starting with "TEST" or "OLD" is not live work. Leave it out of
  comparisons unless I ask.

Cookies in our display rules
- seg_vip = "true" means a signed-in loyalty member.
- cart_abandoned is set by our own script when a basket sits untouched for
  30 minutes.

Window variables in our display rules
- window.customerTier is "gold", "silver" or "none".
- window.pageType is "product", "category", "checkout" or "other".

DataHub values we push
- CART_TOTAL is the basket value in SEK, excluding VAT and shipping.

How I want answers
- Lead with what I should do, then the numbers behind it.
- Ignore campaigns with fewer than 200 impressions when comparing.

Keep the instructions about your business and your setup. The assistant already knows how Fluentos itself works, so the things worth writing down are the ones only you know:

Cookies: the name, the values it can take, and what a visitor did to get it.
Window variables: what your site puts there and when.
DataHub values: what the value represents and its unit. See DataHub for how values are pushed in.
Naming: markets, versions or owners your team puts into campaign names. It is also the simplest way to keep test campaigns out of a performance ranking.

Where to go next

Prompt Library: prompts for checking a campaign, reviewing performance and understanding your setup
Connect an AI Assistant: setting up the connection, and what the assistant can and cannot read