Start with custom instructions
Use Roo Code custom instructions to shape its responses, coding style, and decisions. Roo Code supports global rules, workspace rules, and instructions entered through the Prompts tab. See Roo Code's custom instructions guide.
Choose global or workspace rules
Global rules apply across all projects. Put general global rules in ~/.roo/rules/ on Linux and macOS, or %USERPROFILE%\.roo\rules\ on Windows. Workspace rules apply only to the current project and take precedence when they conflict with global rules. See Roo Code's custom instructions guide.
Store project guidance in rule files
Roo Code prefers a .roo/rules/ directory for workspace-wide rules, with .roorules as a fallback. It reads files in .roo/rules/ recursively, including subdirectories, and adds their contents to the system prompt in alphabetical filename order. If the directory exists but is empty, Roo Code falls back to .roorules. See Roo Code's custom instructions guide.
Add instructions for a specific mode
Mode-specific instructions can be set through the Prompts tab or through rule files and directories. A mode-specific workspace directory is .roo/rules-{modeSlug}/, with .roorules-{modeSlug} as its fallback. Roo Code combines instructions from the Prompts tab, global rules, workspace rules, and mode-specific rules. See Roo Code's custom instructions guide.
Use agent rules for repository guidance
Roo Code loads workspace AGENTS.md or AGENT.md files automatically by default. If both exist, it prefers AGENTS.md. To disable this behavior, set "roo-cline.useAgentRules": false in VS Code settings. See Roo Code's custom instructions guide.
Keep project guidance in version control
Use workspace .roo/rules/ directories under version control to standardize Roo Code behavior for specific projects. See Roo Code's custom instructions guide. KnowMan is built for one person's library today, and team plans are not available yet.
Where KnowMan fits
Roo Code rules are suited to concise instructions and project guidance. KnowMan can save articles and links, read and tag them, answer questions with citations, and keep claims, decisions, and playbooks as memories. See the MCP server guide and guide to giving AI context. KnowMan runs locally with npx -y @knowman/mcp over stdio, and is also available as a hosted server at https://api.knowman.io/mcp.
Connect KnowMan to Roo Code
KnowMan provides a hosted MCP server at https://api.knowman.io/mcp. In clients that support remote MCP servers, add this URL and sign in on the KnowMan consent page, or use an API key as an Authorization: Bearer <key> header.
Roo Code rules can guide how an assistant uses project knowledge. KnowMan also runs locally with npx -y @knowman/mcp; see the open-source MCP client for its package details.
Questions people ask
Where should I put custom instructions for Roo Code?
Use the Prompts tab for direct instructions, global rules for guidance across projects, and workspace rules for a specific project. Roo Code combines these sources, with workspace rules taking precedence over conflicting global rules. See Roo Code's custom instructions guide.
Can Roo Code read reference files from a folder?
Yes. Roo Code reads .roo/rules/ recursively and appends file contents to the system prompt in alphabetical filename order. It uses .roorules as a fallback when the preferred directory is empty. See Roo Code's custom instructions guide.
What can KnowMan add beyond Roo Code rule files?
KnowMan can keep saved articles, links, notes, tags, answers with citations, and memories such as claims, decisions, and playbooks. Its MCP tools include kb_search, kb_ask, kb_get_item, and kb_save, as listed in the KnowMan MCP server guide.
Can Roo Code access KnowMan directly?
KnowMan offers a local MCP server with npx -y @knowman/mcp and a hosted MCP server at https://api.knowman.io/mcp. In clients that support remote MCP servers, add the hosted server URL and sign in with OAuth or use an API key. Read the KnowMan MCP server guide for setup details.