Create and maintain repository rules
Record conventions and boundaries for work in a particular codebase.
Repository rules give the agent guidance that should remain relevant across tasks: architectural boundaries, testing commands, coding conventions, and delivery expectations.
Create the rule
Open the repository rules settings, select the intended repository, and create a rule when your role permits it. Give it a title that describes the constraint and write a short instruction with a reason or source reference.
Preserve the existing public API during internal cleanup.
Put new backend tests beside the module's current tests.
Run the focused tests and backend typecheck before opening the PR.Avoid vague instructions such as “always write good code.” A useful rule helps the agent make a decision or find the authoritative convention.
Maintain revisions
Review the saved rule and its revision after editing. If a proposed rule appears in work, read the proposal and use the review controls your role permits. Do not assume an agent suggestion became active configuration merely because it appears in a conversation.
Update rules when commands, package structure, or architecture change. Remove obsolete instructions rather than accumulating contradictory exceptions.
Verify the result
A rule being available or read does not prove it was followed. Inspect the final diff and reported checks for the behavior the rule requires. If compliance matters, make the expectation part of the task's acceptance criteria and your review.
Members with read access can use rules as context; editing and administration remain subject to workspace role checks. Ask an owner or admin if the action is unavailable.
See rules and skills overview, skills, and review changes.