Skip to content

Project Rules

Release status

RightNow Agent is coming soon for Windows, macOS and Linux. Installation commands and workflows in these guides are reference material until the public release is available.

Project rules give RightNow Agent the conventions and instructions for a directory tree.

Recognized files

Within each directory, RightNow checks these names in order and loads each readable matching file that is not excluded by applicable ignore rules:

  1. 1Agents.md
  2. 2Claude.md
  3. 3CLAUDE.md
  4. 4CLAUDE.local.md
  5. 5AGENT.md
  6. 6AGENTS.md
  • On case-insensitive filesystems, names that resolve to the same file are deduplicated. Top-level Claude-compatible names remain recognized even when machine-wide Claude imports are disabled.
  • Only these names count as top-level instruction files; inside a rules directory, every *.md file loads.
  • Each file loads in full, with no size cap, so keep rules short.

Load order and scope

  1. Home rules load first: <RIGHTNOW_HOME>/rules/*.md, then ~/.claude/ and ~/.cursor/ sources when their compatibility settings allow.
  2. Inside a repository, rules load from the repository root down to the current working directory.
  3. If the working directory is not in a repository, only its local project rules are scanned.
  4. Rules in deeper directories appear later, so they win when instructions conflict. Files in a rules directory load alphabetically.
text
my-repo/
  AGENTS.md
  src/
    AGENTS.md
    components/
      AGENTS.md

Starting in src/components loads all three files. The components rule has the final word on conflicts because it is deepest. Instruction files in directories the agent reads later are noted and read when they apply.

Session-only rules

Use --rules, also available as --append-system-prompt, to add temporary instructions without editing a file.

powershell
rightnow --rules "Always use TypeScript. Prefer functional components."

RightNow wraps this text in <human_rules> and appends it when a session is created. A system prompt override (--system-prompt-override, alias --system-prompt) replaces the base prompt and retains the supplied <human_rules> block. Without an effective system prompt override, changing --rules while resuming leaves the existing rules unchanged. With an effective override, the resumed session uses that override and the currently supplied rules.

The project extension directory

Prefer the .rightnow/ paths. RightNow reads them first and still honors the legacy paths below.

PathPurpose and fallback
.rightnow/config.tomlProject MCP servers, plugins, and permission rules. Reads the legacy config path when the corresponding preferred file is absent.
.rightnow/rules/*.mdBoth the native and legacy rule directories are scanned, subject to ignore rules and file readability.
.rightnow/skills/Project skills. The legacy skill directory and .agents/skills/ are scanned too.
.rightnow/plugins/Project plugins. Reads the legacy plugin directory as a fallback.
.rightnow/hooks/Project hooks. At the repository root, reads the legacy hook directory when the preferred directory is absent.
.rightnow/agents/Project-scoped agent definitions.
.rightnow/lsp.jsonProject-scoped LSP server configuration.
.rightnow/sandbox.tomlProject sandbox profiles.

Compatible rule discovery also covers .claude/rules/*.md, .cursor/rules/*.md, and the project files .claude/CLAUDE.md and .claude/CLAUDE.local.md when their compatibility settings are enabled.

Shipped compatibility configuration

The shipped configuration turns off Claude and Cursor skill, rule, and agent imports from their personal and project directories. Native RightNow rules and recognized top-level project files such as CLAUDE.md still load. To change this, set the [compat] keys listed under Agents and extensions in the configuration reference.

Inspect what loaded

powershell
rightnow inspect

It lists the discovered project instructions with their paths and approximate token counts. Add --json for machine-readable output.