Chapter 17 : Best practices and security

The people who really save time with Jay share a handful of habits: they brief, they check, they keep what works, and they know what you don't hand over to an agent that has control of the computer.

Chapter 17 · 4 min read

The 15 golden rules

#The ruleWhy
1A 5-point brief for any task that mattersGoal, context, deliverable, criteria, example: less back and forth
2Let Jay ask you questionsIt spots what's missing before it gets things wrong
3One session per topicLong sessions mix topics and fill up the context
4One project per recurring topic, with its folderContext, memory and files stay clean
5Edit your first messageThe fix pays off every time after that
6Anything you correct twice becomes a ruleIn the JAY.md, a Skill or your job profile
7The right mode for the right taskThinking or Expert for what matters, Adaptive for the rest
8Ask for sources and uncertaintyYou know where to check and what's shaky
9Calculations with code, in a spreadsheetA model doing math in its head can get it wrong; a formula can be checked
10A plan before any delegationYou correct course before it touches the files
11Drafts, never direct sendingYou keep the final say on what goes out
12Ask access to start withAutonomy is earned task by task
13Say where the result goesA deliverable has an address: a folder, the Atelier, a draft
14Keep your best promptsIn a "Prompts" project or in Skills: your memory won't be enough
15File each new feature under its building blockYou understand in five minutes what takes others a month to keep up with

The most common mistakes

The mistakeInstead
Using Jay like a search engine, one question at a timeOpen a folder to it and hand it a complete job, with a goal
Copying an answer without rereading it because it sounds confidentAsk for sources and uncertain points, and check the three main claims
A single 200-message session for everythingOne session per task, a project for what comes back, /compact when the meter rises
Leaving Full access on everywhere from day oneAsk first, then Auto task by task as trust builds; Full only for Atelier pieces and well-tested tasks
Launching a flow without having done it by handThe 3-day method: fine-tune first, schedule second
Hunting for the perfect prompt onlineWrite a clear brief about your situation: no generic prompt knows your folder

Checking without rereading everything

ReflexWhat you ask
Sources"Cite the source of every number and every fact, file and page."
Uncertainty"Flag what you're not sure about instead of guessing."
Second opinion"Reread your answer like a demanding expert: what's wrong, vague or missing?"
Calculation"Redo this calculation with code and show me the formula."
Opposing view"What's the best argument against your conclusion?"
Files touched"List every file you created, modified or moved in this turn." Or the drawer's Files tab

Security and privacy

Sensitive data. Personal data about clients or colleagues, confidential information, health data: check your company's policy first. The models are hosted in France and don't learn from your data, but a company rule comes before your settings.

Your credentials. Passwords, access keys, card codes: no task justifies pasting them into a session. In any case, Jay will never enter a card number, or a password outside a local page. Connector keys, on the other hand, go in the app's card, in Customize, where they stay on your Mac, encrypted.

The safeguards to set up on day one. Always denied commands in Settings, AI behavior (anything that deletes, sends or publishes). Default access in Work set back to Ask if you're just starting out. Your sensitive sites blocked in Settings, Browser. A Rule hook, in Customize, Advanced, that refuses any write to your archive folders. Touch ID if the Mac is shared.

Prompt injection. Chapter 9 explains it: content Jay reads can try to hijack it. If Jay suddenly proposes an action unrelated to your request, refuse it, keep confirmation on for important actions, and leave "Don't memorize sessions that read the web or an MCP" turned on.

For a one-off topic. An incognito session: nothing is saved, no memory, no sync, and reduced tools: read, search the web, write to a throwaway folder; no terminal, no browser, no connector.