From 3f2ad304bbf7beae51a521f8f16e1ce0a7976ddc Mon Sep 17 00:00:00 2001 From: jdardash <135767837+jdardash@users.noreply.github.com> Date: Sun, 16 Aug 2026 17:55:28 -0700 Subject: [PATCH] chore(agents): sync portable agent core v8f7a8070 Generated from ~/.claude/portable/AGENT_CORE.md by sync_agent_context.py and published by publish_agent_context.py, so agents running on GitHub read the same operating rules as agents running locally: Claude Code (.claude/rules/agent-core.md), Codex and Aider (AGENTS.md), Copilot (.github/copilot-instructions.md), Gemini (GEMINI.md, .gemini/styleguide.md). Only the block between the AGENT CORE markers is generated. Anything outside it is untouched and overrides it. --- .cursor/rules/agent-core.mdc | 5 ++++- .gemini/styleguide.md | 5 ++++- .github/copilot-instructions.md | 5 ++++- AGENTS.md | 5 ++++- GEMINI.md | 5 ++++- 5 files changed, 20 insertions(+), 5 deletions(-) diff --git a/.cursor/rules/agent-core.mdc b/.cursor/rules/agent-core.mdc index 15ad269..7cb2425 100644 --- a/.cursor/rules/agent-core.mdc +++ b/.cursor/rules/agent-core.mdc @@ -3,7 +3,7 @@ description: Portable agent operating rules alwaysApply: true --- - + # Agent Core (portable operating rules) Tool-agnostic rules for any coding agent working in this user's repositories: Claude Code, @@ -19,6 +19,9 @@ that file, then re-run `python ~/.claude/scripts/sync_agent_context.py --all`. - Keep answers short. Lead with what changed and the result. - Always cite `file:line` when explaining code. - ASCII-only in program output on Windows consoles (cp1252): use `+/-/->`, never box-drawing or check marks. +- **No em dashes, anywhere**: replies, code, comments, commit messages, docs, generated text. Restructure with a comma, a semicolon, parentheses, or a second sentence. +- **Nothing you write may read as machine-written.** No stock openers or closers ("I hope this finds you well", "excited to leverage", "delve", "it's not just X, it's Y"), no three perfectly parallel bullets, no restating the question before answering it. Vary sentence length; one concrete specific beats three generic claims. +- In anything a person receives (email, DM, chat message, letter), the colon and the dash used as punctuation are out as well ("Hi Derek -", "Quick background:"); hyphens inside compound words and product names are fine. A project may exempt an artifact that is machine-read before a human sees it. ## 2. Concurrency: you are never the only writer diff --git a/.gemini/styleguide.md b/.gemini/styleguide.md index 9ec3faf..648be06 100644 --- a/.gemini/styleguide.md +++ b/.gemini/styleguide.md @@ -3,7 +3,7 @@ > Read by the Gemini Code Assist GitHub app when it reviews pull requests. > Generated mirror of the portable agent core. See AGENTS.md. - + # Agent Core (portable operating rules) Tool-agnostic rules for any coding agent working in this user's repositories: Claude Code, @@ -19,6 +19,9 @@ that file, then re-run `python ~/.claude/scripts/sync_agent_context.py --all`. - Keep answers short. Lead with what changed and the result. - Always cite `file:line` when explaining code. - ASCII-only in program output on Windows consoles (cp1252): use `+/-/->`, never box-drawing or check marks. +- **No em dashes, anywhere**: replies, code, comments, commit messages, docs, generated text. Restructure with a comma, a semicolon, parentheses, or a second sentence. +- **Nothing you write may read as machine-written.** No stock openers or closers ("I hope this finds you well", "excited to leverage", "delve", "it's not just X, it's Y"), no three perfectly parallel bullets, no restating the question before answering it. Vary sentence length; one concrete specific beats three generic claims. +- In anything a person receives (email, DM, chat message, letter), the colon and the dash used as punctuation are out as well ("Hi Derek -", "Quick background:"); hyphens inside compound words and product names are fine. A project may exempt an artifact that is machine-read before a human sees it. ## 2. Concurrency: you are never the only writer diff --git a/.github/copilot-instructions.md b/.github/copilot-instructions.md index d04e3c6..a6c7009 100644 --- a/.github/copilot-instructions.md +++ b/.github/copilot-instructions.md @@ -2,7 +2,7 @@ > Generated mirror of the portable agent core. See AGENTS.md. - + # Agent Core (portable operating rules) Tool-agnostic rules for any coding agent working in this user's repositories: Claude Code, @@ -18,6 +18,9 @@ that file, then re-run `python ~/.claude/scripts/sync_agent_context.py --all`. - Keep answers short. Lead with what changed and the result. - Always cite `file:line` when explaining code. - ASCII-only in program output on Windows consoles (cp1252): use `+/-/->`, never box-drawing or check marks. +- **No em dashes, anywhere**: replies, code, comments, commit messages, docs, generated text. Restructure with a comma, a semicolon, parentheses, or a second sentence. +- **Nothing you write may read as machine-written.** No stock openers or closers ("I hope this finds you well", "excited to leverage", "delve", "it's not just X, it's Y"), no three perfectly parallel bullets, no restating the question before answering it. Vary sentence length; one concrete specific beats three generic claims. +- In anything a person receives (email, DM, chat message, letter), the colon and the dash used as punctuation are out as well ("Hi Derek -", "Quick background:"); hyphens inside compound words and product names are fine. A project may exempt an artifact that is machine-read before a human sees it. ## 2. Concurrency: you are never the only writer diff --git a/AGENTS.md b/AGENTS.md index 5831d64..36d3193 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -3,7 +3,7 @@ > Cross-tool agent contract for this repo. Spec: > Project-specific rules go ABOVE the managed block and override it. - + # Agent Core (portable operating rules) Tool-agnostic rules for any coding agent working in this user's repositories: Claude Code, @@ -19,6 +19,9 @@ that file, then re-run `python ~/.claude/scripts/sync_agent_context.py --all`. - Keep answers short. Lead with what changed and the result. - Always cite `file:line` when explaining code. - ASCII-only in program output on Windows consoles (cp1252): use `+/-/->`, never box-drawing or check marks. +- **No em dashes, anywhere**: replies, code, comments, commit messages, docs, generated text. Restructure with a comma, a semicolon, parentheses, or a second sentence. +- **Nothing you write may read as machine-written.** No stock openers or closers ("I hope this finds you well", "excited to leverage", "delve", "it's not just X, it's Y"), no three perfectly parallel bullets, no restating the question before answering it. Vary sentence length; one concrete specific beats three generic claims. +- In anything a person receives (email, DM, chat message, letter), the colon and the dash used as punctuation are out as well ("Hi Derek -", "Quick background:"); hyphens inside compound words and product names are fine. A project may exempt an artifact that is machine-read before a human sees it. ## 2. Concurrency: you are never the only writer diff --git a/GEMINI.md b/GEMINI.md index db57ea4..995d391 100644 --- a/GEMINI.md +++ b/GEMINI.md @@ -2,7 +2,7 @@ > Generated mirror of the portable agent core. See AGENTS.md. - + # Agent Core (portable operating rules) Tool-agnostic rules for any coding agent working in this user's repositories: Claude Code, @@ -18,6 +18,9 @@ that file, then re-run `python ~/.claude/scripts/sync_agent_context.py --all`. - Keep answers short. Lead with what changed and the result. - Always cite `file:line` when explaining code. - ASCII-only in program output on Windows consoles (cp1252): use `+/-/->`, never box-drawing or check marks. +- **No em dashes, anywhere**: replies, code, comments, commit messages, docs, generated text. Restructure with a comma, a semicolon, parentheses, or a second sentence. +- **Nothing you write may read as machine-written.** No stock openers or closers ("I hope this finds you well", "excited to leverage", "delve", "it's not just X, it's Y"), no three perfectly parallel bullets, no restating the question before answering it. Vary sentence length; one concrete specific beats three generic claims. +- In anything a person receives (email, DM, chat message, letter), the colon and the dash used as punctuation are out as well ("Hi Derek -", "Quick background:"); hyphens inside compound words and product names are fine. A project may exempt an artifact that is machine-read before a human sees it. ## 2. Concurrency: you are never the only writer