Pi Claude Rules — Development skill for Claude Code

pi-claude-rules

Load Claude Code rules from `.claude/rules/` into [pi](https://github.com/earendil-works/pi-coding-agent).

Pi only reads `AGENTS.md` and `CLAUDE.md`. Teams that deploy scoped instructions with APM or Claude Code into `.claude/rules/*.md` get nothing from them in pi. This extension fixes that. By default it uses a smart hybrid: global rules are loaded before the first request, reads load matching scoped rules into their result, and mutations are blocked until those rules have reached the model.

Quick start

Install the package:

pi install npm:@jordyvanvorselen/pi-claude-rules

Or install from a local checkout:

pi install /path/to/pi-claude-rules

Or try it for one run without installing:

pi -e npm:@jordyvanvorselen/pi-claude-rules

Put rule files in `.claude/rules/` in your project. Start pi. A `[Claude rules]` block appears under pi's own `[Skills]` and `[Extensions]` blocks:

[Claude rules]
  api-versioning, authorization, design-system, git-workflow, java-code-style
  5 rules: 0 always, 5 path-scoped, 0 listed

Press Ctrl+O to expand it. The expanded form shows one line per rule with its mode and glob scope, grouped by source directory:

[Claude rules]
  5 rules: 0 always, 5 path-scoped, 0 listed
  .claude/rules
    api-versioning   on match  connect-backend/src/main/**/*.java
    authorization    on match  connect-backend/src/**/*.java
    design-system    on match  connect-portal/src/**/*.scss
    git-workflow     on match  **
    java-code-style  on match  {connect-backend,panel-event-processor}/src/main/**/*.java

The block is a TUI-only session entry. It is stored in the session file so it survives a resume, and it is never sent to the model.

Run `/claude-rules` to see what was found.

Rule files

A rule is a Markdown file with optional YAML frontmatter. The body is the instruction text.

---
description: V1/V2 API versioning rules for the backend
paths:
  - "connec