Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/xxyoudeadpunkxx/sensecraftxstudio/llms.txt

Use this file to discover all available pages before exploring further.

SensecraftXStudio requires no installation, build step, or configuration. The entire setup is a single file drop and two lines of text in your AI assistant session. The four steps below take under a minute to complete, and the contract is active for the rest of the session from that point forward.
1

Copy AGENTS.md into your project root

Download or copy AGENTS.md from the SensecraftXStudio repository and place it at the root of the project where your AI assistant will be working. The file must be accessible to the assistant in its workspace — placing it at the root ensures it is found without ambiguity.
2

Start a fresh assistant session

Open a new session with your AI coding assistant and give it access to your workspace. Starting fresh ensures there is no prior session context that could silently subordinate the contract before it is activated.
3

Send the activation instruction

Before giving the assistant any task, send this instruction exactly:
Read AGENTS.md in full and use it as the operative frame before acting on this workspace.
This instruction does three things: it directs the assistant to read the file in full, it establishes the contract as the operative frame (not background reading), and it scopes that frame to the current workspace before any action begins.
4

Give the real task

Once the assistant confirms activation, give it the actual work you need done. The contract is now the governing frame for how the assistant reads, executes, and reports on that task.
Review this repository and identify the smallest safe fix for the failing build.
Keep AGENTS.md active for the full session, not just at the start. The contract governs every response — not only the first one. If the assistant starts treating it as background context or stops reflecting its constraints in subsequent moves, that is drift, and the contract needs to be re-activated before proceeding.
Contract drift happens gradually: the contract becomes a one-time read, then memory-only guidance, then background context with no effect on the next move. Learn what drift looks like and how to recover at /contract/activation.

Build docs developers (and LLMs) love

Get started for freeTalk to us