Workspace rules
Rules are Markdown files in .whosedev/rules/ that tell the agent how to work in your repository: coding style, required verification commands, paths to avoid, and links to canonical examples.
Write effective rules
Section titled “Write effective rules”Keep each rule file focused and scannable:
- State required verification (tests, lint, type-check) before work is done.
- Point to canonical examples in the repo instead of pasting large code blocks.
- List restricted paths the agent must not modify without explicit approval.
- Prefer links over duplicating documentation that already lives in the repo.
The starter file .whosedev/rules/coding-style.md is a template you can rename or replace.
Import from other tools
Section titled “Import from other tools”Run WhoseDev: Import Existing Instructions to copy supported instruction files into .whosedev/rules/:
AGENTS.mdCLAUDE.md- Other supported copilot-style instruction files found in the workspace
Original files are not modified.
How rules are applied
Section titled “How rules are applied”Rules in .whosedev/rules/ are loaded as WhoseDev project instructions for agent sessions. They shape how the agent interprets tasks and which constraints it respects in Ask, Plan, and Act modes.
General repository documentation (README files, design docs) is not automatically treated as trusted instructions unless imported or referenced in rules.