Implementation rules guidance

ReadyPlayerNaN commented

2026-03-19 21:05:18 +00:00

Owner

Should we emphasise in the merge request flow for the agents that they are to follow their current project rules to the absolute, or is it too obvious?

ReadyPlayerNaN self-assigned this

2026-03-19 21:11:08 +00:00

ReadyPlayerNaN added the

triaging

label

2026-03-19 21:11:08 +00:00

ReadyPlayerNaN commented

2026-03-19 21:11:23 +00:00

Author

Owner

I've picked up this issue and I'm reviewing it now.

Triage Assessment

This reads as a question rather than a clear request, so let me offer my assessment:

Current state: Phase 5 already says "Follow all project conventions from CLAUDE.md" and lists specific rules (pnpm, check:fix, typecheck, tests). This ties implementation to project-specific rules.

The gap: The guidance is only in Phase 5 and only references CLAUDE.md. It doesn't state a general principle that the agent should always defer to project-specific conventions, tooling, and configuration over its own defaults. This could matter during triage (understanding project constraints), planning (referencing project patterns), and review (following project style).

My recommendation: It's worth adding — not because agents would deliberately ignore project rules, but because an explicit principle makes it unambiguous. A single sentence in the Principles section would suffice, e.g.: "Follow project conventions absolutely. The project's own rules (CLAUDE.md, linter config, CI checks, coding standards) always take precedence over general defaults."

Question for you: Should I proceed with adding this as a principle, or do you think the current Phase 5 coverage is sufficient?

I've picked up this issue and I'm reviewing it now. ## Triage Assessment This reads as a question rather than a clear request, so let me offer my assessment: **Current state:** Phase 5 already says "Follow all project conventions from `CLAUDE.md`" and lists specific rules (pnpm, check:fix, typecheck, tests). This ties implementation to project-specific rules. **The gap:** The guidance is only in Phase 5 and only references `CLAUDE.md`. It doesn't state a general principle that the agent should always defer to project-specific conventions, tooling, and configuration over its own defaults. This could matter during triage (understanding project constraints), planning (referencing project patterns), and review (following project style). **My recommendation:** It's worth adding — not because agents would deliberately ignore project rules, but because an explicit principle makes it unambiguous. A single sentence in the Principles section would suffice, e.g.: "Follow project conventions absolutely. The project's own rules (CLAUDE.md, linter config, CI checks, coding standards) always take precedence over general defaults." **Question for you:** Should I proceed with adding this as a principle, or do you think the current Phase 5 coverage is sufficient?

ReadyPlayerNaN commented

2026-03-19 21:27:06 +00:00

Author

Owner

yes

ReadyPlayerNaN added

planning

and removed

triaging

labels

2026-03-19 21:30:44 +00:00

ReadyPlayerNaN commented

2026-03-19 21:30:55 +00:00

Author

Owner

Thanks for confirming. Proceeding with the plan.

Plan

Goal: Add an explicit principle that agents must follow project-specific rules absolutely, ensuring project conventions always take precedence over general defaults.

Approach: Add a new principle to the Principles section and strengthen the Phase 5 guidance to be more general.

Tasks:

Add principle to Principles section — Add: "Follow project rules absolutely. The project's own conventions (CLAUDE.md, linter config, CI checks, coding standards) always take precedence over general defaults. Read and follow project-specific guidance before making any changes."
Generalize Phase 5 reference — Change the current "Follow all project conventions from CLAUDE.md" to also note that project rules apply to all phases, not just implementation. Add a brief note: "These rules apply throughout the lifecycle — respect project conventions during triage, planning, and review as well."

Risks: None.

Test strategy:

Verify the new principle is in the Principles section.
Verify Phase 5 references are consistent with the new principle.

Thanks for confirming. Proceeding with the plan. ## Plan **Goal:** Add an explicit principle that agents must follow project-specific rules absolutely, ensuring project conventions always take precedence over general defaults. **Approach:** Add a new principle to the Principles section and strengthen the Phase 5 guidance to be more general. **Tasks:** 1. **Add principle to Principles section** — Add: "**Follow project rules absolutely.** The project's own conventions (`CLAUDE.md`, linter config, CI checks, coding standards) always take precedence over general defaults. Read and follow project-specific guidance before making any changes." 2. **Generalize Phase 5 reference** — Change the current "Follow all project conventions from `CLAUDE.md`" to also note that project rules apply to all phases, not just implementation. Add a brief note: "These rules apply throughout the lifecycle — respect project conventions during triage, planning, and review as well." **Risks:** None. **Test strategy:** - Verify the new principle is in the Principles section. - Verify Phase 5 references are consistent with the new principle.

👍 1

ReadyPlayerNaN added

implementing

and removed

planning

labels

2026-03-19 21:31:01 +00:00

ReadyPlayerNaN referenced this issue from a commit

2026-03-19 21:41:11 +00:00

docs: add principle to follow project rules absolutely

ReadyPlayerNaN referenced this issue from a pull request that will close it,

2026-03-19 21:41:22 +00:00