Background
PR #60 (`Slim global rules to bot-enforceable subset`) established the right pattern for handling Copilot's PR review bot's ~4k char read cap: remove English-prose rules entirely rather than hoist them into a separate file. The bot won't enforce sentence case, banned words, or other prose conventions regardless of which file they're in (per MEMORY.md → `feedback_copilot_review_is_bug_finder_not_style_linter.md`), so the Copilot-facing files should carry only bot-enforceable rules: AI-attribution, favicon/OG, code-shape patterns.
After PR #60, `tools/.github/copilot-instructions.md` is 2886 chars with 2 global rules (AI-attribution, favicon/OG) plus project-specific bug classes — well under cap with room to grow.
This issue tracks applying the same slim treatment to the 3 repos that #59 originally flagged at the cap:
- `rosen-frontend` — 3995 chars (5 chars from cap)
- `class` — 3993 chars
- `houseofjawn-bot` — 3992 chars
Each is one byte from invisibly losing content the next time a bug class is added.
What to do per repo
For each of the 3 repos:
- Read `.github/copilot-instructions.md`
- Identify the "Global rules to flag" section (or equivalent)
- Remove these prose-only rules (the bot won't enforce them):
- Sentence case
- No emojis (in code/comments — bot doesn't reliably grep for them)
- Banned words / anti-slop list
- Keep these bot-enforceable rules:
- No AI-authorship attribution (bot can grep PR bodies/commits)
- Favicon/OG meta tags (bot can check meta tag presence) — scope to actually-deployed paths if applicable
- Confirm the file drops to comfortable size (~2-3k chars)
- Open a slim-globals PR per repo
The English-prose conventions remain enforced for primary assistants (Claude Code, etc.) via `~/.claude/CLAUDE.md` — they just don't need to be in Copilot-facing files.
Related
Acceptance
Background
PR #60 (`Slim global rules to bot-enforceable subset`) established the right pattern for handling Copilot's PR review bot's ~4k char read cap: remove English-prose rules entirely rather than hoist them into a separate file. The bot won't enforce sentence case, banned words, or other prose conventions regardless of which file they're in (per MEMORY.md → `feedback_copilot_review_is_bug_finder_not_style_linter.md`), so the Copilot-facing files should carry only bot-enforceable rules: AI-attribution, favicon/OG, code-shape patterns.
After PR #60, `tools/.github/copilot-instructions.md` is 2886 chars with 2 global rules (AI-attribution, favicon/OG) plus project-specific bug classes — well under cap with room to grow.
This issue tracks applying the same slim treatment to the 3 repos that #59 originally flagged at the cap:
Each is one byte from invisibly losing content the next time a bug class is added.
What to do per repo
For each of the 3 repos:
The English-prose conventions remain enforced for primary assistants (Claude Code, etc.) via `~/.claude/CLAUDE.md` — they just don't need to be in Copilot-facing files.
Related
Acceptance