Give an AI client standing rules for a ThinkForge project in a root file named THINKFORGE.md. Use it for terminology, writing style, where work belongs, and checks the client should make.
Create the file
Create one Markdown file named THINKFORGE.md directly inside the project folder. It is optional. Files such as AGENTS.md or CLAUDE.md do not replace it for ThinkForge MCP.
Keep the rules short and specific. Put lasting project knowledge in ordinary documents and temporary task instructions in the current conversation.
For example:
# Project rules
- Write for customers using the current product.
- Use the exact labels shown in the app.
- Read the whole document before revising it.
- Keep existing document names unless a rename is required.
Have the client use the rules
Ask the connected client to read the project's instructions before doing other work. ThinkForge MCP provides get_project_instructions for that purpose.
Name the project when several are available. Otherwise, the client uses the desktop's active project.
A project without an instructions file still works normally.
Change the rules
Ask the connected client to update THINKFORGE.md through set_project_instructions. Updating an existing file requires its current content hash, so the client cannot silently overwrite a newer version.
ThinkForge keeps the first instructions it read while the app is running. This also applies if the file was missing or empty.
Restart ThinkForge after creating or changing the file. The change is saved immediately, but clients will continue receiving the cached instructions until that restart.
The file must be valid UTF-8 and no larger than 64 KB. If it is open in ThinkForge, finish and close it before requesting an MCP update.
Review the client's work
Project instructions guide the AI client; they do not enforce permissions or guarantee correct work. Give each task clear scope and review important changes.
For connection setup, see ThinkForge MCP.