Write persistent instructions with Cline Rules
Cline Rules are Markdown files for persistent instructions across conversations. Use them for coding standards, project context, documentation or testing requirements, and explicit constraints. Cline Rules documentation
Workspace rules go in .clinerules/ or .cline/rules/ at the project root. Cline combines workspace and global rules, with workspace rules taking precedence when they conflict. Create rules in the Rules panel or ask Cline to create one with /newrule. Cline Rules documentation
Keep rules focused and current
Write specific rules, explain why a constraint exists, point to examples, and keep each file focused on one concern. Rules consume context tokens, so Cline’s documentation recommends concise rules that link to detailed reference material. Cline Rules documentation
Rules without frontmatter are always active. Conditional rules use YAML frontmatter and the supported paths condition to match files in the current context. Each rule can be enabled or disabled without deleting its file. Cline Rules documentation
Store project context in Memory Bank
Cline’s Memory Bank approach uses structured Markdown files in the project so you and Cline can access project knowledge. Its documented structure includes projectbrief.md, productContext.md, activeContext.md, systemPatterns.md, techContext.md, and progress.md. Memory Bank guide
To set it up, add the Memory Bank instructions to a Cline Rules file such as .clinerules/memory-bank.md, then ask Cline to “initialize memory bank.” The documented instructions tell Cline to read all Memory Bank files at the start of each task. Memory Bank guide
Update Memory Bank as work changes
The Memory Bank guide says activeContext.md tracks current focus, recent changes, and next steps. techContext.md records the stack, setup, constraints, and dependencies, while progress.md records what works, remaining work, and known issues. Memory Bank guide
Ask Cline to “update memory bank” after discovering project patterns or making significant changes. If a context window fills, the documented sequence is to update Memory Bank, start a new conversation, and ask Cline to follow custom instructions. Memory Bank guide
KnowMan MCP and Cline
KnowMan's MCP server is a local stdio server. The KnowMan MCP guide describes the server, but the available Cline documentation does not describe how to configure Cline to connect to it or use saved items. KnowMan MCP guide Cline Rules documentation
Cline Rules and Memory Bank provide project instructions and project files. Explore connecting an AI to your notes and a knowledge base for AI agents for related approaches.
Questions people ask
Where should I put Cline project rules?
Put workspace rules in .clinerules/ or .cline/rules/ at the project root. Cline combines them with global rules, and workspace rules take precedence when they conflict. Cline Rules documentation
How do I initialize Cline Memory Bank?
Add the Memory Bank instructions to a Cline Rules file, such as .clinerules/memory-bank.md, then ask Cline to “initialize memory bank.” The guide describes a set of structured Markdown files for project context. Memory Bank guide
Can Cline search my KnowMan library?
The available Cline documentation does not explain how Cline connects to or uses KnowMan's MCP server. KnowMan provides a local stdio MCP server; see the KnowMan MCP guide.
Can Cline save a new URL to KnowMan?
The available Cline documentation does not explain how Cline connects to or uses KnowMan's MCP server. KnowMan provides a local stdio MCP server; see the KnowMan MCP guide.