Repository navigation
Why not add '.pi/rules' directory into RuleSource #11
Description
Problem
Why not add '.pi/rules' directory into RuleSource?
Proposal
update RuleSource like below
export type RuleSource =
| ".pi/rules"
| "~/.pi/rules"
| ".omo/rules"
| ".claude/rules"
| ".cursor/rules"
| ".github/instructions"
| ".github/copilot-instructions.md"
| "AGENTS.md"
| "CLAUDE.md"
| "CONTEXT.md"
| "~/.omo/rules"
| "~/.opencode/rules"
| "~/.claude/rules"
| "~/.config/opencode/AGENTS.md"
| "~/.claude/CLAUDE.md";Alternatives considered
No response
Activity
code-yeongyu commentedon Sep 24, 2026
Implemented in #33 (merged in
ed6442f01bd2451045a1f7c11310da7f198dc457, released as v0.2.0)..pi/rules/and~/.pi/rules/are now first-class sources, same pattern as.omo/rules/. Discovery, SOURCE_PRIORITY, finder mapping, tests, and README are updated. Downstream senpi does not yet vendor this source and will need to pick it up on the next rules sync.